Mail Archives: djgpp/1998/04/15/04:17:44
Hallo,
here is the second public beta release of "Lcc-Win32 for Linux".
What is it:
===========
Lcc-Win32 is a port of lcc to the win32 environment, done by Jacob Navia
with an added Resource compiler (lrc.exe),P(ortable)-E(xecutable) Linker
(lcclnk.exe), IDE (wedit.exe), Resource Browser(weditres.exe), Make
(make.exe) , a PE dumper (pedump.exe) and more . Find Lcc-Win32 at
http://www.cs.virginia.edu/~lcc-win32/.
Thanks to Jacob Navia giving me private access to non-public sources I can
show you the results of my effort to port the command line tools to
Linux. Here is my second public beta test.
What is the status of the port:
===============================
Since the first release in December 1997, I have killed some ugly bugs in
lcclnk, lrc and have made lcc-win32 more robust. I compiled successfully
several small C sample applications, including resources. Please point me to
bigger projects using lcc-win32 for more testing.
You might want to give wedit and weditres a try with Wine too.
Copyright:
==========
For an exact copyright of Lcc-Win32, look at the the Lcc-Win32 distribution.
At anonymous AT ftp://ftp.mathematik.tu-darmstadt.de/pub/linux/bonnes, I have
set up the the modified public sources of the December release. I release
them under the GPL. I will try to put up there the recent version hopefully
r.s.n.
Where to find:
=============
anonymous AT ftp://ftp.mathematik.tu-darmstadt.de/pub/linux/bonnes/
Get lccbin-980415.tar.gz
Setup:
=====
1. Get the original lcc-win32 distribution.
2. Unpack <somewhere>. If you unpack on a Case-sensitive Filesystem, change
all Filenames at least in lccpub/include and lccpub/lib to all lowercase!
3. Unpack lccbin-980415.tar.gz and put lcc-win32, lcc-make, lrc and lcclnk
in your path or use it with explicit path.
4. Export an Environment Variable "LCCWIN32" pointing to the
<somewhere>/lccpub. /usr/lib/lccpub and /usr/local/lib/lccpub is searched by
default.
5. (Test) Run lcc-make in the demo directories after caring for the Name
change from lcc(*1) to lcc-win32.
6. Run on your projects.
Possible showstoppers:
=====================
1. Mixing of Upper/Lower-Case Filenames
2. Namechange from lcc to lcc-win32
3. CR/LF versus CR for text files.
4. Test with original lcc-win32 running under Wine or NT/Win95/Win32s if
same error appears.
Porting to other architectures:
==============================
For the public source tools, you can do yourself, but send back
remarks. For the private source tools I see at least two possibilities:
1. Give me temporary acces to a network connected machine
2. Point me to an easy to setup and small footprint crosscompiler
(*1) lcc is also a native compiler on many platforms, so I choose to make a
clean distiction in name.
Uwe Bonnes
bon AT elektron DOT ikp DOT physik DOT tu-darmstadt DOT de 15.April 1998
--
Uwe Bonnes bon AT elektron DOT ikp DOT physik DOT tu-darmstadt DOT de
Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt
--------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------
- Raw text -