Eclipse PDE UI 功能导出具有相同操作系统、不同架构的两个片段
希望有一些 Eclipse PDE 专家来解决我遇到的问题。
我正在尝试导出(通过 PDE UI)一个包含两个片段的功能,其中两个片段都针对相同的操作系统(例如 Linux),但具有不同的体系结构值(例如 x86 和 x86_64)。每个片段都有自己的多个 .so 库文件副本,这些文件是在 Linux x86 或 Linux x86 64 位上构建的。例如:
FragmentA (os=Linux,arch=x86)
lib1.so
lib2.so
lib3.so
FragmentB (os=Linux,arch=x86_64)
lib1.so
lib2.so
lib3.so
使用相应的增量包导出托管功能以选择 linux (gtk/x86) OR linux (gtk/x86_64),导出按预期工作。但是,当我选择 BOTH 平台时,导出失败并显示以下消息:
Processing inclusion from feature com.sample.feature:
Bundle com.sample.linux.x86_64_1.0.0.qualifier failed to resolve.:
Unsatisfied native code filter:
lib1.so; lib2.so; lib3.so; processor=x86_64; osname=linux.
为什么我不能同时导出两个片段?我还有一个 Win32 x86 片段,我可以使用 linux X86 功能导出它,但它没有 .so 文件,而是具有相同文件标题的 .dll 文件(例如,lib1.dll、lib2.dll、lib3.dll)。
在两个基于 Linux 的片段中具有相同名称的 .so 库文件是否会导致此问题?
任何帮助将不胜感激,因为这是我们构建过程的关键块(通过 UI 手动和无头)。
Hoping to have some Eclipse PDE guru's weigh in here in a problem I'm having trouble solving.
I am attempting export (via PDE UI) a feature that has two fragments included where both fragments target the same os (e.g., Linux) but have different architecture values (e.g., x86 and x86_64). Each fragment has their own copy of several .so library files, which were built on the either Linux x86 or Linux x86 64 bit. For example:
FragmentA (os=Linux,arch=x86)
lib1.so
lib2.so
lib3.so
FragmentB (os=Linux,arch=x86_64)
lib1.so
lib2.so
lib3.so
Exporting the hosting feature with using the corresponding delta pack to select either linux (gtk/x86) OR linux (gtk/x86_64), the export works as expected. However, when I select BOTH platforms, the export fails with the following message:
Processing inclusion from feature com.sample.feature:
Bundle com.sample.linux.x86_64_1.0.0.qualifier failed to resolve.:
Unsatisfied native code filter:
lib1.so; lib2.so; lib3.so; processor=x86_64; osname=linux.
Why can't I export both fragments together? I also have a Win32 x86 fragment that I can export with the linux X86 feature but instead of having .so files, it has .dll files with the same file titles (e.g., lib1.dll, lib2.dll, lib3.dll).
Could having .so library files named the same in the two Linux-based fragments cause this issue?
Any help would be much appreciated as this is a critical block to our build process (both manually via the UI and headlessly).
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论