Re: [dev] OpenOffice.org Java JRE search paths

2009-04-01 Thread Hanno Meyer-Thurow
On Wed, 01 Apr 2009 07:53:36 +0200
Joachim Lingner joachim.ling...@sun.com wrote:

 Starting with OOO310 m8 OOo will automatically search for a new JRE when 
 the previously selected one was removed. Provided that the new JRE is in 
 a path that is found, everything will work.

That is good to know. :)

Do you have any code pointers to check for the changes below?
They are interesting with or without the feature above.

 Hanno Meyer-Thurow schrieb:
  So, in short it would be these three points of interest:
  - change Java JRE search paths to one (set by configure option)
  - accept a symlink as the base directory for a Java JDK/JRE
  - to add a manual Java JDK/JRE install use the (already available)
'Add' button in the Java options dialog
(in my hacked build non-functioning)

Thank you!


Regards,
Hanno

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



[dev] OpenOffice.org Java JRE search paths

2009-03-31 Thread Hanno Meyer-Thurow
Hi all!
As of now OpenOffice.org looks for a JRE in different paths.

What I heard is that each micro version update unsets the
OpenOffice.org Java configuration in Gentoo and one has to
set the Java JRE again under

Extras  Options  OpenOffice.org  Java

Serkan, correct me please if I am wrong.

The Gentoo Java Team came up with the idea to centralise
the Java JRE search path in one directory. This would be /usr/lib/jvm
in Gentoo where Java JDK/JRE are managed without the micro version
in its pathname. And named like jre | jdk-major.minor only.

So, in short it would be these three points of interest:
- change Java JRE search paths to one (set by configure option)
- accept a symlink as the base directory for a Java JDK/JRE
- to add a manual Java JDK/JRE install use the (already available)
  'Add' button in the Java options dialog
  (in my hacked build non-functioning)

I tried to patch

jvmfwk/plugins/sunmajor/pluginlib/util.cxx

There is a char array of search paths and symlink checks
but without luck.

Any help or pointers is appreciated!
And thank you in advance!


Regards,
Hanno

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org



Re: [dev] AMD64 Java

2007-05-02 Thread Hanno Meyer-Thurow
On Tue, 1 May 2007 16:30:44 -0700
Travis Athougies [EMAIL PROTECTED] wrote:

 Hi,
 
 I'm trying to compile with blackdown-jdk on amd64 because it said that it
 had been reported to work on the wiki. I'm using version 1.5.

Any jdk-1.5 version (but gcj-4.3 alpha) on x86_64 breaks in this or that way.
Either use blackdown-jdk-1.4.* or gcj.

 If not and I'll have to use gcj can any fellow Gentooers explain how to
 install gcj as a jdk on gentoo?

http://overlays.gentoo.org/proj/java/wiki/GCJ_as_a_JDK

Btw, at least with ooo-build the gcj oom killers are history.


Regards,
Hanno

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [dev] Building OpenOffice.org

2007-04-28 Thread Hanno Meyer-Thurow
On Sat, 28 Apr 2007 11:57:37 -0700
Travis Athougies [EMAIL PROTECTED] wrote:

 I would like to contribute code to openoffice.org but I need to know if I
 can have two copies installed at the same time, Gentoo's openoffice-bin and
 the one that I built for development. IS this possible?

Yes.

What I do to hack on OOo is documented here
http://geki.ath.cx/index.php/OpenOffice

Discussion is held at this thread
http://forums.gentoo.org/viewtopic-t-489909.html

Though, this is for ooo-build version of OOo.
If you are interested in this way you may ask questions on that thread, please.

___
After you did
ebuild /path/to/ebuild compile (hopefully successed)

hack (described on my page) on the source. Then, you switch to ooo-build
directory and run
bin/ooinstall -l path-to-install-to

That will link the compiled openoffice to that installation path as if it was a
normal installation.

Finally run this in a new shell to test the development version
cd path-to-install-to/program
source ./ooenv
./soffice.bin -writer # for example

Now when you hack again on that one shell you can restart OOo with 
'./soffice.bin ...'
in the second shell to see the change.

Take care not to mix up the HOME/.ooo-*/ directory with stable and
development version configuration of OOo. Better use a testuser for
that.

So far, I hope I did not miss or mix up something.


Regards,
Hanno

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]