chicken-hackers
[Top][All Lists]
Advanced

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

Re: [Chicken-hackers] [PATCH] Handle import libraries with static linkag


From: felix . winkelmann
Subject: Re: [Chicken-hackers] [PATCH] Handle import libraries with static linkage egg property
Date: Sat, 27 Jul 2019 22:17:47 +0200

> I finally got around to this.
>
> I decided it would be dumb to invoke the compiler an extra time just to
> emit import libraries when we're already compiling the extension once;
> better to just have csc do what we need it to on that one pass.
>
> I spent a while trying to make this work with the current set of
> options, but in retrospect that's impossible. There are now three
> situations we need to support: (1) the current "sane default" behaviour
> where emitting an import library removes it from the program, (2) the
> situation where a user explicitly drops the library code by passing the
> "-no-module-registration" flag, and (3) this new situation where we need
> to both emit the library code and keep it in the program. To support
> this third case I've added a flag that causes the module registration
> code to be preserved in the program unconditionally -- basically the
> inverse of `-no-module-registration' -- which chicken-install then uses.
>
> I think this is a pretty logical addition, and it fixes the linkage egg
> property, but let me know what you think.

This looks quite clean. I'll have to look more carefully at the patch,
but from the point of usage, it all makes sense.


felix




reply via email to

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