Differences between Cocoa and Cocoa-Java Projects/Targets
Differences between Cocoa and Cocoa-Java Projects/Targets
- Subject: Differences between Cocoa and Cocoa-Java Projects/Targets
- From: Phil <email@hidden>
- Date: Thu, 17 Feb 2005 03:52:01 +1300
Hi,
I'm building a primarily Obj-C Cocoa application, but using a Java
library (via. the bridge), so I've created a Cocoa-Java project.
However, I'm unsure as to how this is altering my project. I've
noticed that:
- I can write/compile/run Obj-C code just fine, as if there's no
difference between this and a normal application.
- Instead of a normal Application target, it is a Java Application target.
-- The Java Application target has an editor that you don't get with
the normal Application target.
It has some of the common configuration options for gcc and javac.
It has forms for the Info.plist file with the Java information
already completed
It has an additional Java Resources build phase
You can't get the regular Target Info inspector window, and can't
set dependencies (as far as I can see).
- The built products seem to be exactly the same (except it loads the
JVM at runtime, but you can turn that off in the Info.plist)
So, my questions are -
a) Why is there a different target editor for a Cocoa-Java application
and why isn't it available for a regular Cocoa application?
b) In fact, why is it a different target type? Shouldn't the only
difference be the addition of the "NSJava*" keys to Info.plist?
c) What exactly is the difference between these two projects (other
than what I've already discovered)?
Thanks,
Phil
--
Phil <email@hidden>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden