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

2006-10-25 Thread John Labenski
On 10/25/06, Klaas Holwerda <[EMAIL PROTECTED]> 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, > >

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

2006-10-25 Thread Klaas Holwerda
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

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

2006-10-24 Thread John Labenski
Sorry about the delay, you're right that the problem is the linking order. I got tyhe official wxWidgets 2.6.3 compiled everything as static release libs and I get the same errors, not linking to wxNumberEntryDialog for example. The problem is that the configure generated Makefile puts the stedit

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

2006-10-24 Thread klaas.holwerda
I see this was actually right, since there are only non wxwidgest and wxstedit libs in this list. So to conclude to make it link in static mode the order must be: g++ -o samples/stedit/wxstedit wxstedit_wxstedit.o -L./lib-L./lib-L/usr/local/lib -pthread -lwx_gtk2d_stedit-2.6 AND the

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

2006-10-24 Thread klaas.holwerda
So now the static: I reinstalled wxWidgets static. And configure of wxstedit gives me this. Configuration for wxstedit 1.2.3 successfully completed. Summary of main configuration settings for wxstedit: - DEBUG build - ANSI m

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

2006-10-24 Thread klaas.holwerda
Hi John, So finally i decide to build wxWidgets in shared mode, and see what wxstedit did with that. - it compile and linked, but the samples does not run properly. [EMAIL PROTECTED] stedit]$ ldd ./wxstedit linux-gate.so.1 => (0x0027a000) libwx_based-2.6.so.0 => /usr/local/lib/

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

2006-10-24 Thread Klaas Holwerda
John Labenski wrote: > On 10/23/06, klaas.holwerda <[EMAIL PROTECTED]> wrote: > >>Hi John, >> >>I did the following, to see if the latest produced >>libwx_gtk2d_stedit-2.6.a might work with wxLua: > > > Ok, well first things first, I assume that you can now sucessfully > compile, link, and run w

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

2006-10-23 Thread John Labenski
On 10/23/06, klaas.holwerda <[EMAIL PROTECTED]> wrote: > Hi John, > > I did the following, to see if the latest produced > libwx_gtk2d_stedit-2.6.a might work with wxLua: Ok, well first things first, I assume that you can now sucessfully compile, link, and run wxstedit, the sample in wxCode's wxst

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

2006-10-23 Thread klaas.holwerda
Hi John, I did the following, to see if the latest produced libwx_gtk2d_stedit-2.6.a might work with wxLua: cd /usr/local/lib cp libwx_gtk2d_stedit-2.6.a libstedit.a Then i cleaned wxLua ( make clean), and next compiled again. I did configure, but i have they idea wxLua is still looking for li

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

2006-10-23 Thread klaas.holwerda
Hi John, John Labenski wrote: > Ok, your lib built fine. > > Yes its a linking problem. I did set LD_LIBRAYPATH too, but no difference. > I don't see any errors from not finding the libs, so I don't > understand the problem. Do all these libs exist? Try this in the > wxWidgets lib dir to see if

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

2006-10-23 Thread John Labenski
On 10/23/06, klaas.holwerda <[EMAIL PROTECTED]> wrote: > Hi John, > > I did get the lattest CVS ( removed wxstedit and updated it clean. ). > Did run ./configure and make. > This is what i get down here. I am not sure if setup0.h needs to be > copied on unix to setup.h, but in any case the result s

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

2006-10-23 Thread klaas.holwerda
Hi John, I did get the lattest CVS ( removed wxstedit and updated it clean. ). Did run ./configure and make. This is what i get down here. I am not sure if setup0.h needs to be copied on unix to setup.h, but in any case the result seems to be the same. Wait for 2.8.0 ? :-( Klaas [EMAIL PROTECTE

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

2006-10-23 Thread John Labenski
On 10/23/06, Francesco Montorsi <[EMAIL PROTECTED]> wrote: > > There's something at the end of build/configure.ac, but I don't > > understand it at all. > > > > # argument 1: here put the minimum required version of wx > > # argument 2: here you must put a comma-separed list of all wx > > required

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

2006-10-23 Thread Francesco Montorsi
John Labenski ha scritto: > Ok, starting over, the wxStEdit bakefiles are updated to the ones in > wxCode/build and I've regenerated everything using bakefile 0.2.0 in > MSW using the prebuilt exe. Committed and did a checkout in linux and > ran acregen.sh to get a new configure. > > The problem i

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

2006-10-23 Thread John Labenski
Ok, starting over, the wxStEdit bakefiles are updated to the ones in wxCode/build and I've regenerated everything using bakefile 0.2.0 in MSW using the prebuilt exe. Committed and did a checkout in linux and ran acregen.sh to get a new configure. The problem is that in components/wxstedit/build/wx