Re: no rule to process file
Re: no rule to process file
- Subject: Re: no rule to process file
- From: Greg Guerin <email@hidden>
- Date: Fri, 9 Jun 2006 11:11:05 -0700
Ivan C Myrvold wrote:
>This time I started with a Cocoa-Java Application project. But as you will
>see at step 30, the
>
> id javaObject = [[NSClassFromString(@"MyJava") alloc] init];
>
>will not create the javaObject. It will be nil.
>
>Why is not this working? My old PPC project I started developing in 2002,
>still works on my PPC machines, and the above command creates the Java
>object correctly.
At this step:
21. Drag MyTest jar file from Products group to the Copy Files Phase Path
the icon for the MyTest build product is a tiny toolbox, not a coffee-cup
rectangle. Also, at step 22, the pathname shown in the box doesn't have a
".jar" suffix. These two things, the icon and the lack of suffix, me think
it's a dylib or an executable file, not a jar-file, you're copying.
For the icon, I'm judging by what I see in my Cocoa-Java project under
Xcode 2.2.1. Since I don't know which versions you're using, maybe jars
have the toolbox icon for you. If they don't, then maybe it's the wrong
file.
Also check these things in your built app-bundle, to confirm the correct
things are being put in place.
1) Confirm that there is a MyTest.jar, with the correct spelling, in the
correct place.
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.
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.
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.
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.
-- 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