ALT_OUTPUTDIR=$(OUTPUTDIR)
doesn't make sense to me.
The makefiles will define OUTPUTDIR to be equal to $(ALT_OUTPUTDIR) if
ALT_OUTPUTDIR is set.
The _OUTPUTDIR is the default build location, when ALT_OUTPUTDIR is not set.
The original idea here in setting ALT_OUTPUTDIR=$(_OUTPUTDIR)-$(DEBUG_NAM
On Jan 10, 2008, at 9:09 AM, Kelly O'Hair wrote:
Some of the java sources are generated, from Makefile logic. So no
you can't
just do a javac `find . -name \*.java`.
But in general, the java compilations and the native compilations
are done
together as each part of the jdk areas are built
I would suggest to fix the top-level Makefile such that
COMMON_DEBUG_FLAGS uses $(OUTPUTDIR) instead of $(_OUTPUTDIR)
and doesn't append "-$(DEBUG_NAME)" to ALT_OUTPUTDIR like so:
COMMON_DEBUG_FLAGS= \
DEBUG_NAME=$(DEBUG_NAME) \
ALT_OUTPUTDIR=$(OUTPUTDIR) \
NO_DOCS=true
W
Your final paragraph I think is the answer:
"In my eyes, the cleanest solution would be if ALT_OUTPUTDIR would be honoured
"as is", as the output directory for everything we built, without anything
appended to it. So the developer should be free to choose whatever he wants
as
the outp
At one point I was experimenting with an option that would import all the
native libraries (.dll or .so files) from the JDK_IMPORT_PATH area rather
than run the native compiler. The idea was to allow for building the jdk
without having a native compiler. For various reasons I gave up on this.
I o
> >
> > Any comments if this is the right way to do a debug build?
>
> If it works it's fine. I usually just run 'make debug_build', does that not
> work?
>
It works, but it has the problems that I detailed in my first mail.
Did you also read that one?
I may seem that my second mail contained the
Volker Simonis wrote:
Hi,
me again. I' found that the additional "-fastdebug" directories are
created unconditionally by the top-level makefile, in the setup-step:
setup:
$(MKDIR) -p $(OUTPUTDIR)/j2sdk-image
$(MKDIR) -p $(ABS_OUTPUTDIR)/j2sdk-image
$(MKDIR) -p $(OUTPUT
Some of the java sources are generated, from Makefile logic. So no you can't
just do a javac `find . -name \*.java`.
But in general, the java compilations and the native compilations are done
together as each part of the jdk areas are built.
The corba, jaxp, jaxws, langtools directories are almo
How about providing your own compiler tools (gcc, link, lib) which
simply copies the -o target from an existing JDK build?
Max
On Jan 10, 2008, at 8:27 PM, Alan Bateman wrote:
Roman Kennke wrote:
Hi there,
I'm looking for a make target, that compiles only the Java classes of
OpenJDK. Is th
Hi,
> What do you mean by "the Java classes of OpenJDK".
> Every subproject contains some Jaca classes, so I'm afraid it's
> not possible to build only all the Java classses from OpenJDK with
> one build target.
>
> If you are refering to the JDK Java classes you can get near that
> by only build
Roman Kennke wrote:
Hi there,
I'm looking for a make target, that compiles only the Java classes of
OpenJDK. Is there a way to do that? Thanks,
/Roman
I don't think there is one. There are a number of areas where the source
files are generated during the build (nio and jdwp for example) so
hi,
ALT_PARALLEL_COMPILE_JOBS is currently only honoured by the corba and
the jdk subprojects while the hotspot subproject uses
HOTSPOT_BUILD_JOBS as indicator to do a parallel build.
Unfortunately, neither ALT_PARALLEL_COMPILE_JOBS nor
HOTSPOT_BUILD_JOBS is handed over from the top-level makefil
What do you mean by "the Java classes of OpenJDK".
Every subproject contains some Jaca classes, so I'm afraid it's
not possible to build only all the Java classses from OpenJDK with
one build target.
If you are refering to the JDK Java classes you can get near that
by only building the JDK target
Hi there,
I'm looking for a make target, that compiles only the Java classes of
OpenJDK. Is there a way to do that? Thanks,
/Roman
--
http://kennke.org/blog/
--
Dipl.-Inform. (FH) Roman Kennke, Software Engineer, http://kennke.org
aicas Allerton Interworks Computer Automated Systems GmbH
Haid-
Hi,
me again. I' found that the additional "-fastdebug" directories are
created unconditionally by the top-level makefile, in the setup-step:
setup:
$(MKDIR) -p $(OUTPUTDIR)/j2sdk-image
$(MKDIR) -p $(ABS_OUTPUTDIR)/j2sdk-image
$(MKDIR) -p $(OUTPUTDIR)-fastdebug/j2sdk-image
Hi,
there seems to be a problem with the handling of ALT_OUTPUTDIR for debug and
fastdebug builds. The top-level makefile contains the following definitions:
Makefile
include $(JDK_MAKE_SHARED_DIR)/Defs-control.gmk
COMMON_DEBUG_FLAGS= \
DEBUG_NAME=$(DEBUG_NAME) \
ALT_OUT
16 matches
Mail list logo
