Menu
▾
▴
wxcode-users
|
From: klaas.holwerda <kho...@xs...> - 2006-11-08 21:12:04
|
Hi John, At least the latest CVS of wxstedit under VC6 with nmake in release build , produces the wrong library name. nmake -f makefile.vc BUILD=release I did clean all *.lib *.obj files etc. by hand first, to be sure. I think it should produce wxmsw26_stedit.lib But in debug and release i only get wxmsw26d_stedit.lib Hope you know how to fix this, Klaas |
|
From: John L. <jla...@gm...> - 2006-11-08 22:04:29
|
On 11/8/06, klaas.holwerda <kho...@xs...> wrote: > Hi John, > > At least the latest CVS of wxstedit under VC6 with nmake in release > build , produces the wrong library name. > > nmake -f makefile.vc BUILD=release > > I did clean all *.lib *.obj files etc. by hand first, to be sure. > > I think it should produce wxmsw26_stedit.lib > But in debug and release i only get wxmsw26d_stedit.lib > > Hope you know how to fix this, Ugh... more bakefile problems. I'll try to look into it tonight. For now just copy it to the right name... -John Labenski |
|
From: klaas.holwerda <kho...@xs...> - 2006-11-08 22:07:11
|
Next i tried using wxWidgets 2.7.2., and it wants to produce the same name ( so not with 27 in it ). And it wants to use wxmsw26d_stc.lib and it should be wxmsw27d_stc.lib?? But it is looking in the rigth directories for it, so these things seem to be hard coded somewhere? Klaas klaas.holwerda wrote: > Hi John, > > At least the latest CVS of wxstedit under VC6 with nmake in release > build , produces the wrong library name. > |
|
From: klaas.holwerda <kho...@xs...> - 2006-11-08 22:12:26
|
klaas.holwerda wrote: > But it is looking in the rigth directories for it, so these things seem > to be hard coded somewhere? > In the makefile.vc i changed the WX_VERSION to 27 , that solved one problem. Still i though setting WXWIN should be enough. Klaas |
|
From: John L. <jla...@gm...> - 2006-11-08 22:29:01
|
On 11/8/06, klaas.holwerda <kho...@xs...> wrote: > klaas.holwerda wrote: > > But it is looking in the rigth directories for it, so these things seem > > to be hard coded somewhere? > > > In the makefile.vc i changed the WX_VERSION to 27 , that solved one problem. > Still i though setting WXWIN should be enough. To my knowledge there is no way in MSW to get the version number into the nmake makefiles. There is no equivalent to wx-config so unfortunately you always have to specify WX_VERSION. WXWIN on the other hand is traditionally the path to the wxWidgets library and so it'll contain 'C:\path\to\wxWidgets-XXX'. -John Labenski |
|
From: John L. <jla...@gm...> - 2006-11-09 05:07:36
|
On 11/8/06, John Labenski <jla...@gm...> wrote:
> On 11/8/06, klaas.holwerda <kho...@xs...> wrote:
> > klaas.holwerda wrote:
> > > But it is looking in the rigth directories for it, so these things seem
> > > to be hard coded somewhere?
> > >
> > In the makefile.vc i changed the WX_VERSION to 27 , that solved one problem.
> > Still i though setting WXWIN should be enough.
>
> To my knowledge there is no way in MSW to get the version number into
> the nmake makefiles. There is no equivalent to wx-config so
> unfortunately you always have to specify WX_VERSION. WXWIN on the
> other hand is traditionally the path to the wxWidgets library and so
> it'll contain 'C:\path\to\wxWidgets-XXX'.
After reviewing the makefile.vc the behavior you saw is "normal." You
actually have to specify on the command line what build you want.
Instead of editing the makefile.vc just put the directives you want to
override on the command line like this.
$nmake WX_VERSION=27 WX_DEBUG=0 -f makefile.vc
Regards,
John Labenski
|
|
From: Klaas H. <db...@nl...> - 2006-11-09 09:03:30
|
John Labenski wrote: > $nmake WX_VERSION=27 WX_DEBUG=0 -f makefile.vc Oke if that is the way, better cjhange it to the lattest official release i think. I wonder why it is not possible to detect the version (as i do in Cmake from the library names ). C:\wxMSW-2.7.2\lib\vc_lib\mswd\build.cfg Contains this after wxWidgets is build: WXVER_MAJOR=2 WXVER_MINOR=7 WXVER_RELEASE=2 So the information is there, wonder why Franscesco is not using this, maybe it is not doable in nmake. wx-config.exe ( recently mentioned on the dev list )does it like that. One problem is that building wxWidgets using VC project files, does not produce the build.cfg. So the version option would be needed still. Klaas -- Unclassified |
|
From: Francesco M. <f18...@ya...> - 2006-11-09 12:12:41
|
Klaas Holwerda ha scritto: > John Labenski wrote: > >> $nmake WX_VERSION=27 WX_DEBUG=0 -f makefile.vc > > Oke if that is the way, better cjhange it to the lattest official release i think. > > I wonder why it is not possible to detect the version (as i do in Cmake from the library names ). > > C:\wxMSW-2.7.2\lib\vc_lib\mswd\build.cfg > > Contains this after wxWidgets is build: > > WXVER_MAJOR=2 > WXVER_MINOR=7 > WXVER_RELEASE=2 > > So the information is there, wonder why Franscesco is not using this, maybe it is not doable in nmake. right - DOS and NMAKE don't give you enough tools to do that. And I also see another major problem: if you have multiple wx builds then you're going to have multiple build.cfg files in different subfolders of vc_lib; how can you choose one among them ? There's no notion of "default build" on Windows... so autodetection of the build configuration is possible only on linux with autoconf format... > wx-config.exe ( recently mentioned on the dev list )does it like that. right... but it needs a shell / make tool which supports backtick expansion (aka command expansion), which is not the case for most of win32 MAKEs... Francesco |
|
From: Klaas H. <db...@nl...> - 2006-11-09 22:36:58
|
Francesco Montorsi wrote: > Klaas Holwerda ha scritto: > >>John Labenski wrote: >> >> >>>$nmake WX_VERSION=27 WX_DEBUG=0 -f makefile.vc >> >>Oke if that is the way, better cjhange it to the lattest official release i think. >> >>I wonder why it is not possible to detect the version (as i do in Cmake from the library names ). >> >>C:\wxMSW-2.7.2\lib\vc_lib\mswd\build.cfg >> >>Contains this after wxWidgets is build: >> >>WXVER_MAJOR=2 >>WXVER_MINOR=7 >>WXVER_RELEASE=2 >> >>So the information is there, wonder why Franscesco is not using this, maybe it is not doable in nmake. > > right - DOS and NMAKE don't give you enough tools to do that. > And I also see another major problem: if you have multiple wx builds > then you're going to have multiple build.cfg files in different > subfolders of vc_lib; how can you choose one among them ? > > There's no notion of "default build" on Windows... so autodetection of > the build configuration is possible only on linux with autoconf format... The default is debug, which is found in %WXWIN%. Others need to be specified with BUILD= > > >>wx-config.exe ( recently mentioned on the dev list )does it like that. > > right... but it needs a shell / make tool which supports backtick > expansion (aka command expansion), which is not the case for most of > win32 MAKEs... He also talks about "and in VC using response files" to make this happen. I don't know what that is. I do know that Cmake produces targets that run *.bat batch files, and produce files. Those targets are part of the VC projects files. I will try to find what is happening in case of nmake generated makefile. If such a target can produce some file, which is include in the nmake files somehow, it might be possible. Klaas -- Unclassified |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X