On Mon, 14 Feb 2005 13:11:43 +0100, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
This is how it would work for Linux too.
Evert, can you help me port to Linux? It looks like we need to follow
the MSVC pattern of gcc for ASMs and icc for C files ... But we need
to make changes at the autoconf-level to give a new configure script
... As such the installation of icc can be found by querying the
default /opt/intel_cc_80/bin directory.. I have kept the Linux
documentation for icc in:
http://guilt.bafsoft.net/allegro/icl/Linux.tar.bz2 (if not, linux.tar.bz2)
I guess it should ultimately be integrated with the configure machinery on
Linux... not completely sure if that's really the way to go though.
When I tried it last, I had some problems with the ICC compiled library:
text didn't render properly. I didn't invesigate the cause back then
though...
Can you give me the exact details? Which version of icc was it, and
how was the library linked with it? I am guessing that the compiler
may not be a problem.Might have been a library dependancy..
And for Windows, do we need a separate platform? Because icl "is"
MSVC-dependant on Windows. It uses the MSVC headers/libraries to do
most of the compilation. If so, can we make the change a minor one
like:
#ifdef ALLEGRO_ICL
#define ALLEGRO_MSVC
#endif
I don't have a problem in re-making a allegro/platform/iclwin.h or
whatever .. It will be plainly "redundant" with the MSVC file. Why I
suggested that we retain the common-ness was, that a dynamic/static
library compiled with icl can be used as-is with cl (MSVC or MSVC7) ..
Here is a more recent MSVC makefile:
http://guilt.bafsoft.net/allegro/icl/makefile.vc
I'd really like to see everybody's ideas on this...
Awaiting a reply.