|Announce: lcc 4.2 & lcc.NET now available firstname.lastname@example.org (Dave Hanson) (2002-09-14)|
|Re: Announce: lcc 4.2 & lcc.NET now available Juergen.Kahrs@vr-web.de (Juergen Kahrs) (2002-09-14)|
|From:||"Juergen Kahrs" <Juergen.Kahrs@vr-web.de>|
|Date:||14 Sep 2002 16:38:03 -0400|
|Posted-Date:||14 Sep 2002 16:38:03 EDT|
Dave Hanson wrote:
> A backend for the Microsoft .NET intermediate language, MSIL, is also
> now available. It must be used with lcc 4.2. For download
> instructions, visit http://www.research.microsoft.com/downloads/ and
> scroll down to the "MSIL backend for lcc v4.2" entry.
The MSIL backend is only available under a special license agreement.
It only works on MS Windows. You need several other Microsoft products
if you want to build and install the compiler: Visual C++ and the
.NET Framework SDK. All this required software costs more than the
computer it is running on. I do not intend to pay Microsoft so much
money for playing with just-another-Java-clone.
When installing the MSIL backend on Linux, you will need gcc's header
files, libraries and preprocessor. This is what the installation doc
says. It makes sense to use gcc's established infrastructure for the
bootstrap of lcc or any other compiler. What disappoints me is the
asymmetric relationship between these compilers: lcc's MSIL backend needs
gcc's infrastructure to bootstrap on Linux, but lcc's MSIL backend is
only available under the EULA.
Return to the
Search the comp.compilers archives again.