Re: [Java-gnome-developer] (Hacked) version of 4.0.13 in Maven repo

[Jacek F. <ja...@gm...>]

Yes, but that would create an artifact called org-gnome-libgtkjni-4.0.13.so,
which would not load (since Plaform.loadNative() expects the standard naming
format only). And it must be in the same folder as the jar, otherwise it
wouldn't load either.

Embedding the .so in the jar seemed the best idea (that's how SWT does it),
but requires the unfortunate patch. I tried a lot of different Maven tricks,
but the hardcoded requirement of a particular file name in a particular
folder was always the deal breaker....

I am not too happy about having to patch the code to get this to work and I
have a gut feeling Andrew likes it even less...any alternate suggestions
would be therefore welcome.

On Sun, Nov 15, 2009 at 6:36 AM, Stefan Schweizer <ste...@gm...
> wrote:

> On Fri, 2009-11-13 at 12:37 -0500, Jacek Furmankiewicz wrote:
> > I added the dependency on the utility mentioned in this entry and
> > modified loadNativeCode() to attempt loading the .so  directly from
> > the jar's META-INF/lib (which is how I deploy it in the Maven repo).
>
> Have you tried declaring the libgtkjni.so as separate artifact with type
> 'so'? I think something like this could work:
>
> <dependency>
>        <groupId>org.gnome</groupId>
>         <artifactId>libgtkjni</artifactId>
>         <version>4.0.13</version>
>         <type>so</type>
> </dependency>
>
>
>        Stefan
>
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> java-gnome-developer mailing list
> jav...@li...
> https://lists.sourceforge.net/lists/listinfo/java-gnome-developer
>