[Laszlo-dev] Upstream Binaries in SVN
ben at laszlosystems.com
Sun Jan 1 12:07:37 PST 2006
Tucker says he likes to be daring and run publically-available
distros. I try to be like Tucker when I'm not too busy trying to be
like Oliver and Bret :)
On the one hand, it sort-of simplifies deployment by having all the
versions we need of all the subparts all in one place. On the other
hand, we've wandered into version twilight on some of the tools; the
tools in the trees are no longer always the correct tools.
We use tomcat-5.0.24 or 28, where the current version is more like
5.5. I'm not sure whether LPS works with Tomcat 5.5; 5.0.24 is pretty
LPS won't work with ant 1.6.1, only 1.5.1, which is pretty old;
converting it to use ant 1.6 is non-trivial, and involves porting
some 3rd-party libraries.
Jikes, we've got sources and weird binaries for 1.18 in the tree, but
1.22/1.23 is the current version, and seems to work.
Better documentation of how to build OpenLaszlo would be great. I
usually start with
http://wiki.openlaszlo.org/Build_Instructions and that just about
Sean, if you want to update this to refer to the current working
versions of things, that'd be great. We should also at least get rid
of the old jikes binaries in the tree, and point to installers for
jikes 1.22. I'm on aim today (benjaminatwork) and you can msg me if
you run into trouble building OpenLaszlo. It's a great day, your
first build! Way to begin the new year!
On Jan 1, 2006, at 3:22 AM, Sean Wheller wrote:
> Is there any need to have the upstream binaries in SVN.
> A source checkout of openLazslo should not require the checkout of
> Perhaps we could lighten the load by documenting the dependencies and
> explaining how to build openlaszlo.
> For example, the tools/ dir in SVN is packed with binaries that can be
> retrieved from upstream sites or distro installation repositories.
> Sean Wheller
> Technical Author
> sean at inwords.co.za
> Laszlo-dev mailing list
> Laszlo-dev at openlaszlo.org
More information about the Laszlo-dev