Binary distributions (nightly and other)

gregorypierce · August 2, 2003, 8:47pm

Let me put it bluntly, having to build from source sucks-ass. Every project on java.net should be generating a nightly build from the code that is checked into CVS by using a build.xml file or similar. It is completely insane to have to build stuff oneself - just to play around with things. Java.net needs to provide a binary for every piece of the open source libraries - jinput, jogl, joal, jutils, etc. There should be a binary posted and on update, the CVS release should be built and a notification should be sent out so that people know the new release is done.

While I’m sure the sun folks have the best intentions of keeping the user community up to date on the latest releases and such - that is a 1980s approach to software development and version control

gregorypierce · August 3, 2003, 1:13am

Since I have the relevant rights on the site, I’ve deployed jutils.jar and the coreAPI for jinput. I’ve also cleaned up the hierarchy of directories so that it is easier to find platform specific versions.

djp · August 3, 2003, 3:50am

We feel your pain!

We are working on getting nightly builds going for the games-core projects. I know I have said this in the past but we are getting really close now.

I am not sure what to do about all the other projects. We really can’t take on the task of building nightlies for all projects.

Suggestions?

d

pepijnve · August 4, 2003, 3:09pm

Maybe something like cruise control could be used to build binaries often.

athomas · August 4, 2003, 4:31pm

[quote]Maybe something like cruise control could be used to build binaries often.
[/quote]
Glad you mentioned it. We are currently in the process of configuring CruiseControl to handle building the core APIs. We should have everything up and running shortly. Please stand by…

gregorypierce · August 4, 2003, 4:35pm

Anthill, cruise control, etc. already exists. No point in Sun trying to pioneer new ground here. Hell if they get it to work with java.net I’m sure they could sell packaged binaries with their own Linux/Solaris development clusters and make the world a better place In any event, there are solutions out there already so we should just pick one, get a couple of solaris boxen for a build farm and go forth

pepijnve · August 4, 2003, 5:21pm

I didn’t mean to suggest that a new solution would be created, but rather that cruise control would be used. Or something similar (like anthill, centipede, maven, …).

swpalmer · August 4, 2003, 6:01pm

Can cross compilation for Win32, OS X, Linux etc all happen from one box? I would think it would be easier to have the various environments available for builds. Does cruise control handle that?

gregorypierce · August 4, 2003, 11:31pm

Yep, the can all be built from the same box - especially if we’re using gcc to compile all the native bits.

swpalmer · August 5, 2003, 1:23am

That’s cool. I expected linking problems when you have to bind to DirectX or Mac OS frameworks. The header files alone aren’t enough, are they?

gregorypierce · August 5, 2003, 2:24pm

Since we’re doing dynamic linking they are less of a problem. I can successfully (for example) build the Linux stuff from OSX after tweaking the environment. Haven’t tried anything with respect to building things that use DirectX.