[Top][All Lists]

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

Re: [Chicken-users] on generating types files for compound libraries of

From: Peter Bex
Subject: Re: [Chicken-users] on generating types files for compound libraries of multiple modules
Date: Wed, 14 Aug 2019 08:51:56 +0200
User-agent: Mutt/1.10.1 (2018-07-13)

On Wed, Aug 14, 2019 at 08:23:51AM +0200, Marco Maggi wrote:
> Ciao,
>   I see  there is  no declaration  specifier for  "-emit-types-file", is
> there   a   reason?    I   would   appreciate   something   similar   to
> "emit-import-library".

I don't know, but it might be just a matter of nobody having had a use
case yet.  I've made a ticket for this:

>   Also: how do  you handle types files for shared  libraries composed by
> multiple modules?   Should I generate a  types file for each  module and
> install all of them along the shared library?  I doubt this is correct.

No, as far as I know you simply load the types database using -types or
-consult-types-file and that accepts any filename.  The core types
database (types.db) also contains type information for several modules.
So when you emit the types file you can just write it to a single file.

Actually, I don't think there's even functionality in place to separate
out the types per module.  So what you're trying to do sounds perfectly

>   I have shared  libraries with multiple modules compiled  in.  Only one
> module is the "public" one (exporting the public API), the others export
> some "public" syntactic bindings  and some "private" syntactic bindings.
> Is this case currently supported by CHICKEN?

That should be fine.  It's not completely standard, so you might need to
do a few things here and there to make it work, but I don't see any
problem with it.  If you're running into specific problems, let us know
and we'll try to find out what's going wrong.


Attachment: signature.asc
Description: PGP signature

reply via email to

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