Re: conversion of a PowerPC dylib to a universal dylib
Re: conversion of a PowerPC dylib to a universal dylib
- Subject: Re: conversion of a PowerPC dylib to a universal dylib
- From: Don Clark <email@hidden>
- Date: Thu, 9 Mar 2006 14:53:54 -0500
| Daniel, thanks for the reply and suggestions. The file tool reports "libOLocale.jnilib: current ar archive".
I set up certain fields as follows: Architectures $(NATIVE_ARCH) Mach-O Type Dynamic Library Product Name OLocale Executable prefix lib Executable Extension jnilib Mac OS X Deployment target Mac OS X 10.4
Setting up the name, prefix and extension as above cured the '.a' extension, but the file type of the resulting file still isn't dylib.
I went back and built the version of the project from before executing the Upgrade All Targets... command - that project builds and the JNI lib works with my Java app. It's only the Upgraded project that fails.
/Don On Mar 9, 2006, at 11:56 AM, Daniel Jalkut wrote: Don - can you examine the resulting binary to see if it is in fact a static or a dynamic library? The "flie" command from the command line should let you see this.
When you removed the "a" from executable extension, did you delete the build setting? (is it still bold?) If not, select the (now blank) setting and hit the delete key. You should see it turn from bold to plain. It sounds like you have inadvertently instructed Xcode to add an extension "" to your resulting binary. You may want to define this extension as "jnilib" since it's going to end up being that eventually anyway.
Daniel
On Mar 8, 2006, at 1:47 PM, Don Clark wrote:
I have a Java Native Interface (JNI) dylib project that built with Xcode 2.2 before being converted using the "Upgrade All Targets in Project to Native". Now the project builds a static library with .a extension. In the Project Settings the Mach-O type is specified as Dynamic Library, and now I have removed the "a" from the Executable Extension field, but the library is now named with a trailing "." (that would precede the "a" if it was still there). It appears that some option isn't set correctly, to produce a dylib with the specified name - note that Java loads JNI dylibs with the expectation that the name is libLibrary-Name-Here.jnilib Does anyone have any idea of why the dylib project now builds what appears to be a static library?
|
_______________________________________________
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