chicken-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: minh thu
Subject: [Chicken-users] Re: #include in foreign-parse
Date: Sat, 5 Jul 2008 23:04:27 +0200

2008/7/5 minh thu <address@hidden>:
> Hi,
>
> I've made bindings in the following way (in a .scm file):
>
> (foreign-parse #<<EOF
>
> ___declare ...
> ...
> #include "somefile.h"
> ...
>
> EOF
> )
>
> and the somefile.h is placed in the .egg.
>
> 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 ?
>
> Any idea ? (I'm still using chicken 3.2.0)
>
> Thanks a lot,
> Thu
>


Weird. By ending the #include <...> lines with a #include "file.h" with file.h
being in the .egg, chicken-setup ends successfully.

Is it something known (and corrected in later version) ?

Ciao,
Thu




reply via email to

[Prev in Thread] Current Thread [Next in Thread]