Stephan Bergmann <stephan.bergmann <at> sun.com> writes:
>
> Andrew Ziem wrote:
> > Hello,
> >
> > I heard it's easy to package ogltrans as oxt, so I wonder if I am closer
> > to success or closer to exposing my ignorance. :)
> >
> > I have an oxt**, but it fails to load with error like
> > (com.sun.start.lang.DisposedException) {{{Message = "URP_Bridge :
> > disposed\X000a(tid=22) Unexpected connection closure", Context =
> > (com.sun.star.uno.XInterface) @0}}}.
> >
> > Basically, I did this:
> > 1. Compile OOH680_m12 with --enable-ogltrans --enable-opengl
> > 2. regcomp -register -r ogltrans.rdb -c libOGLTrans.uno.so
Hi Stephen. Thanks for your reply.
> Step 2 is not necessary. It is the Extension Manager (or alternatively
> the unopkg command line tool) that will register your extension's UNO
> component library with OOo's services registry. The additional
> ogltrans.rdb is at best harmless, and at worst a source of errors.
OK. At first, I didn't do it.
> > 3. createExtPackage.pl ogltrans.oxt *rdb *so
>
> No idea what createExtPackage.pl does, sorry.
In the OOo 2.4.0 source tree, it .zips a few files with a manifest to make it an
.oxt. I think oovbaapi uses it.
> > 4. Try to load in OOo 2.4.0 Linux vanilla.
>
> The libOGLTrans.uno.so in your extension does not only link against URE
> libraries, but also against OOo's libvcl680li.so, libcomphelp4gcc3.so,
> and libcanvastools680li.so. That means that it will only work against
> very specific versions of OOo, if it works at all (see
> <http://porting.openoffice.org/servlets/ReadMsg?list=mac&msgNo=6872>).
Hmm. I see neither an easy way to remove all these dependencies (such as vcl)
nor a replacement. It seems the OpenGL transitions (touted for OOo 2.4) are in
the same situation as oovbaapi.
Andrew
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
