Description of the generated jars

Hello,

I am currently trying to package Jogl & Gluegen into Debian/Ubuntu and I have some problems to find out which jar is doing what and how they work together (in order to separate them in packages).

Is there a description of use cases of the following jars ?
gluegen-gl.jar
jogl-natives-linux-amd64-cdc.jar
jogl-natives-linux-amd64.jar
jogl.all-noawt.jar
jogl.all.cdc.jar
jogl.all.jar
jogl.awt.jar
jogl.core.cdc.jar
jogl.core.jar
jogl.egl.cdc.jar
jogl.egl.jar
jogl.gldesktop.dbg.jar
jogl.gldesktop.jar
jogl.gles1.cdc.jar
jogl.gles1.dbg.cdc.jar
jogl.gles1.dbg.jar
jogl.gles1.jar
jogl.gles2.cdc.jar
jogl.gles2.dbg.cdc.jar
jogl.gles2.dbg.jar
jogl.gles2.jar
jogl.glu.gldesktop.jar
jogl.glu.mipmap.cdc.jar
jogl.glu.mipmap.jar
jogl.glu.tess.cdc.jar
jogl.glu.tess.jar
jogl.os.osx.jar
jogl.os.win.jar
jogl.os.x11.jar
jogl.sdk.jar
jogl.test.jar
jogl.util.awt.jar
jogl.util.cdc.jar
jogl.util.fixedfuncemu.cdc.jar
jogl.util.fixedfuncemu.jar
jogl.util.gldesktop.jar
jogl.util.jar


By the way, what means cdc ?

Thanks
S

Hello,

you can find a short description on the wiki (http://jogamp.org/jogl/doc/deployment/JOGL-DEPLOYMENT.html).

e.g a possible full-functionality setup would look like:

jars...
 - nativewindow.all.jar
 - jogl.all.jar
 - newt.all.jar

natives (please extract jars, must be in lib path)...
 - jogl-natives-linux-<arch>.jar
 - newt-natives-linux-<arch>.jar
 - nativewindow-natives-linux-<arch>.jar

JOGL depends on gluegen-rt which would be:
jars...
 - gluegen-rt.jar

natives (please extract once again)...
 - gluegen-rt-natives-linux-<arch>.jar

for completeness: JOCL also requires gluegen-rt:
jars...
- jocl.jar

natives...
- jocl-natives-linux-<arch>.jar

cdc stands for connected device configuration (mobile).

hope that helps a little bit,

best regards,

michael

On 12/05/2010 04:53 PM, sylvestre [via jogamp] wrote:

Hello,

I am currently trying to package Jogl & Gluegen into Debian/Ubuntu and I have some problems to find out which jar is doing what and how they work together (in order to separate them in packages).

Is there a description of use cases of the following jars ?
gluegen-gl.jar
jogl-natives-linux-amd64-cdc.jar
jogl-natives-linux-amd64.jar
jogl.all-noawt.jar
jogl.all.cdc.jar
jogl.all.jar
jogl.awt.jar
jogl.core.cdc.jar
jogl.core.jar
jogl.egl.cdc.jar
jogl.egl.jar
jogl.gldesktop.dbg.jar
jogl.gldesktop.jar
jogl.gles1.cdc.jar
jogl.gles1.dbg.cdc.jar
jogl.gles1.dbg.jar
jogl.gles1.jar
jogl.gles2.cdc.jar
jogl.gles2.dbg.cdc.jar
jogl.gles2.dbg.jar
jogl.gles2.jar
jogl.glu.gldesktop.jar
jogl.glu.mipmap.cdc.jar
jogl.glu.mipmap.jar
jogl.glu.tess.cdc.jar
jogl.glu.tess.jar
jogl.os.osx.jar
jogl.os.win.jar
jogl.os.x11.jar
jogl.sdk.jar
jogl.test.jar
jogl.util.awt.jar
jogl.util.cdc.jar
jogl.util.fixedfuncemu.cdc.jar
jogl.util.fixedfuncemu.jar
jogl.util.gldesktop.jar
jogl.util.jar


By the way, what means cdc ?

Thanks
S

---

View message @ http://jogamp.762907.n3.nabble.com/Description-of-the-generated-jars-tp2022761p2022761.html
To start a new topic under jogamp, email [hidden email]
To unsubscribe from jogamp, click here.

-- 
http://michael-bien.com/

On Sunday, December 05, 2010 16:53:59 sylvestre [via jogamp] wrote:
>
> Hello,
>
> I am currently trying to package Jogl & Gluegen into Debian/Ubuntu and I have some problems to find out which jar is doing what and how they work together (in order to separate them in packages).
>
> Is there a description of use cases of the following jars ?

http://jogamp.org/jogl/doc/deployment/JOGL-DEPLOYMENT.html

>
>
> By the way, what means cdc ?

old mobile stuff .. see:

http://jogamp.org/deployment/jogamp-next/javadoc/jogl/javadoc/overview-summary.html#overview_description
http://java.sun.com/javame/technology/cdc/

>
> Thanks
> S

~Sven

sylvestre wrote

I am currently trying to package Jogl & Gluegen into Debian/Ubuntu

Good idea :)

Hello

Thanks for your answer.

For information, gluegen2 has been accepted into Debian. I am now packaging Jogl2.

I have a question regarding the URL your sent.

In the section "Platform (mandatory)", in the subsection:
"JOGL [pick your platform]:"
    * jogl.egl.jar
=> what is egl ?
Does it replace jogl.os.x11.jar or should it be shipped with ?

thanks

On Friday, February 25, 2011 11:50:21 sylvestre [via jogamp] wrote:
so you have decided not to use *all* jar's .. well :)

    * jogl.egl.jar       EGL
    * jogl.os.x11.jar    GLX
    * jogl.os.win.jar    WGL
    * jogl.os.osx.jar    CGL

the platform GL bindings, where EGL is for the khronos abstract EGL one,
usually used on mobile for ES1 or ES2 or SVG ..

~Sven
>
> thanks

> so you have decided not to use *all* jar's .. well :)
Indeed ! I have to factorize this in the packaging system and therefor avoid duplication of jars ...

Thanks for the information.

  do you plan to add JOCL too?

-michael

On 02/25/2011 11:50 AM, sylvestre [via jogamp] wrote: --
http://michael-bien.com/

I  am not planning to use JOCL (while I am a strong user of JOGL) but it won't be the first time I package a software that I am not really using.
I have two questions if I am going in this direction:
* How hard is it to build compare to JOGL 2 ?
* Will you provide help ?

PS: To tell you the truth, I was planning to have a least a look to make sure that my packaging of gluegen2 is not "JOGL2 only".

  sure i would help. Its in our interest to make the projects available.

building:
as soon you have built jogl, its quite easy to build jocl.

http://jogamp.org/jocl/doc/HowToBuild.html

I haven't tested it yet but it should be possible to build jocl without
having a OpenCL SDK/driver installed.

best regards,
michael

On 02/28/2011 04:10 PM, sylvestre [via jogamp] wrote:

On Monday, February 28, 2011 16:10:46 sylvestre [via jogamp] wrote:
>
> I  am not planning to use JOCL (while I am a strong user of JOGL) but it
> won't be the first time I package a software that I am not really using.

Sounds all great .. thank you very much for your efforts.

Would it be feasible to add a debian packaging script to our 'jogamp-scripting'
folder?
'jogamp-scripting' is next to the other git stuff of ours,
holding all our final deployment magic.

In such case, we could create debian packages on the fly when we aggregate and sign,
where you can cherry pick and maintain this 'procedure'.
Would be awesome IMHO.

Cheers, Sven