Re: [Chicken-users] Units as shared libraries (SWING, dynamic, does not work)

[Joel Reymont]

> Thomas Chust wrote:

>I work around this problem by including something like
>
>(cond-expand
>  ((or chicken-compile-shared shared)
>   )
>  (else
>   (declare (unit my-unit-name))))
>
>at top of the unit's source code. 

My issue is that SWIG requires you to put a %module directive at the top
of your .i file which it then merrily translates into the unit
declaration. The only way to generate a Chicken extension is to break
your compilation right after SWIG and edit the generated scheme file or
to insert a sed (remove this line from file) step into the make file. I
don think the sed bit will work on Windows, though.

    Joel

-- 
OpenPoker: The Linux of poker software
http://wagerlabs.com/forums
Tenerife: Canary Islands: Spain