[Bf-committers] Re: [Bf-blender-cvs] CVScommit:blender/extern/bFTGL/make/msvc_7_0ftgl_static_lib.vcprojblender/extern/bullet/make/msvc_7_0Bullet3_vc7.vcprojblender/extern/bullet/make/msvc_7_0/DynamicsBulletDynamics_vc7.vcprojblender/extern/ma

Gilbert, Joseph T. jgilbert at tigr.ORG
Tue Apr 18 17:06:21 CEST 2006


What would make sense is to add ALL the intern and extern projects to 1
single solution in 1 heirarchy of folders.  Then you would create
various build types. For instance:

blender debug
blender release
blenderplayer debug
blenderplayer release
dependancies debug
dependancies release
etc

This is already set up in the vc7 projectfiles to build blender,
blenderplayer and the activeX controller by building/skipping certain
projects through the build menu.

Unfortunately to do this to the vc7 projectfiles will take a significant
effort to do because of all the compiler and linker paths that need to
be modified. But it would be doable nonetheless. If we go with a vc8 set
of projectfiles I would think this would be more sensible than our
current setup. :)

I love the idea about the autogeneration of vcprojectfiles from scons.
However, from what I heard it's not the greatest at doing this. (There
is some problem that you need vc6's compiler to generate the .vcproj
files or something...??) It might also not be convenient for msvc users
because you'd need to update the scons build files, run scons to
generate new projectfiles and reload the projectfiles rather than simply
running cvs update. Although this probably, in the end, is not such a
big price to pay for 'hub' build system approach.


-----Original Message-----
From: bf-committers-bounces at projects.blender.org
[mailto:bf-committers-bounces at projects.blender.org] On Behalf Of Jacques
Beaurain
Sent: Monday, April 17, 2006 10:33 PM
To: bf-blender developers
Subject: Re: [Bf-committers] Re: [Bf-blender-cvs]
CVScommit:blender/extern/bFTGL/make/msvc_7_0ftgl_static_lib.vcprojblende
r/extern/bullet/make/msvc_7_0Bullet3_vc7.vcprojblender/extern/bullet/mak
e/msvc_7_0/DynamicsBulletDynamics_vc7.vcprojblender/extern/ma

I agree fully with all Joseph's points and want to add the following.

Why is there extern, intern and blender solutions? Is it not better to
combine everything in one solution and set up the dependencies
properly?

The problem with the automatic conversion to vc8 is that the compile
and linker flags usually need tweeking as well and you have to redo
this everytime you update from CVS.

The ideal solution would be to use scons's ability to generate vcproj
files (I recently stumbled upon this:
http://www.gamedev.net/community/forums/topic.asp?topic_id=315034&whichp
age=1&#2019592)
This will take a little bit of Python work but I think it can be done.
One can then specify the version you want in the config files and the
do something like the following after a cvs update:

scons buildvcproj

my 2c.

J
_______________________________________________
Bf-committers mailing list
Bf-committers at projects.blender.org
http://projects.blender.org/mailman/listinfo/bf-committers


More information about the Bf-committers mailing list