| Re: [AD] icl porting on Linux |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Sunday 20 March 2005 09:00, guilt wrote:
> i am not sure of how to port it to icc on Linux.. because the makefile
> uses autoconf ..
The proper thing to do would be to add a --use-icc switch to the configure
script.
> that files contains the icc 8.1 user manual, hacked makefile n error
> logs.. looks like the ASMs will have to be compiled on gcc only .. can
> someone help in letting me know of what has to be changed, (maybe a
> new platform?) and how? do let me know..
You will also need to specify the commandline switch that tells icc *not*
to identify itself as GNU C. There is currently no easy way to specify
which files should be build with gcc and which should be build with icc.
To do this, the list of files would need to be split and seperate rules
used for both of them. This is probably too much trouble right now, so I
would recommend that you try to get the C only version to compile and run
properly with icc (--disable-asm to the configure script).
If that has no issues, we can try to figure out a clever way to compile the
asm files as well. If the C only version works fine, I don't think this is
a priority though.
> for windows, have updated the compiling flags.. it works very well, no
issues.
Good!
> http://guilt.bafsoft.net/allegro/icl/makefile.vc
Could you make a diff that clearly shows what changes you made?
> BTW, i would consider it wiser to us ICL with MSVC on Windows and GCC
> on LINUX because as such, the compiler doesnt have all the standard
> header files etc.. the standard distributionm ships with compiler
> binaries, tools and "some" optimized headers/libraries ..
Can you provide a proper port readme file as for the other ports that
describes how to build for icc in Windows (see allegro/docs/src/msvc._tx
for a reference)?
Evert