Hi Nicola,
for your fix in the bundle make file you added a comment that we should
explain, why we have to link against all libraries on Windows while we
don't need this on any other system. The reason is simple, we don't need
this on Windows either. What we need there is that we define a
pre-pro
> Ahh, I get it... was this change made to support Windows by any chance ? One of
> the big problems with Bundles on the old OpenSTep forNT was that you
> culdnt call anything from the main application that you needed to link
> against - it all had to be linked into the bundle separately.
>
> Th
Ahh, I get it... was this change made to support Windows by any chance ? One of
the big problems with Bundles on the old OpenSTep forNT was that you
culdnt call anything from the main application that you needed to link
against - it all had to be linked into the bundle separately.
This might be m
> > that occurred to me too ... and well it is certainly caused by the fact
> > that gnustep-make has been modified to link bundles against all libraries
>
> So does that mean that it staticly links bundles against available libraries
> rather than using the shared libraries on startup ? I am so
> that occurred to me too ... and well it is certainly caused by the fact
> that gnustep-make has been modified to link bundles against all libraries
So does that mean that it staticly links bundles against available libraries
rather than using the shared libraries on startup ? I am somewhat conf
> having done that I now get a coredump.
that occurred to me too ... and well it is certainly caused by the fact
that gnustep-make has been modified to link bundles against all libraries
... that change is delicate and probably needs to be fixed somewhat ...
problem is understanding all the bits
