Debugging Xcomps

Kelly Burgess kellyb at montana.com
Thu Apr 23 22:23:21 EDT 2009


Hi Scott,

I don't use Visual Studio, but XCode is easy to set up for debugging.

1. add a new 'copy files build phase' to the target, at the end of 
the other build phases.  Specify the absolute path of the Studio 
xcomp folder - e.g. "/Applications/Omnis Studio 
4.2/Omnis.app/Contents/MacOS/external/" - so that after your target 
is successfully built (in your common output folder, e.g. 
/Developer/Projects/_OSXDebug), the finished xcomp will then be 
copied into the xcomp folder of the Studio you're going to test it 
with.

2. add a new 'custom executable' to the executables node below the 
target node, give it a name like 'Studio42', and specify the absolute 
path of Studio, e.g. "/Applications/Omnis Studio 4.2/Omnis.app".  You 
can have several of these, allowing you to test with different 
versions of Studio.  A menu lets you select the 'active executable' 
from among the choices before you build.

Once XCode knows what the executable is, it should allow you to build 
and debug.  Note that you need to use the 'Development' setting for 
the Active Build Configuration.  You can't debug a 'Deployment' 
build, which contains both PPC and Intel code.  The 'Development' 
build will only contain one of those two, depending on the 
architecture you're using to build the target.  If you're running 
your code and not able to hit your assigned breakpoints, it's usually 
because you've switched to building the Deployment config.

A build-and-go should build the development xcomp, copy it into the 
Studio xcomp folder, and launch Studio.  From there, you open your 
test library and invoke the code that leads to your breakpoint.

Hope that helps,

Kelly



More information about the omnisdev-en mailing list