[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: RE: MSVC compiler support [patch 11]: CRUFT.DLL exported symbols (Fo

From: michael . goffioul
Subject: RE: RE: MSVC compiler support [patch 11]: CRUFT.DLL exported symbols (Fortran)
Date: Thu, 26 Oct 2006 16:33:10 +0200

Note that in the patch, I also moved the compiler-specific flags "-EHs -MD"
at the first position. I did it because when I run the configure script, I specify
the build host as i686-pc-msdosmsvc. However this case is catched by the
first choice (which catches i686-*-*) and the flags are not correctly set.

> With this rule, it appears that an extra entry will be added to the
> cruft.def file each time a file is compiled (it can happen more than
> once if the object files are removed, or if the source file is
> touched). Is that a problem? Perhaps we should instead create as
> separate def file for each source file and then collect them all at
> the end? Also, I don't see any rule to remove the cruft.def file.
See attached patch for another proposal. It creates a .def file for each
fortran file and concatenates everything at the end. The dependency on
cruft.def is only active when the canonical host type contains msdosmsvc
(this could also be moved to configure script by putting a @...@ tag
for libraries dependencies).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]