A few comments inline.
On 2013-03-16 21:38, Mani Sarkar wrote:
Hi,
The OpenJDK adopters in the community have been testing out
the steps lately to build OpenJDK on the MacOS and so far things are fine,
we didn't need to install MacPort or have major issues with the Mac.
You can have a look at the steps if these help with your issues:
http://java.net/projects/adoptopenjdk/pages/AdoptOpenJDKBuildInstructions
http://java.net/projects/adoptopenjdk/pages/GetSource
http://java.net/projects/adoptopenjdk/pages/GetSource#Mac_OS_X
http://java.net/projects/adoptopenjdk/pages/Build#Mac_OS_X
There is no need to cd down to common/makefiles anymore. We hid the new
build system there before making it default. Now you can run bash
configure and make from the root. Please see README-builds.html in the
src root for more details. It should be up to date now, thanks to Kelly.
http://java.net/projects/adoptopenjdk/pages/MakeImages
To get verbose build logs, the preferred way is to use the LOG variable
and not VERBOSE. LOG can be set to warn, info, debug or trace. Again see
README-builds.html. Also, the build output is always saved to a log file
in the build output directory unless disabled, so no need to pipe yourself.
/Erik
Any feedback is welcome.
Cheers,
mani
It's not installed by default, and I'm not sure why you'd want to since
Apple provides it. But if it's there that could be a concern.
If you install subversion, you get file, and there are other things that
(if installed) will pull in subversion (e.g., trac).
Ah Trac, how I remember thee...
Incidentally, someone else got a build working with brew so there's an
alternative to MacPorts for those who don't want to use it. The only caveat
is that brew installs everything into the system paths, which could cause
problems later on. And it uses Ruby *hack cough*...
Installing stuff on system paths is not what I want.
Same here, which is one reason I stick with MacPorts. I'm not sure what
the fuss is anyways, once binaries are available ports come in very fast.
-DrD-
