Shared target platform, debugging, and multiple dev platforms [message #593370] |
Wed, 18 March 2009 16:54 |
Eric Rizzo Messages: 3070 Registered: July 2009 |
Senior Member |
|
|
[Sorry for the cross-post, but I'm not sure which audience is most
likely to be able to help]
Our team uses a shared (in CVS) target platform. This target includes
the Eclipse SDK (3.4.1) and a lot of other features/plugins. It includes
the SWT source plugins for both win32 and macosx.
The problem is when debugging on OS X. During coding, navigating the
code for SWT classes works correctly, it uses the macosx source plugin
and displays the OS X specific code. But when debugging, the debugger is
using the win32 source code instead, even though what is executing is
(obviously) the macosx code. It results in the debugger line numbers not
aligning properly with the displayed source files.
The launch configuration we use for launching our app on Mac
specifically excludes all win32 SWT plugins and specifically includes
the macosx SWT source and binary plugins.
So what is the proper way to set up a dev environment that uses a shared
target platform and will debug properly on both Windows and Mac?
Any help appreciated,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.02707 seconds