Re: no rule to process file
Re: no rule to process file
- Subject: Re: no rule to process file
- From: Ivan C Myrvold <email@hidden>
- Date: Fri, 9 Jun 2006 22:41:51 +0200
I found out that if I quit Xcode after building the Java file in step
15, and open the project again, the MyTest under the Products group
has changed icon from toolbox to a teacup icon, and also with the
extension .jar. This must be a bug in Xcode 2.3.
I changed the images in step 21 and 22 to show this (I didn't bother
to change the other images).
1) Confirm that there is a MyTest.jar, with the correct spelling,
in the
correct place.
Ivan-C-Myrvolds-MacBook:~ imyrvold$ ls -al /Users/imyrvold/Documents/
Cocoa/MyTest/build/Debug/MyTest.jar
-rw-r--r-- 1 imyrvold imyrvold 837 Jun 9 22:11 /Users/imyrvold/
Documents/Cocoa/MyTest/build/Debug/MyTest.jar
Ivan-C-Myrvolds-MacBook:~ imyrvold$
2) Confirm that MyTest.jar is indeed a jar-file. Use a:
jar tf path-to-jar.jar
command in Terminal to list the file's contents.
Ivan-C-Myrvolds-MacBook:~ imyrvold$ jar tf /Users/imyrvold/Documents/
Cocoa/MyTest/build/Debug/MyTest.jar
META-INF/
META-INF/MANIFEST.MF
MyJava.class
Ivan-C-Myrvolds-MacBook:~ imyrvold$
3) Confirm that Info.plist in the app-bundle contains the 3 needed
NSJava*
keys. Copy and paste their names and values to an email message
and post
it, so I can compare to a known-working Cocoa-Java app I have here.
<key>Java</key>
<dict>
<key>JVMVersion</key>
<string>1.3+</string>
</dict>
<key>NSJavaNeeded</key>
<string>YES</string>
<key>NSJavaPath</key>
<array>
<string>MyTest.jar</string>
</array>
<key>NSJavaRoot</key>
<string>Contents/Resources/Java</string>
4) Confirm that the spelling of MyTest.jar in the classpath key
exactly
matches the file-name of #1.
If your old PPC project works, I suggest starting with that and
getting it
to build correctly for just the native architecture first. After that
works, then convert it.
Yes, I will try that
What you're doing now has too many variables and too many unknowns,
so it's
impossible to say what's wrong or why. Start simple, make that
work, and
only then start changing things, and only one thing at a time.
Also, rebuild at every conceivable point along the way, even if the
code is
just stubs. If you change too many things without doing a rebuild,
you can
dig yourself into a hole without knowing you've done so. You're
not just
debugging your program, you're debugging your build process, too.
Thanks for your help. I have learned a lot about Xcode these couple
of days. I am not giving up easily, and eventually I hope to get this
working.
Ivan
-- GG
_______________________________________________
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
_______________________________________________
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