Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

Possible to use .a library files?

algebra
Beginner
‎10-12-2004 12:38 PM
432 Views
I have some .a library files generated with cygwin. Is it possible to use them with IVF? I've tried treating them as regular .lib files and included them under project setttings' linker options. However, that didn't work.

So, given a .a file, how do I use it or how do I convert it to .lib?
0 Kudos

Link Copied

1 Reply
TimP
Honored Contributor III
‎10-12-2004 03:05 PM
432 Views
You leave a lot of possibilities open. Cygwin .a files will work with 32-bit Windows, within limits. They won't work with 64-bit windows, as cygwin doesn't support the /machine tag. In our usual usage, we create the .a files from objects built by IVF and MSVC (or ICL). The Microsoft linker throws a warning for each object which has been renamed to .o, and sometimes there is difficulty with correct handling of the differences between C and C++. It would be quite difficult to use .a files generated by g77, gfortran, or g++. gcc might fall in the middle, but you would have to deal with the linkage conventions being different from what is usually expected with gcc. Evidently, you get quickly into areas of non-support.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.