Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Building in a Container

rokelley
Novice
523 Views

We're trying to modernize our Fortran build process a little bit with GitLab and Docker, but I've come accross a difficult question:

Given:

  • A .vfproj project and .sln file
  • An installation of "Build Tools for Visual Studio" with some workload TBD
  • An installation of oneAPI or the Intel Fortran Compiler

Should I be able to reproduce the build that our developers are getting when they simply click the "Build" button in the full Visual Studio installation (including all the compiler options form the vfproj file)?

 

Also, can anyone share some tips on installing the older Fortran Compilers like Composer XE 2011 (v12) in a container? I see the oneAPI containers at Docker hub but I can't yet tell if those include the Fotran compiler.

0 Kudos
7 Replies
Ron_Green
Moderator
511 Views

forget PSXE in a container - these older compilers need a license file and you cannot distribute it with your container.  

oneAPI compilers don't need or use a license file.  but you if you intend to distribute this container with our tools you do need your end users to read and agree to our EULA.   At least this is what I remember - do you intend to distribute this container?

Yes, the oneapi hpc toolkit container will have our Fortran compilers.

0 Kudos
rokelley
Novice
501 Views

I think we use a license server for those, we're kind of locked in to a few old versions right now due to qualification requirements. Any input on the command line build?

0 Kudos
Ron_Green
Moderator
492 Views

you'll need gnu gcc glibc and binutils build tools.  normal developer rpms or packages in your image.  nothing weird or obscure.  

0 Kudos
Ron_Green
Moderator
487 Views

I just checked Sys Requirements and it says

"

  • Linux Developer tools component installed, including gcc, g++ and related tools."
0 Kudos
rokelley
Novice
485 Views

Our developers started all these projects in Visual Studio, so a ton of compiler options (among other things) have accumulated in the vfproj file. Is there a way to get those out and pass them to ifort, or is that not the way?

0 Kudos
Steve_Lionel
Black Belt Retired Employee
456 Views

The "Command Line" project property in VS has all of the options being used. I would often take the buildlog.htm, which contains the full commands used to compile each source, and turn that into a batch file.

0 Kudos
Ron_Green
Moderator
480 Views

I don't know, I don't use VS enough.   There are a lot more qualified VS users here than I.

0 Kudos
Reply