Hi All,
(cc'd the list so this discussion would make it into the archives)
I totally agree that we need one set of comm libs for all platforms,
the maintenance on more than one would kill us.
I willing to provide patches for the libjirtrcx2 to reintroduce the
changes that Andy made for OSX (and test them) if I could get a
pointer to the CVS trail (approximate date, branch etc).
On Feb 6, 2006, at 2:58 AM, Matthias Paul Scholz wrote:
Hello Andy, Bill, Markus,
after having packed and tried a Linux and a Windows version and
having talked to all of you, the present state of the leJOS CVS
sources as it unveils to me is as follows:
Both the ant build files in the lejos root folder and in the
release folder (the release build uses the root build) work without
problem in building the lejos 3 release for Windows and Linux
except for the communication libs (irctrcx and jirctrcx):
After reverting to gcc3.3 ($ sudo gcc_select 3.3) I can build on OSX
too, with the recent patch to get around the gcc 4.0 error that was
sent in by (Alexandre Buisse) I'll try again to build with 4.0. I
suspect it will work without a problem.
- on Windows, src/comms/libirctrcx can not be built, but src/comms/
libirctrcx2 and src/comms/libjirctrcx2 can; they do appear to work
flawlessly on XP
- on Linux, src/comms/libirctrcx and src/comms/libjirctrcx can be
built and work flawlessly; src/comms/libirctrcx2 and src/comms/
libjirctrcx2 can be built, but do not work (firmdl always brings up
an "RCX not responding" error)
Hence, on Linux a working release can be built when using the lib(j)
irctrcx versions only, on Windows a working one can be built when
using the lib(j)irctrcx2 versions only.
As for Mac OSX, the situation is unclear to me for I can't try it
out by myself as sourceforge's Mac compile farm hosts are
constantly off-line still (but Andy has pointed out that the
current version of libirctrcx does not run flawlessly on MacOSX);
however, the Mac related adjustments Andy made to the libirctrcx
sources don't appear to have made it into libirctrcx2 (?).
Hence, the situation it's not completely optimal yet.
In my opinion, a good strategy could be to focus on getting the lib
(j)irctrcx2 versions running on Linux and Mac OSX to have a single
souce for the communication libs.
What do you think of it?
Regards,
Matthias
PS Greetings to Boston (have been there by myself for some time) -
may be mighty cold there presently :-)
Andy Belk wrote:
Sorry for the confusion, I want to help get lejos running on the
mac again. I'm keen to help merge the old version of the lejos
code with what is there now (or at least try to help find the
problem).
Ah, great ;-)
By old version I meant the old version of lejos. Does the
version that is downloadable from sourceforge.net work on the
mac or do you have a local snapshot that is working?
I made an unofficial release some time ago (there's a copy on my
Mac.com webpage : http://homepage.mac.com/andybelk/)
This was CVS TOT around May 2004, nearly eternity in software
terms ;-}
I'm in Boston on business so I'm a bit useless right now, but
might be able to get back into things next weekend.
Cheers,
Andy
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Lejos-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lejos-discussion
