Linking fortran lib on a non-Fortran developer machine

[dave_buckley]

Is it possible to provide astatic FORTAN library to non-Fortran Developers so that they can link this into a solution without the Fortran compilers installed locally?

Have attempted to do this by removing the VFPROJ from the solution and then refernecing the static lib built from a production build environment.

However have been seeing different linker errors for either IFCONSOL.lib or IFWIN.lib when trying this on a non-Fortran machine.

This is also after playing with some of the different options with the runtime settings for the FORTRAN project.

Other than distributing the FORTRAN libs to our developers is it possible to provide a single LIB file with all of the dependancies included within itself?

Thanks
Dave

[DavidWhite]

Quoting - dave.buckley

Is it possible to provide astatic FORTAN library to non-Fortran Developers so that they can link this into a solution without the Fortran compilers installed locally?

Have attempted to do this by removing the VFPROJ from the solution and then refernecing the static lib built from a production build environment.

However have been seeing different linker errors for either IFCONSOL.lib or IFWIN.lib when trying this on a non-Fortran machine.

This is also after playing with some of the different options with the runtime settings for the FORTRAN project.

Other than distributing the FORTRAN libs to our developers is it possible to provide a single LIB file with all of the dependancies included within itself?

Thanks
Dave

Dave,

I'm not an expert on this, but there may be some runtime distributables that you also need to provide to these developers. Check the documentation, there is a list of libraries which you can distribute to other users. Unfortunately, you may not distribute the debug libraries (have an extra D on the end of their name).

Regards,

David

[Steven_L_Intel1]

Other than distributing the Fortran libraries? No. You need to do that. They are redistributable (the non-debug libraries, anyway.) Could you build a DLL? That would not require additional libraries to link (you would supply the DLL and the "export library".) If you linked the DLL against the static (non-DLL) run-time libraries, there would be nothing else to distribute.

[e309x5]

Quoting - Steve Lionel (Intel)

Im trying to port an Intel Visual Fortran compiler v9.1 user defined library into a old watcom fortran 77 library. Watcom linker complains error 2123 no dictionary for the library. I Have never used this post before and did not findout how to start a new post. Any ideas?


Other than distributing the Fortran libraries? No. You need to do that. They are redistributable (the non-debug libraries, anyway.) Could you build a DLL? That would not require additional libraries to link (you would supply the DLL and the "export library".) If you linked the DLL against the static (non-DLL) run-time libraries, there would be nothing else to distribute.

[Steven_L_Intel1]

e309x5, you can start a new discussion by clicking "Start New Discussion" to the right of the forum title on the main forum page.

You cannot create a library with mixed Watcom and Intel Fortran objects. In general, Fortran compilers do not allow mixing of objects built with other Fortran compilers.