Hi there everyone.
This will officially be my first email to the OpenJDK project.
I got to attend a couple of sessions/BOFs at JavaOne2008 about
OpenJDK and my interest was piqued. I've been playing with the build
for the last week. (A more accurate description would be, "yanking my
hair o
Rob Ross wrote:
Hi there everyone.
This will officially be my first email to the OpenJDK project.
Welcome. I actually appreciate the email, some comments below.
I got to attend a couple of sessions/BOFs at JavaOne2008 about OpenJDK
and my interest was piqued. I've been playing with the b
I propose that Sun create an externally-visible tree of binaries
in the form that the JDK makefiles expect for ALT_SLASH_JAVA.
Then OpenJDK developers could copy this tree to their development
machine, set ALT_SLASH_JAVA to this directory, and most of
the sanity warnings would evaporate.
Of course
Martin,
I'd settle for just a *list* of all the tools you need, and have the JDK
build able to find all the tools given a minimum of ALT variable
settings.
For licensing reasons, I suspect Sun cannot redistribute many of the
tools,
but if the user could populate such a tree, then any version
I can't see this happening due to the legal re-distribution issues
and requirements you'd have on all these different software packages.
And I for one would NOT want to be the maintainer of it.
Maybe my frustrations with Windows is blinding me to some new
good solution to this problem, but instal
I tried to provide that list at:
http://hg.openjdk.java.net/jdk7/build/raw-file/tip/README-builds.html#windows
Did I miss the target somehow?
-kto
Jonathan Gibbons wrote:
Martin,
I'd settle for just a *list* of all the tools you need, and have the JDK
build able to find all the tools gi
One setting is enough, if the directory structure is right:
$ALT_SLASH_JAVA
devtools
share
ant...
findbugs...
plugin
mozilla_headers_18.win32...
Windows
DXSDK...
re
jdk
1.6.0/archive/fcs/binaries/windows-i586...
Kelly, Max,
That list mostly covers what you need for a build (Ant does not seem to
be present, required
by langtools), but it bdoesn't cover everything you may need to work on
OpenJDK, and it
doesn't particularly encourage a single shared tree.
As Max points out, you can get by with a single
It is a "BUILD" readme. The development requirements are a separate
thing, perhaps that should be documented in the development guide?
Yes, we should add "ant" as a build requirement, I'll fix that.
---
Trying to satisfy everyone with the build configurations is frustrating
to say the least.
If
True, and to be fair, the BUILD readme is quite good. Perhaps I'd be
happy with a simple
short table in the developers guide that at least gives me one place to
go to find a list of
everything I need, with (references to) info on where to get and how to
"use" those tools.
(ie what env variable
- Freetype is new to many of us, I use a freetype that someone else
built
so I have never experienced building it myself.
I will try and look into this and see if I can document it better.
Original way to build freetype on windows is described here:
http://mail.openjdk.java.net/pip
11 matches
Mail list logo
