Re: How to use another module at build time?

[Michael K. <mic...@gm...>]

On 03/25/2012 05:49 AM, Sam Steingold wrote:
>> * Michael Kappert<zvp...@tz...>  [2012-03-23 23:54:25 +0100]:
>>
>> Is there a way to make clisp load the prerequisite, or use the 'full'
>> linking set when building the dependent module?
>
> I think it is best to use dynamic modules and put (require
> "requirement") in the lisp file.

Ok - unfortunately simply require-ing the module did not work because 
clisp-link first compiles all requested modules and only then creates 
the dynmod directory and shared libs.

I guess I need to understand clisp-link and link.sh better...

>> I tried (in link.sh.in)
>> ${MAKE-make} clisp-module \
>>     CC="${CC}" CPPFLAGS="${CPPFLAGS}" CFLAGS="${CFLAGS}" \
>>     CLISP_LINKKIT="$absolute_linkkitdir" CLISP="${CLISP} -K full"
>>
>> and then try to build the module with

>> $ make MODULES=gtk+3
btw, this was wrong, it does not add modules to dynmod/ but replaces 
them with the newly requested...

>> but I still see
>> make[1]: Entering directory `<clisp>/build.gir/gtk+3'
>> <clisp>/clisp -K boot  ...
>
> this is weird. new-clx requires syscalls and the build works fine.
> please take a look at how it is done.

The new-clx lisp files are compiled with -K boot. It seems new-clx does 
not call syscalls functions at compile time. (The "gtk+3" module queries 
GTK+ Typelibs[1] at compile time, via a macro that produces a huge progn 
containing FFI forms.).


Thanks,
Michael

[1] http://developer.gnome.org/gi/unstable/gi-overview.html
--