Re: [dev] Fw: [saxon] Saxon9 and OpenOffice 2.4
Hi Agnisys, the Saxon.jar must be present in your extension - best way to add it during creation of the extension with a zip command. Additionally, the Class-Path: entry in the manifest file of your .jar must reference the saxon9.jar file. Do you use NetBeans to create the extension? Hope that helps, Steffen Agnisys wrote: Hi, Can someone help me run an XSLT transformation using Saxon in an Openoffice 2.4 extension? I get a net.sf.saxon.TransformerFactoryImpl not found error. Thanks, Anupam. - Forwarded Message From: Svante Schubert [EMAIL PROTECTED] To: Mailing list for the SAXON XSLT and XQuery processor [EMAIL PROTECTED] Sent: Friday, August 8, 2008 10:17:28 AM Subject: Re: [saxon] Saxon9 and OpenOffice 2.4 Hi Agnisys, there is usually no Saxon9 in OOo 2.4, therefore you have to add it to your Office extension. Try the dev@openoffice.org list for further details, you are on the wrong mailing list. ;-) For the good news, Saxon9 will be part of OOo 3.0. Many thanks to Michael Kay for his help on this task and of course for the nice processor he provides. Regards, Svante Agnisys wrote: I'm trying to use Saxon9 in an extension created for OO2.4. When running the extension, I get the following error : net.sf.saxon.TransformerFactoryImpl not found My guess is that at run time its not finding the said class. So here are the things I've tried : 1. Added saxon9.jar to CLASSPATH 2. copied saxon9.jar to the program/classes dir in OO2.4 directory structure. 3. copied saxon9.jar to the distribution area of the extension. I still get the same error. Any pointers would be very much appreciated. Thanks, Anupam. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Compiling OOo 3.0 m28 @ OpenSolaris snv_94
Hi, any hints how to solve the below compile problem? Or any hints how to compile OOo [3.0 m28] on OpenSolaris in general? If one does not set CC=cc, OpenOffice seems to prefer GCC even if I set PATH like /opt/SunStudioExpress/bin:/usr/local/bin/:/usr/bin and cc (Sun Ceres C) is the first compiler in my path. The cc that comes with OpenSolaris snv_94's ss-dev package has version 5.10: [EMAIL PROTECTED]:~/oo.org-m28/config_office$ cc -V cc: Sun Ceres C 5.10 SunOS_i386 2008/04/04 usage: cc [ options] files. Use 'cc -flags' for details But OpenOffice wants an older version: checking for cc... /opt/SunStudioExpress/bin//cc checking the SunStudio C/C++ compiler version... configure: error: found version 5.10, use version 5.5, 5.7, 5.8 or 5.9 of the SunStudio C/C++ compiler As cc did not work out for me, I tried the GCC that ships with OpenSolaris: checking the GNU gcc compiler version... checked (gcc 3.4.3) checking gcc linker... configure: error: failed (not GNU ld). Use GNU ld instead of Sun ld on Solaris That's because configure checks the ld used by running: [EMAIL PROTECTED]:~/oo.org-m28/config_office$ gcc -Wl,--version 21 |head -n 1 /usr/ccs/bin/ld: illegal option -- version OpenSolaris does ship with a GNU ld which I could use (in theory) but configure will ignore it: [EMAIL PROTECTED]:~/oo.org-m28/config_office$ /usr/gnu/bin/ld -v GNU ld version 2.15 [EMAIL PROTECTED]:~/oo.org-m28/config_office$ CC=gcc LD=/usr/gnu/bin/ld ./configure --disable-build-mozilla --disable-mediawiki --with-use-shell=bash [...] checking gcc linker... configure: error: failed (not GNU ld). Use GNU ld instead of Sun ld on Solaris For whatever reason, I was brave enough to ignore the equation Solaris = Sun compiler and I have build a new GCC 4.2.2: [EMAIL PROTECTED]:~/oo.org-m28/config_office$ /export/home/nixnutz/gcc/bin/gcc -Wl,--version GNU ld version 2.15 I continued trying to compile OOo and ended with: ./configure --disable-build-mozilla --disable-mediawiki --with-use-shell=bash [...] checking X11/Xaw/Label.h presence... no checking for X11/Xaw/Label.h... no configure: error: Xaw include headers not found [EMAIL PROTECTED]:~/oo.org-m28/config_office$ pfexec pkg search -r Xaw INDEX ACTIONVALUE PACKAGE basename dir usr/X11/include/X11/Xaw pkg:/[EMAIL PROTECTED] basename dir usr/X11/include/X11/Xaw pkg:/[EMAIL PROTECTED] basename dir usr/X11/share/X11/doc/hardcopy/Xaw pkg:/[EMAIL PROTECTED] basename dir usr/X11/share/X11/doc/hardcopy/Xaw pkg:/[EMAIL PROTECTED] basename dir usr/X11/share/X11/doc/hardcopy/Xaw pkg:/[EMAIL PROTECTED] [EMAIL PROTECTED]:~/oo.org-m28/config_office$ pfexec pkg install FSWxorg-headers Nothing to install in this image (is this package already installed?) [EMAIL PROTECTED]:~/oo.org-m28/config_office$ pfexec pkg info FSWxorg-headers Name: FSWxorg-headers Summary: State: Installed Authority: opensolaris.org (preferred) Version: 0.5.11 Build Release: 5.11 Branch: 0.94 Packaging Date: Mon Jul 21 19:04:46 2008 Size: 0 B FMRI: pkg:/[EMAIL PROTECTED],5.11-0.94:20080721T190446Z Looks like an OpenSolaris matter to me: [EMAIL PROTECTED]:~/oo.org-m28/config_office$ ls /usr/X11/include/X11/Xaw ls: cannot access /usr/X11/include/X11/Xaw: No such file or directory Any hints are welcome! Thanks! Ulf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Compiling OOo 3.0 m28 @ OpenSolaris snv_94
Hi Ulf, *,
On Tue, Aug 12, 2008 at 3:45 PM, Ulf Wendel [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ cc -V
cc: Sun Ceres C 5.10 SunOS_i386 2008/04/04
usage: cc [ options] files. Use 'cc -flags' for details
But OpenOffice wants an older version:
I doubt that. (and if I'm wrong: The guy/gal who wrote the config
check should have added an appropriate comment in that case).
checking for cc... /opt/SunStudioExpress/bin//cc
checking the SunStudio C/C++ compiler version... configure: error: found
version 5.10, use version 5.5, 5.7, 5.8 or 5.9 of the SunStudio C/C++
compiler
The configure check is like that:
_sunstudio_minor=`echo $_sunstudio_version | $AWK -F. '{ if ($2 == 5)
print true; else if ($2 == 7) print true; else if ($2 == 8) print
true; else if ($2 == 9) print true; else print false }'
So from my understanding two-digit minor versions have just not taken
into account at all.
I'd suggest forcing that check to true and try with the 5.10 compiler.
[building with gnu cc also requires gnu ld]
OpenSolaris does ship with a GNU ld which I could use (in theory) but
configure will ignore it:
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ /usr/gnu/bin/ld -v
GNU ld version 2.15
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ CC=gcc LD=/usr/gnu/bin/ld
[...]
checking gcc linker... configure: error: failed (not GNU ld). Use GNU ld
instead of Sun ld on Solaris
Even if configure would be happy with that, the build would break
nevertheless, since it doesn't call $LD, but does as configure does:
running the compiler with the linker-mode flags.
Looks like an OpenSolaris matter to me:
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ ls
/usr/X11/include/X11/Xaw
ls: cannot access /usr/X11/include/X11/Xaw: No such file or directory
Well - either that package is not installed, or the path just is wrong.
ciao
Christian
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Compiling OOo 3.0 m28 @ OpenSolaris snv_94
Christian Lohmaier schrieb:
checking for cc... /opt/SunStudioExpress/bin//cc
checking the SunStudio C/C++ compiler version... configure: error: found
version 5.10, use version 5.5, 5.7, 5.8 or 5.9 of the SunStudio C/C++
compiler
The configure check is like that:
_sunstudio_minor=`echo $_sunstudio_version | $AWK -F. '{ if ($2 == 5)
print true; else if ($2 == 7) print true; else if ($2 == 8) print
true; else if ($2 == 9) print true; else print false }'
So from my understanding two-digit minor versions have just not taken
into account at all.
I'd suggest forcing that check to true and try with the 5.10 compiler.
Ok, will try that.
Is there a rule of thumb for *Solaris* like: use Sun compiler for Sun
OS, don't mix in GNU, if possible (that's fishing for trouble)? If so,
one might want to add a hint to the configure script that Sun CC should
be preferred in some cases (such as my OpenSolaris installation).
[building with gnu cc also requires gnu ld]
OpenSolaris does ship with a GNU ld which I could use (in theory) but
configure will ignore it:
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ /usr/gnu/bin/ld -v
GNU ld version 2.15
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ CC=gcc LD=/usr/gnu/bin/ld
[...]
checking gcc linker... configure: error: failed (not GNU ld). Use GNU ld
instead of Sun ld on Solaris
Even if configure would be happy with that, the build would break
nevertheless, since it doesn't call $LD, but does as configure does:
running the compiler with the linker-mode flags.
Looks like an OpenSolaris matter to me:
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ ls
/usr/X11/include/X11/Xaw
ls: cannot access /usr/X11/include/X11/Xaw: No such file or directory
Well - either that package is not installed, or the path just is wrong.
The package seems to be installed:
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ pfexec pkg info
FSWxorg-headers
Name: FSWxorg-headers
Summary:
State: Installed
Authority: opensolaris.org (preferred)
Version: 0.5.11
Build Release: 5.11
Branch: 0.94
Packaging Date: Mon Jul 21 19:04:46 2008
Size: 0 B
FMRI: pkg:/[EMAIL PROTECTED],5.11-0.94:20080721T190446Z
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ pfexec pkg list -v
FSWxorg-headers
FMRI STATE
UFIX
pkg:/[EMAIL PROTECTED],5.11-0.94:20080721T190446Z
installed
But its contents does not look very promising:
[EMAIL PROTECTED]:~/oo.org-m28/config_office$ pfexec pkg contents
-t file,dir FSWxorg-headers
PATH
I'll check on the OpenSolaris lists about this.
Ulf
--
Ulf Wendel, MySQL
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer
Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB161028
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] NetBeans setup for sdk
On Thu, 2008-07-03 at 10:07 +0200, Juergen Schmidt wrote: Hi Terrence, the NB plugin as well the SDK are currently not working with the new OO.org 3.0. Because of a completely new structure both the plugin and the SDK have to changed or adapted. We are currently working on it and you can expect it next week. Hi, I see OpenOffice.org API plugin for Netbeans 1.1.3 available http://blogs.sun.com/GullFOSS/entry/openoffice_org_api_plugin_for, but ftp://openoffice.mirrors.tds.net/pub/openoffice/extended/developer/OOO300_m2/OOo-Dev_OOO300_m2_src_sdk.tar.bz2 at least (I loooked at other some other mirrors back on the 6th) is a mere 42 bytes. Wow, that is right good compression technology grin /. I presume this is just a packaging issue. Is there a better place for me to raise it? Thanks, Terry. Juergen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Debugging OOo
Hi All, Which way do you debug OOo? I currently wanted to perform a full build of OOo 2.4 with debug=true, but ran into multiple problems e.g. during packing of the install set under .../instset_native, while there are no problems with the build when I don't set debug=true. Adding debug symbols to certain moduls of OOo would satisfiy my needs. I presume that I just need to install my compiled build, recompile the modules for which I need debug symbols with debug=true and copy the newly created shared libs and executables over the installation. Is that okay or is there any better approach? Best regards, Micha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Debugging OOo
On Wed, 2008-08-13 at 02:11 +0200, Michael Strobel wrote: Hi All, Adding debug symbols to certain modules of OOo would satisfiy my needs. If you configure with --enable-symbols OOo is built with -g which is sufficient to debug it. Alternatively you can e.g. just whack export ARCH_FLAGS=-g and rebuild a module or two. C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Debugging OOo
Michael Strobel wrote: Hi All, Which way do you debug OOo? I currently wanted to perform a full build of OOo 2.4 with debug=true, but ran into multiple problems e.g. during packing of the install set under .../instset_native, while there are no problems with the build when I don't set debug=true. Adding debug symbols to certain moduls of OOo would satisfiy my needs. I presume that I just need to install my compiled build, recompile the modules for which I need debug symbols with debug=true and copy the newly created shared libs and executables over the installation. Is that okay or is there any better approach? First build without debug and install. Then rebuild the selected modules with debug and just symlink the selected .so within the installed version above. That way I save on the step of copying, or even the deliver. Just build debug=true to check your changes. Hub - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Differences between release candidate, development build, and final
Neither the development builds, nor the beta builds, have GUI integration for Linux. Will the release candidate have GUI integration? I would like some better screen shots and instructions for an installation article, and I would like to report an expected timeline to the publisher. Based on the Wiki, I expect a release candidate around August 25. -- Andrew Pitonyak My Macro Document: http://www.pitonyak.org/AndrewMacro.odt My Book: http://www.hentzenwerke.com/catalog/oome.htm Info: http://www.pitonyak.org/oo.php See Also: http://documentation.openoffice.org/HOW_TO/index.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
