🚀 go-pugleaf

Hi,

I went ahead and did the upgrade. I needed to because my application needed
to be "Mach-O" to access the serial ports easily. Well I thought it would be
easier to just build the OS X version as Mach-O, and the pre OS-X as a
non-carbon app. Getting mach-o has been tougher than I thought.

First, the mach-o tools seem to do a much much better job with the header
files. After fixing some c++ template related problems and a few other code
fixes, I got the code to compile using the mach-o tools.

There were a few issues:

When debugging, some pointers display as @R## (register?) values. When you
try to dereference them using the expanding arrow you get an error message
(don't remember the exact wording but it was something like "value is
offset..."

Another problem with the debugger is it cannot seem to find all my source
files. I think it has something to do with the way my source files are
structured. My source files are stored in a hierarchical directory
structure. The structure seems to work fine when building but for some
reason the debugger cannot find a file that is near the bottom of the
hierarchy. When I try to set breakpoints in this file in the IDE, the
breakpoints are a dull red.  When I do the same thing with a file that the
debugger CAN find, the breakpoints are a deep dark red. The debugger will
stop at the deep dark red breakpoints but not on the dull red breakpoints.

Also, the "step over" sometimes "steps into".

This is making debugging my application a bit difficult.


Adam Skwersky
askwersky@worldnet.att.net