THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 07/02/2007 at 05:13, xxxxxxxx wrote:
oh man, this XCode drives me nuts (maybe it´s simply me). How can I debug my app? I created a new custom executable, linked that to my project and have set the executable path to the location of my generated .dylib (btw. how can I let XCode output the final .dylib into a different location?).
XCode does give me the options of "Debug" and "Build and Debug" but of course when it tries to start it cannot because it cannot start the dylib and I cannot find any place to set the Cinema 4D path.
And actually I have no clue how XCode handles the plugin debugging situation.
So any help is very appreciated...Kuro
On 07/02/2007 at 19:12, xxxxxxxx wrote:
Actually, I haven't done any debugging with XCode yet. As noted in the SDK Help forum, I just updated from 2.2.1 to 2.4.1 (and was met with the strangeness mentioned there). At least now it doesn't ask you to run 'ranlib' continuously.
XCode is definitely frustrating. Don't EVER try to replace the api project with just the api lib! I found this out last night - you not only remove the project but all dependencies (i.e.: the compiler/linker settings drop back to defaults!). Luckily, I keep a backup of the project for just such special occassions!
One thing is to make sure that the API project is set to Debug as default before doing a debug build. Don't know how to specify the application to launch when you are building a dylib for one.
On 08/02/2007 at 04:42, xxxxxxxx wrote:
thanks for the info and tips. Yes, it´s not yet the environment it should be I think.
I have already solved my problem but would still like to know how to correctly debug if somebody else may know.
On 08/02/2007 at 09:34, xxxxxxxx wrote:
Some more info.
You can circumvent possible recompilation of the API project by adding the lib_api_release.a and lib_api_debug.a into your plugin's project. Uncheck the API project stuff so that you are only referencing one lib (at a time). Now you get the dependencies while never fearing recompilation of the API libs.
So much for the fix to the problem linking the API lib. Every time I reopen my plugin project, the API project has defaulted back to Debug even though I'm loading the API project and setting the default to Release there directly. Not extremely annoying, but mildly.
On running the debugger, have you checked out Apple and Google for possible answers. I usually haunt the MacOSX dev forums when something eludes me with CodeWarrior or XCode. I've found the latest batch of knowledgeable MacOS developers to be much friendlier and helpful than in the past - probably all of the new devs 'switching' over and porting has softened them up.
On 18/02/2007 at 23:26, xxxxxxxx wrote:
Samir, try this:
_Use the custom Executable part of xcode, put the host application there. (Right click on Executable -- > Add --> New Custom Executable)
Then select this custom executable to be the default launched (Check the radio button).
Put some breakpoint into your program.
Run the Debugger_
The 'host application' would be the Cinema 4D.app.
Though I still don't know how you would copy the finished dylib to the correct location before the debug begins. That ought to be a doozy...
On 19/02/2007 at 03:30, xxxxxxxx wrote:
thank you! However, I also tried that already. I simply cannot find the final button to, as you correctly state, how to get the finished dylib replaced correctly.
I´ll report back when I find out
thx for the heads up!