Re: How to use another module at build time?

[Sam S. <sd...@gn...>]

> * Michael Kappert <zvp...@tz...> [2012-03-28 00:12:21 +0200]:
>
>> 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.

so what's wrong with (eval-when (:compile-toplevel) (require...)) ?

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

this will help, yes :-)
please help with the docs too.

>>> 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.).

take a look at the anymodule target in Makefile.
if you are not using configure, you should be able to do

$ cd gtk+3 && make clisp-module CLISP="whatever"

if you discover that you really do need all those other make variables,
you can just edit the build Makefile and replace

CLISP="/home/sds/src/clisp/current/build/clisp -K boot  -E UTF-8 -Emisc 1:1 -Epathname 1:1 -norc" ; \

with whatever suits you.


-- 
Sam Steingold (http://sds.podval.org/) on Ubuntu 11.10 (oneiric) X 11.0.11004000
http://www.childpsy.net/ http://camera.org http://americancensorship.org
http://dhimmi.com http://ffii.org http://mideasttruth.com http://jihadwatch.org
God had a deadline, so He wrote it all in Lisp.