M
To: Kelly O'Hair
Cc: build-dev
Subject: Re: Building OpenJDK 7 on Windows XP
Well I'm happy to report I finally got the full build to work,
although it took another 15 hours or so.
The last two big issues I encountered:
1. Unfamiliarity with the freetype project, so had to figure o
Consulting, Teaching, Speaking, Writing
http://www.tedneward.com
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Andrew John Hughes
> Sent: Friday, May 23, 2008 12:51 AM
> To: Ted Neward
> Cc: Rob Ross; Kelly O'Hair; build-dev
2008/5/23 Ted Neward <[EMAIL PROTECTED]>:
> Now check out
> http://blogs.tedneward.com/2007/12/15/Let+The+JDK+Hacking+Begin.aspx (sorry
> I didn't see your email sooner, but I've been AFK for a while), and tell me
> if I left anything out of the process.
>
Hmmm... your blog doesn't seem to all
iting
http://www.tedneward.com
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:build-dev-
> [EMAIL PROTECTED] On Behalf Of Rob Ross
> Sent: Tuesday, May 20, 2008 3:43 AM
> To: Kelly O'Hair
> Cc: build-dev
> Subject: Re: Building OpenJDK 7 on Windows XP
>
>
I do recall that a large part of the problem is that the Visual Studio
compiler uses default filenames that are generic names, so that if GNU
make does try and compile two different files, they can end up trying to
write to the same file, not good.
So it may not be GNU make's fault in all cases,
On Windows, I don't think gmake -j is used by default, unless you used it
yourself. The jdk makefiles won't use it, and hotspot is built with NMAKE
on windows.
I have never seen the parallel job feature of GNU make work on windows,
or work very well, I always avoid it.
-kto
Rob Ross wrote:
Well
Thanks Igor, I'll try and add that information to the OpenJDK Build README.
-kto
Igor Nekrestyanov wrote:
- 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 documen
Well I'm happy to report I finally got the full build to work,
although it took another 15 hours or so.
The last two big issues I encountered:
1. Unfamiliarity with the freetype project, so had to figure out what
needed to be built. This project is rather complicated. It supports
building
- 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
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
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
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
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...
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
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
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 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
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
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
19 matches
Mail list logo
