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
JavaCL is missing OSGi support #283
Comments
Any news on this? I am stuck with this too |
This would be a tremendous help to have fixed for me as well! OSGi support FTW |
Sorry wrong button :) Was checking if there were any updates... |
…NAPSHOT) and JavaCL (1.0-SNAPSHOT) Added OSGi projects for BridJ and JavaCL (issue #283)
Hi @tarelli , Sorry about the delay ! (you can download it here : https://oss.sonatype.org/content/groups/public/com/nativelibs4java/javacl-osgi) Please let me know if it works correctly in your container. Cheers |
Hi Olivier, [2012-05-15 18:49:00.209] ERROR Thread-69 org.bridj.BridJ Failed to load 'bridj' java.io.FileNotFoundException: bridj [2012-05-15 18:49:00.234] ERROR Thread-69 System.err java.lang.RuntimeException: Failed to initialize BridJ Do you have any idea what is happening? Looks like bridj is not found at runtime. |
Hi @tarelli , Thanks for your work and sorry for the delay. This error would seem to indicate that Platform.extractEmbeddedLibraryResource failed. That method is responsible for getting the native bridj library (bridj.dll, libbridj.so, libbridj.dylib) from the org/bridj/lib/xyz embedded resource path (where xyz is win32, win64, linux_x86, etc...). Cheers |
Hi @ochafik , |
Hi @tarelli , Sorry for not being able to solve the issue yet :-S It's available here : Regarding the attachment of sources, I'm afraid javacl-osgi-sources.jar only contains the bundle activator and not an aggregation of all the dependencies' sources. For that you'll have to find the jars for sources of BridJ & JavaCL (in your case, BridJ should be enough) : I'll have a closer look at how to reproduce in Eclipse tomorrow, any pointers and/or executable demos are welcome ! |
Hi @ochafik , |
Wow - this is huge, mad props to @ochafik! :) |
Hehe, my pleasure ! Cheers |
The Import package directive fails when javacl is added to a manifest file:
Import-Package: com.nativelibs4java.opencl [0.0.0, oo) could not be resolved MANIFEST.MF
Import-Package: com.nativelibs4java.util [0.0.0, oo) could not be resolved MANIFEST.MF
The text was updated successfully, but these errors were encountered: