[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Allegro Developers <alleg-developers@xxxxxxxxxx>
- Subject: [AD] Intel C++ 8.1
- From: guilt <karthikkumar@xxxxxxxxxx>
- Date: Mon, 14 Feb 2005 16:27:31 +0530
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=CXBRt4Z5CDLttgTEdEJ5l0F9PzucHadPc4xturojxx54OqaOSu3NyDraTnBwB+woTmpndvlPzj19kiHQbDOZS28PApzM8LH0PZ/kXeXlJmYI1RA9PDg0Cy/m51VG0lZA1JUfWAUwCBd6lPLv3yt7OK82r+QAFulG8dMH5nWwcCM=
Hi,
I was thinking of giving out a makefile for this compiler. Actually,
icc is very compatible with vc. So, there will actually be very few
changes required to makefile.vc ..
I was just wondering about three things:
1. ALLEGRO_MSVC: as such, this port is completely compatible with icc.
So, should there be a separate ALLEGRO_ICC? I don't really think there
may be a need.
2. Should there be a separate makefile.icl or makefile.icc for
Windows? As such, most things ought to work with makefile.vc except
for some changes/clean-up ..
Probably, while building with makefile.vc, a Make USE_ICL=1 won't be a
bad idea after all ..
Just let me know about the idea.
--
Karthik
http://guilt.bafsoft.net