> But there are
> plenty of little things in there which mean I would still use my own
> library, not Debug.Trace, even if it did have a few extra functions.
Oh, I see.
That's actually possible.
Okay, I'll withdraw my suggestion this time.
Thanks!
2018年6月12日(火) 14:25 Evan Laforge :
> I agree th
Thank you both for the replies.
My issue with the current situation is that I can navigate myself into a
situation where I’m stuck. By asking ghc to build static libraries, it will
later fall over when it tries to load those.
Guess what I really want is to turn the DYNAMIC_GHC_PROGRAMS into a r
You could work around the dlopen issue as long as the static library is
compiled with -fPIC by using --whole-archive (assuming you permit dangling
references which will need to be resolved later) and making a shared
library out of the static code. But you'd have to create one shared library
per st
