project seetings for Visual Studio

Hi Thomas,

I am currently working on a .bat file to build wxWidgets and a way to be
able to use multiple VS versions with wxWidgets automatically. There is
more to it than just using $(PlatformName).

Basically it involves using nmake -f makefile.vc instead of using the
project files.

nmake -f makefile.vc accepts a couple of interesting parameters.

Here is an example:

nmake -f makefile.vc TARGET_CPU=amd64 COMPILER_PREFIX=vc80 DEBUG=1
SHARED=1 UNICODE=1

would build wxWidgets Unicode Debug DLL, but put the results under

$(WXWIN)/lib/vc80_lib

rather than $(WXWIN)/lib/vc_lib

Additionally you will have to modify $(WXWIN)/include/msvc/wx/setup.h,
because it will always try to include ..*/vc_lib/mswu/setup.h

where it would have to include
..*/vc80_lib/...

etc...

I've got a modified setup.h already and a batch file and got all of it
working on my system using VC80, VC90 and VC90x64.

This all needs finishing touches and documenting though and I could use
some help.

Interested?

Regards

Hajo

Thomas Krebs wrote:
>
>
> Hi,
>
> I'm just looking at the lastest SVN version and see that there is a VS
> solution file for VC8 (beside others). That is nice.
>
> As we need both Win32 and x64 platform version libraries and would like
> to have them in parallel we would like to have settings for the obj and
> library files that do not overwrite the other's platform files.
>
> To do that VC supports that by the help of the variable $(PlatformName)
> in the project seetings.
> Is there any plans to add support for the x64 platform in the VC8
> project files?
> AFAIK you use some meta files to generate these VC project files, so I
> don't know how to do it at that level.
>
> Thomas
> _______________________________________________
> wx-users mailing list
> [email protected]
> http://lists.wxwidgets.org/mailman/listinfo/wx-users
>

_______________________________________________
wx-users mailing list
[email protected]
http://lists.wxwidgets.org/mailman/listinfo/wx-users

On Wed, 2008-07-16 at 19:25 +0200, Hajo Kirchhoff wrote:
> Hi Thomas,
>
> I am currently working on a .bat file to build wxWidgets and a way to be
> able to use multiple VS versions with wxWidgets automatically. There is
> more to it than just using $(PlatformName).
>
> Basically it involves using nmake -f makefile.vc instead of using the
> project files.

I am also a fan of the nmake approach - it seems to be a much cleaner
and more consistent way to get the library built than Visual Studio
solution files.

- Brian

_______________________________________________
wx-users mailing list
[email protected]
http://lists.wxwidgets.org/mailman/listinfo/wx-users

Hajo Kirchhoff schrieb:
> Hi Thomas,
>
> I am currently working on a .bat file to build wxWidgets and a way to be
> able to use multiple VS versions with wxWidgets automatically. There is
> more to it than just using $(PlatformName).
>
> Basically it involves using nmake -f makefile.vc instead of using the
> project files.
>
> nmake -f makefile.vc accepts a couple of interesting parameters.
>
> Here is an example:
>
> nmake -f makefile.vc TARGET_CPU=amd64 COMPILER_PREFIX=vc80 DEBUG=1
> SHARED=1 UNICODE=1
>
> would build wxWidgets Unicode Debug DLL, but put the results under
>
> $(WXWIN)/lib/vc80_lib
>
> rather than $(WXWIN)/lib/vc_lib
>
> Additionally you will have to modify $(WXWIN)/include/msvc/wx/setup.h,
> because it will always try to include ..*/vc_lib/mswu/setup.h
>
> where it would have to include
> ..*/vc80_lib/...
>
> etc...
>
> I've got a modified setup.h already and a batch file and got all of it
> working on my system using VC80, VC90 and VC90x64.
>
> This all needs finishing touches and documenting though and I could use
> some help.
>
> Interested?
>

I am - as always - not very precise in my wording...
I always manage to compile everything successfully after some fiddling
with the project files. I simply want to have project files where I
don't have to fiddling around any more...

And I prefer to have VS project files. It makes it easier to browse
through the sources...

If the nmake makefiles and the VS project files produce different
results in terms of output directories I would think this should be
fixed as well...

Thomas
_______________________________________________
wx-users mailing list
[email protected]
http://lists.wxwidgets.org/mailman/listinfo/wx-users

Hello Thomas

Have you managed to change the output settings on your project options? I
belive that is all you need to avoid the deletion of the other build files.
This is a lot of work, so you can set environment variables.
On the 64 bits hand, I have just created a new solution platform, copy all
the win32 values and set /Wp64 and a few other values.

Regards
Rafael

-----Mensagem original-----
De: Thomas Krebs [mailto:[email protected]
Enviada em: quarta-feira, 16 de julho de 2008 15:58
Para: [email protected]
Assunto: Re: project seetings for Visual Studio



Hajo Kirchhoff schrieb:
> Hi Thomas,
>
> I am currently working on a .bat file to build wxWidgets and a way to
> be able to use multiple VS versions with wxWidgets automatically.
> There is more to it than just using $(PlatformName).
>
> Basically it involves using nmake -f makefile.vc instead of using the
> project files.
>
> nmake -f makefile.vc accepts a couple of interesting parameters.
>
> Here is an example:
>
> nmake -f makefile.vc TARGET_CPU=amd64 COMPILER_PREFIX=vc80 DEBUG=1
> SHARED=1 UNICODE=1
>
> would build wxWidgets Unicode Debug DLL, but put the results under
>
> $(WXWIN)/lib/vc80_lib
>
> rather than $(WXWIN)/lib/vc_lib
>
> Additionally you will have to modify $(WXWIN)/include/msvc/wx/setup.h,
> because it will always try to include ..*/vc_lib/mswu/setup.h
>
> where it would have to include
> ..*/vc80_lib/...
>
> etc...
>
> I've got a modified setup.h already and a batch file and got all of it
> working on my system using VC80, VC90 and VC90x64.
>
> This all needs finishing touches and documenting though and I could
> use some help.
>
> Interested?
>

I am - as always - not very precise in my wording...
I always manage to compile everything successfully after some fiddling with
the project files. I simply want to have project files where I don't have to
fiddling around any more...

And I prefer to have VS project files. It makes it easier to browse through
the sources...

If the nmake makefiles and the VS project files produce different results in
terms of output directories I would think this should be fixed as well...

Thomas
_______________________________________________
wx-users mailing list
[email protected]
http://lists.wxwidgets.org/mailman/listinfo/wx-users

__________ NOD32 3274 (20080716) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com


_______________________________________________
wx-users mailing list
[email protected]
http://lists.wxwidgets.org/mailman/listinfo/wx-users