Hi all,

as mentioned by Mark and Tom, this should be discussed on the list.
When we build classpath inside libgcj we 'need' some gcc specific bits to build qt-peers for example. Other areas might benefit too. To build c++ stuff we need the just bootstrapped g++, its include & its libraries. To make these known to the classpath machinery it would be good to have the option mentionend in the subject. Then we can add the includes and the library to the QT_CFLAGS/QT_LIBS with simply cheking for ENABLE_LIBJAVA_BUILD=yes and add them. (We would have to extend the configury to check for this later, yes)

So far I see no possibility to pass them down from libjava build into classpath build without the option below.

What are your comments, thoughts on this? Is there a better possibility?

Thanks
Andreas

Index: configure.ac
===================================================================
RCS file: /cvs/gcc/gcc/libjava/classpath/configure.ac,v
retrieving revision 1.5
diff -u -r1.5 configure.ac
--- configure.ac        30 Sep 2005 20:46:42 -0000      1.5
+++ configure.ac        2 Oct 2005 19:29:24 -0000
@@ -77,6 +77,18 @@
               esac],
               [ENABLE_WERROR=no])

+dnl -------------------------------------------------------------
+dnl Whether to compile classpath inside gcc (disabled by default)
+dnl -------------------------------------------------------------
+AC_ARG_ENABLE([libjava-build],
+ [AS_HELP_STRING(--disable-libjava-build,whether to build classpath inside gcc. [default=no])],
+       [case "${enableval}" in
+         yes) ENABLE_LIBJAVA_BUILD=yes ;;
+         no) ENABLE_LIBJAVA_BUILD=no ;;
+         *) ENABLE_LIBJAVA_BUILD=no ;;
+       esac],
+       [ENABLE_LIBJAVA_BUILD=no])
+AC_SUBST(ENABLE_LIBJAVA_BUILD)
 dnl -----------------------------------------------------------
 dnl Default AWT toolkit
 dnl -----------------------------------------------------------


_______________________________________________
Classpath mailing list
Classpath@gnu.org
http://lists.gnu.org/mailman/listinfo/classpath

Reply via email to