Re: WO5.2 and Dec 2002 Mac OS X Developer Tools
Re: WO5.2 and Dec 2002 Mac OS X Developer Tools
- Subject: Re: WO5.2 and Dec 2002 Mac OS X Developer Tools
- From: Art Isbell <email@hidden>
- Date: Wed, 18 Dec 2002 14:11:05 -1000
On Wednesday, December 18, 2002, at 10:59 AM, email@hidden wrote:
Daniel Muller wrote:
On 16.12.2002, at 20:00, Art Isbell wrote:
On Monday, December 16, 2002, at 02:50 AM, Daniel Muller wrote:
It seems to work well, all my applications run without a glitch...
except that I'm unable to use the debugger... even a new project
runs
without to stop to breakpoints!!
Make sure the project's debugger is set to the Java debugger rather
than gdb.
Thank your for your suggestion but it was set as "jdb" by default. I
tried gdb but same things happened.
Try making the same debug settings for ALL targets.
I was having problems getting deprecated API listings, until I turned
it on for all three targets (App, Application Server and Web Server).
It was definitely turned on for the target I was building, but I had
no luck until it was on for ALL THREE targets.
The top-level target seems to be little more than a "pseudo-target"
that merely results in both the Application Server and Web Server
targets being built. If the Application Server and Web Server targets
are removed from the top-level target and the top-level target is
built, it will create a "build" directory containing several
directories and files, but they appear to be only the standard generic
directories and files that exist in all WO app projects. There doesn't
appear to be anything specific to the current project because the
project files aren't usually associated with the top-level target.
If the Application Server target is built, it seems to populate the
"build" directory with files that are associated with the Application
Server target (d'oh!) but it doesn't build the product's directory
structure (e.g., *.woa). So building the top-level target seems like
the correct way to build products. I'm not sure when, if ever, it
would make sense to build the Application Server or Web Server targets.
I don't know how the various settings of the various targets interact.
I suppose they're independent of one another. If so, then I would
think that setting the compiler to warn about deprecated API only in
the Application Server target would suffice assuming that your source
files are associated with the Application Server target as is the usual
case. But I haven't tried various scenarios. PBX is a complex beast
that's probably very powerful once fully understood.
Mind you, this is with the dev tools that Ship with WO 5.2. I haven't
been able to find these December 2002 ones - are they available for
Select Members and above from the Developer Website only??? I am only
an onliner...
I think they are available only to those who are registered to receive
pre-release software seeds. I'm not registered to receive software
seeds and I can't find any mention of the Dec 2002 Dev tools when I log
on to my ADC account. I think those who apply for these software seeds
agree not to discuss them in public, but there appear to be some loose
lips in this forum. Apple is undoubtedly monitoring this forum, so if
I wanted to receive future software seeds, I'd keep my mouth shut.
YMMV :-)
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.