Matthieu,
Matthieu Herrb wrote:
Torrey Lyons wrote (in a message from Saturday 25)
> The issue on Mac OS X is that most shared libraries want to be built
> as "two-level namespace" images. Two-level namespace images have
> significant advantages in loading speed, but they require that they
Hi
> Harold L Hunt II wrote:
>
> > I tried a build without $(SMLIB) and $(ICELIB) in SharedXtReqs, but it
> > fails to link due to unresolved symbols (all symbols must be resolved at
> > library link time in DLLs on Windows).
> >
> > I will have to consult with the rest of the Cygwin people to see
Torrey Lyons wrote (in a message from Saturday 25)
> The issue on Mac OS X is that most shared libraries want to be built
> as "two-level namespace" images. Two-level namespace images have
> significant advantages in loading speed, but they require that they
> have no unresolved symbols when
Harold L Hunt II wrote:
> I tried a build without $(SMLIB) and $(ICELIB) in SharedXtReqs, but it
> fails to link due to unresolved symbols (all symbols must be resolved at
> library link time in DLLs on Windows).
>
> I will have to consult with the rest of the Cygwin people to see what we
> should
Thanks Torrey.
I tried a build without $(SMLIB) and $(ICELIB) in SharedXtReqs, but it
fails to link due to unresolved symbols (all symbols must be resolved at
library link time in DLLs on Windows).
I will have to consult with the rest of the Cygwin people to see what we
should do now.
Thanks
