Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 370325

Summary:	Bundle-NativeCode does not work if List of dlls is to Long
Product:	[Eclipse Project] PDE	Reporter:	Jens Schmidt <jens.schmidt>
Component:	UI	Assignee:	PDE-UI-Inbox <pde-ui-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	major
Priority:	P3	CC:	curtis.windatt.public
Version:	3.7.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Jens Schmidt

2012-02-01 09:29:12 EST

Build Identifier: 20110916-0149

While working with a TP the Bundle-NativeCode directive works fine.
But if you try to start the Plugin natively (without the Developer Eclipse)
the OSGi - Console displays the following Error:

"The Bundle [...] could not be resolved. Reason: The native code paths cannot be found: [...]"

This error Occurs if you try to load many dlls.
In my example 54.


Reproducible: Always

Steps to Reproduce:
1. Setup a Target Platform
2. create a new Plugin
3. Bundle-NativeCode about 50dlls
4. start TP in debug Mode -> works
5. close TP
5. start eclipse with -console
6. type: install PluginWhichYouJustCreated
7. output: Bundle id is someNumber
7. type: start someNumber
8. output: aforementioned Error

Comment 1 Jens Schmidt

2012-02-01 10:12:45 EST

correction: this is NOT because the list of dlls is to long.
the error was partialy on my side because of a 
lowercase/upercase mixup.
oddly enough the TP did work an loaded the dll ...

Comment 2 Curtis Windatt

2012-02-01 14:28:23 EST

(In reply to comment #1)
> correction: this is NOT because the list of dlls is to long.
> the error was partialy on my side because of a 
> lowercase/upercase mixup.
> oddly enough the TP did work an loaded the dll ...

Does this mean you are no longer having a problem? I currently do not have time to investigate this, please try and track down the cause in PDE.

Comment 3 Jens Schmidt

2012-02-14 08:40:10 EST

In a sense yes, the problem was resolved.

Maybe I clarify:
- Asume you hava a Plugin which needs some native code let's call that "someNativeLibrary.dll"
- You use the bundle-nativecode stanza 
- but supply the name "somenativelibrary.dll" (<- this was my original error)
- You load with System.loadLibrary("someNativeLibrary");

If you debug you Plugin with a target platform it will work this way.
If you export your Plugin and start your RCP it will not work.

IMHO either it should work in both cases or in none, this way it is very confusing.

Comment 4 Eclipse Genie

2019-09-23 09:45:10 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.