People with PB 2.1 should re-grab CVS HEAD

#1 Hey, thank you David
I found another problem with the old PB 10.2 project file, but since it died it's good death, who cares ? 8p (fyi : in the ressource copying fieldwhere you enter the icons to be copied into the bundle, there was also a reference to the whole bundle in the products directory, ie kinda like a recursive reference to itself : with the result of a release build clocking at around 140 megs !!!! And not working ;))
Again, thank you :)

Edit : The new 2.1 project builds fine, albeit it didn't copy the built executable to the example folder, for two reasons, afaik :

1 - the directory preferences that you set in PB's prefs, as to where to put build products and intermediate files, seems to not get saved with the Project File : it used my defaults, which is fine with me (ie does it in the pb/build folder, as is the default behavior, iirc)

2 - Since the copy/install phase is disabled in the new project, it doesn't get copied.

Those two together leads to the executable being in the pb/build folder : I just copied it by hand to the example folder. Of course, I can either change my prefs so that it gets built in the example folder, or just create new executables to run either the Release or Debug builds, or both, from inside PB.

Just thought I'd bring this to everyone's attention, so we can either mention this in the ReadMe file, or decide how we go about this.
Good day all

#2 Yes, it looks like the build settings are per user, not per project. So people will need to set that individually. Silly... and I'll keep looking for alternate solutions (or a script to set it up for novice users).

You'll want to set the build target to go to the example directory now. Otherwise, a whole bunch of things won't work, most importantly running/debugging from within PB. ;)

d

#3 Didn't know where else to post this so:

The Debug Target still has a prob, and will not do a correct debug build. The debug defines will not neccesarily get set in the headers themselves, so the global compiler flags need another flag: -DTORQUE_DEBUG.

As it is now, the debug stuff doesnt happen, even in a 'debug' build.

I'll just start a thread. found a difft show stopper.

#4 okay, I'll look at the other thread.. though last I knew, TORQUE_DEBUG was getting set up properly. But admittedly, been a long time since I verified it under PB.