[Gtkradiant] [Bug 842] VC7 / vs.net project files

gtkradiant@zerowing.idsoftware.com gtkradiant@zerowing.idsoftware.com
Thu, 27 Nov 2003 20:42:46 -0600


------- Additional Comments From digibob@gotadsl.co.uk  2003-11-27 20:42 -------
The only thing that wont work 'out of the box' with these is the python calling.

You need to set the path up for this manually, as VS.NET will override all 
default path settings ( unless you installed python prior to VS.NET in which 
case it will already use that path in its settings ).

These can be set up via Tools->Options Menu, then Projects/VC++ Directories, 
Add the path to your python dir to the list marked "Show Directories for: 
Executable Files".

I moved out all the linker .lib inputs for libs generated by the solution 
itself, and set up the dependancies to do this all automatically. The linker 
input dirs have NOT as of yet been cleaned up in regards to this change, this 
doesn't cause any problems of course, just leaves some un-needed mess behind.

The camera plugin had an errant /I on one of the command line options, dunno 
how vc6 got away with that, so *shrug*.

Textool isn't in the solution for now, as i'm assuming it just plain doesn't 
compile in vc6 either.

I'll leave more comments later if i think of anything.