Re: ZipException when loading native jars
Posted by Sven Gothel on Dec 05, 2012; 7:51pm
URL: https://forum.jogamp.org/ZipException-when-loading-native-jars-tp4027387p4027422.html
On 12/05/2012 08:45 PM, ryanmohr [via jogamp] wrote:
> Sven Gothel wrote
> .. plus my other reply regarding the proprietary status of that method.
> I would not dare to include a blob in my project, depending on some weirdo
> deployment and maybe even market scheme :)
>
> Exactly! The only reason we're willing to go to the work of writing a custom
> deployment process is to remove or internalize as many variables as possible.
>
> We need to be able to guarantee that the application we send to our customers
> just works (to the point that we'll soon be giving customers the option to
> have the JRE embedded, removing one more variable that's given our customers
> problems in the past).
>
> Sven -- I'm giving your suggestions a go right now. Will let you know if I
> make any progress. Appreciate the guidance!You are welcome, ofc.
Pls simply share the onejar demo project (via git/github, as you wish)
and we can make an assessment whether it's a bug of GlueGen.
However, I am sure we can fix the issue.
When you create that project, it might be nice to maybe simply create
it as a jogl-demos sub-project (own folder), w/ our jogamp license,
so we can share your experience ..
~Sven
URL: https://forum.jogamp.org/ZipException-when-loading-native-jars-tp4027387p4027422.html
On 12/05/2012 08:45 PM, ryanmohr [via jogamp] wrote:
> Sven Gothel wrote
> .. plus my other reply regarding the proprietary status of that method.
> I would not dare to include a blob in my project, depending on some weirdo
> deployment and maybe even market scheme :)
>
> Exactly! The only reason we're willing to go to the work of writing a custom
> deployment process is to remove or internalize as many variables as possible.
>
> We need to be able to guarantee that the application we send to our customers
> just works (to the point that we'll soon be giving customers the option to
> have the JRE embedded, removing one more variable that's given our customers
> problems in the past).
>
> Sven -- I'm giving your suggestions a go right now. Will let you know if I
> make any progress. Appreciate the guidance!
Pls simply share the onejar demo project (via git/github, as you wish)
and we can make an assessment whether it's a bug of GlueGen.
However, I am sure we can fix the issue.
When you create that project, it might be nice to maybe simply create
it as a jogl-demos sub-project (own folder), w/ our jogamp license,
so we can share your experience ..
~Sven
signature.asc (909 bytes) | Free forum by Nabble | Edit this page |