[Cook] Interior_Files

Ryan Thompson ryan at flamtap.org
Thu May 12 04:44:05 EST 2011


Using  #include <../inc/file.h> instead of #include "file.h" resolved the
problem of not finding the generated file. Thanks for your help!

-Ryan



On Tue, May 10, 2011 at 9:31 PM, Pendergraft, Jerry <JPendergraft at sjm.com>wrote:

>  Actually if the problem is that the compiler is not finding the .h file
> then Interior_files is not going to help you.
> Not sure what your directory structure looks like but the two things to
> consider are:
> 1) The -I options given for your compile.
>     - need to point to where you generate the .h file
> 2) The form of the #include directive for the generated file
>     - If you are thinking the form #include "file.h" will help you are
> probably going to be disappointed.
>     - You need to use on of:
>      a) #include <file.h>
>      b) #include <dir/gen/file.h>
>    For case a) you need -Idir/gen for compiler options
>    For case b) you need -I. for compiler options
>
>  The interior_files function is unlikely to be useful for your needs but
> the graph_leaf_file variable may help cook avoid calculating useless
> dependencies, and is usually something like:
>  graph_leaf_file = [project_files];
>
>  Which tells cook not to consider looking for a recipe to generate any
> file on that list. It would reduce such lookups to just your generated
> file[s].
>
>  hope that helps.
>
>
>  ------------------------------
> *From:* cook-users-bounces+jpendergraft=sjm.com at lists.auug.org.au[cook-users-bounces+jpendergraft=
> sjm.com at lists.auug.org.au] on behalf of Ryan Thompson [ryan at flamtap.org]
> *Sent:* Friday, May 06, 2011 4:02 PM
> *To:* cook-users at auug.org.au
> *Subject:* [Cook] Interior_Files
>
>  Can you show me an example of the use of the Interior_Files argument to
> c_incl?
>
> We have a .h file that is generated during the cook process from other
> files.
>
> Once the .h file is generated, it needs to be available for inclusion by
> .cpp files in the normal build process.
>
> What I see happen is that the .h is created but then the .h is not found
> when cook is building one of the .cpp files that includes it.
>
> I think Interior_Files may be what we need to use but I can't figure out
> the usage.
>
> Thanks for any information,
>
> -Ryan Thompson
>    This communication, including any attachments, may contain information
> that is proprietary, privileged, confidential or legally exempt from
> disclosure. If you are not a named addressee, you are hereby notified that
> you are not authorized to read, print, retain a copy of or disseminate any
> portion of this communication without the consent of the sender and that
> doing so may be unlawful. If you have received this communication in error,
> please immediately notify the sender via return e-mail and delete it from
> your system.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.auug.org.au/pipermail/cook-users/attachments/20110511/36a682f7/attachment.html>


More information about the Cook-users mailing list