Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LIBRARY_PATH is error #2

Open
killme2008 opened this issue Oct 21, 2011 · 5 comments
Open

LIBRARY_PATH is error #2

killme2008 opened this issue Oct 21, 2011 · 5 comments

Comments

@killme2008
Copy link

LIBRARY_PATH should be

private static String LIBRARY_PATH = "/data/data/" + PACKAGE_NAME + "/lib";

It is not in app folder on my i9100.

@paddybyers
Copy link
Owner

I agree lib is the right place - but that's only OK if you can persuade Android to extract the library there automatically on installation. I'm not sure how you do this - for me it was working sometimes but not always.

So I put the lib in app, and have code there to programmatically extract it when it is first loaded. You can't do this in lib because the lib directory is owned by root and not by the app, and you can't put things in there programmatically.

If you can figure out why it's not always being extracted to lib automatically, then great.

Thanks

@skabbes
Copy link
Contributor

skabbes commented Jan 11, 2012

If you place the lib in APP_ROOT/lib/armeabi/libjninode.so, then the library will automatically be be placed in the correct library location of your app.

Then you can use System.loadLibrary("jninode") instead of System.load("/path/to/lib"). This is how Android NDK apps load shared libraries afaik. This doesn't solve the problem of how to load bridge.node, but it is at least a start.

@paddybyers
Copy link
Owner

Hmm, fancy doing a PR for it? :)

@skabbes
Copy link
Contributor

skabbes commented Jan 11, 2012

Yep, I'll look into it later today.

@paddybyers
Copy link
Owner

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants