Re: [Chicken-users] #include in foreign-parse

[felix winkelmann]

On Sat, Jul 5, 2008 at 8:25 PM, minh thu <address@hidden> wrote:
>
> No problem, everything is fine.
>
> (But how do I install a local .egg ? chicken-setup complains the .egg
> is not in /tmp/chicken-... )
>
> Then, since the somefile.h ships with the library to bind, it makes sense,
> to replace
>
> #include "somefile.h"
>
> with
>
> #include <somefile.h>
>
> no more put it in the .egg, and assume the library is already installed.
>
> But now, when installing the egg, I've got
>
> Error: during expansion of (foreign-parse ...) - can not open include
> file: "somefile.h"
>
> I think the problem is because of the change "somefile.h"
> <somefile.h>, but I'm not sure.
>
> The header is in /usr/local/include/, maybe sudo chicken-setup does not see 
> it ?
>

That's right. `foreign-parse' will follow the #include and try to
generate bindings
from it's contents. Since the header is not in the egg anymore (and
foreign-parse
does not search default include paths), the egg isn't found. You can wrap the
include-line into

#ifndef CHICKEN
#include ...
#endif

or put the #include into a `foreign-declare' section.


cheers,
felix