Re: [wxCode-users] Bakefile libs in configure was Re: does wxstedit compile with 2.6.3

[John L. <jla...@gm...>]

On 10/25/06, Klaas Holwerda <db...@nl...> wrote:
> John Labenski wrote:
> >
> > Anyway, with this simple fix you can use static libs if you like. If I
> > understand correctly, aren't shared libs faster to compile stuff
> > locally since the linker stage takes a little less time? Anyway,
> > that's the reason why I make shared libs if I'm only going to use the
> > program on my own machine, if this is wrong I'd like to know.
>
> I don't know, i just use static to not have dependencies for users of my software. But i can imagine that its quicker to
> link that way.

Thats what I thought too.

> So in the end the problem which is still strange, is that in shared mode the wxstedit sample gave a asserts.
> I think this is because the same libraries are linked several times.

Ok, I see the problem, I was double linking core and base, fixed in
wxStEdit CVS.

> All other smaller problems are configure like issues, like how to get static build when both static and shared wxWidgets
> are available. Very likeley wx-config is not used correctly in the configure scripts.

This is what I do, I set the path to the wx-config I want, create a
new dir in wxStEdit, run ../configure --prefix=new/dir, and that way
you can have two separate build at the same time.

In wxWidgets I do the same, create a dir wxWidgets/config_gtk2_debug
and config_gtk2_static and run ../configure
--prefix=/path/to/wxWidgets/config_gtk2_XXX ... so that I have two
builds at once. I never bother to install wxWidgets since wx-config
finds the includes and the libs properly if you do the above.

------

Next up, get make install to work for wxStEdit. I see how to hack
Makefile.in to do it, but I would prefer a bakefile solution.

Regards,
    John Labenski