To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=63446 Issue #:|63446 Summary:|configuration of SDK for running with gcj and ant Component:|porting Version:|OOo 2.0.2 Platform:|All URL:| OS/Version:|Linux Status:|NEW Status whiteboard:| Keywords:| Resolution:| Issue type:|TASK Priority:|P3 Subcomponent:|code Assigned to:|jsc Reported by:|sparcmoz
------- Additional comments from [EMAIL PROTECTED] Tue Mar 21 14:25:52 -0800 2006 ------- This issue is to request configuration of SDK for running with gcj and ant. I will reproduce these notes on the [EMAIL PROTECTED] list in case others like to comment. For gcj there are 2 main flavours to be considered: (1) where fake java commands exist, such as /usr/bin/java, these are provided by the various linux distributions, using java-gcj-compat or jpackage infrastructure. This is useful for most users but please see comments at issue 62265 and cws_src680_maho1 (2) the vanilla gcj installation which provides corresponding commands such as gij, gcj, gjdoc, fastjar, this is useful for experimenting with different compiler versions and gives visibility to bugs such as hardcoded java commands or failing to obey the configured environment Based on the comments by cmc and maho at issue 62265 the strategy should be like this: (a) --with-java=gij: this is only to make a flag that can be used to bypass non-working code, or find special workarounds for gcj (b) --with-jdk-home=/path/to/java/home: this should allow choosing between alternative installed compilers. The configuration should look for java at the specified location, and not rely on searching the PATH. If javac command is not found, then search for the corresponding gcj command. Note that gjdoc is not part of the gcj installation. For example in my system there are: (i) /usr/bin/java - provided by debian (ii)/usr/local/bin/gcj - my vanilla gcj 4.0 (iii)/usr/local/4.1/bin/gcj - my vanilla gcj 4.1 (iv) /usr/local/bin/gjdoc (c) --with-ant-home=/path/to/ant/home: similar issues as gcj for alternative installations. For ant to launch directly (simply using "ant" command) with gcj 4.1 it is necessary to set JAVACMD. But gcj 4.0 will not launch ant the direct way, so it necesssary to use this method: gij -classpath $ANT_LIB/ant.jar:$ANT_LIB/ant-launcher.jar -Dant.home=$ANT_HOME org.apache.tools.ant.Main Corresponding issues affect the includes and link paths. These are revealed most easily in examples/DevelopersGuide/OfficeDev/DesktopEnvironment. There it appears it may also be necessary to explicitly include jni.h when using gcj? --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
