TGB and TGBGame need PUAP_OPTIMIZE PUAP_SCRIPT_CHANGE flags
by Bret Patterson · in iTorque 2D · 05/08/2009 (7:00 pm) · 5 replies
Bug tag removed by Michael Perry
The TGB Builder and TGBGame targets for MAC etc need the PUAP_OPTIMIZE PUAP_SCRIPT_CHANGE preprocessor defines to make the TGB Builder and other iTGB programs consistent with the iPhone.
Additionally native components require these to be consistent since the calls to setUsesPhysics doesn't
exist without these flags.
The TGB Builder and TGBGame targets for MAC etc need the PUAP_OPTIMIZE PUAP_SCRIPT_CHANGE preprocessor defines to make the TGB Builder and other iTGB programs consistent with the iPhone.
Additionally native components require these to be consistent since the calls to setUsesPhysics doesn't
exist without these flags.
About the author
#2
05/08/2009 (7:13 pm)
Yea that's fine. This one was minor.
#3
with itg 1.2 when i try to add these 2 PREPROCESSOR MACRO in the TGBGAme target and Torque Game Builder Target , it compiles without any errors but when i try to open the shooter_components project it fails in iTGB ?
05/13/2009 (2:01 pm)
Hello,with itg 1.2 when i try to add these 2 PREPROCESSOR MACRO in the TGBGAme target and Torque Game Builder Target , it compiles without any errors but when i try to open the shooter_components project it fails in iTGB ?
#4
05/13/2009 (4:03 pm)
I believe that this is causing me some problems. Where do I go to check/set these flags for my project?
#5
in Xcode, select the target (Torque Game Builer or TGBGame release or debug versions depending on what you are testing on), then select the Info icon. Once that window opens up, select the Build tab, then scroll down to the preprocessor stuff.
05/13/2009 (5:45 pm)
yes, if you enable PUAP_SCRIPT_CHANGE for TGB and TGBGame, you won't be able to open any projects. This seems like a major problem to me, since it means you can't run a game with PUAP_SCRIPT_CHANGE enabled on the phone.in Xcode, select the target (Torque Game Builer or TGBGame release or debug versions depending on what you are testing on), then select the Info icon. Once that window opens up, select the Build tab, then scroll down to the preprocessor stuff.
Employee Michael Perry
ZombieShortbus
I'll remove the bug flag for this one.