Not recognizing intel fortran compiler using devenv

[H0R5E]

Hi, I am trying to compile a fortran project using Windows based on a Visual Studio solution file using the devenv command, e.g.

devenv.com Nemoh.sln /build "Release|x64"

I have the project building locally using this command with Visual Studio Community 2022, but when I run this actions, the project files are not recognised. Here is an example artifact of the UpgradeLog.htm output, which says:

The application which this project type is based on was not found

for all of the project files.

The repository/branch being tested is https://github.com/DTOcean/NEMOH
The workflow is here: https://github.com/DTOcean/NEMOH/actions/workflows/release.yml

Any help is greatly appreciated.

Thanks,

Mat

[wpbonelli]

This action installs oneAPI without VS integration. That might be the issue? Not sure.

Check the flags in the script here https://github.com/fortran-lang/setup-fortran/blob/main/install-intel-windows.bat and see if turning on vs2022 integration helps?

I guess we could consider an action input to toggle this, but we've tried to stay away from toolchain-specific inputs.

[H0R5E]

OK, thanks, I'll give it a try.

I guess we could consider an action input to toggle this, but we've tried to stay away from toolchain-specific inputs.

If I get something to work I'm happy to offer an update to the docs to describe the process, if that would be useful?

EDIT: Saying that, perhaps it's easier to just pass some options through to the installer from the action. Again, happy to offer a PR.

[wpbonelli]

EDIT: Saying that, perhaps it's easier to just pass some options through to the installer from the action. Again, happy to offer a PR.

That sounds reasonable, something like install_args? Note it'll be package managers e.g. apt/brew/choco generally, intel is the only one with its own installer at the moment.

That'd be very welcome, thanks.

By the way, after some thought I recollect having to enable VS integration before. In case it's useful to you, see here and usage here. In that case it wasn't devenv, it was part of the necessary rigmarole to build petsc on windows. But this does seem to be a pretty common situation

[H0R5E]

@wpbonelli, I was thinking of something simpler, to simply set the NEED_VS2022_INTEGRATION option. I understand this might be of more limited use.

EDIT: Otherwise, do you have any idea what would be needed for Visual Studio integration on the other platforms? I just wouldn't know where to start.

[wpbonelli]

VS integration is only applicable/relevant to windows AFAIK.

We've had requests before for specific options (also for intel) but cases like these could pile up quickly..

The oneAPI docs say the installer will try to do VS integration by default, so if we had an install_args or similar, we could remove the hard-coded disable (I think we did this for speed?) and let people turn integration off if they want?

Other similar actions have a generic input to tack arbitrary args onto a command, e.g. https://github.com/mamba-org/setup-micromamba?tab=readme-ov-file#custom-arguments. For us the executable/command to which the args will get sent will vary but I think the pattern should work. Maybe I'm not thinking about this right but my sense is it's best to stay toolchain agnostic

[H0R5E]

So I think an option should be something like bootstrapper_args as these would be passed to the bootstrapper for Windows and Mac. There doesn't seem to be an equivalent process for Linux. Personally, I don't see why it's necessary to pass options to apt or brew, given these can easily be done within a workflow, but I'm happy to be persuaded otherwise.

One question I have is whether user provided arguments should override all the defaults passed to the bootstrapper or whether they should be diffed somehow?

EDIT: I can not find any documentation regarding the options passed to these bootstrapper apps, BTW. Do you know where the options are described?

[wpbonelli]

I can not find any documentation regarding the options passed to these bootstrapper apps, BTW. Do you know where the options are described?

I'm looking at https://www.intel.com/content/www/us/en/docs/oneapi/installation-guide-windows/2025-0/command-line-options.html

There doesn't seem to be an equivalent process for Linux.

Yeah, linux the preferred install method is apt though they provide install scripts too IIRC.

Personally, I don't see why it's necessary to pass options to apt or brew, given these can easily be done within a workflow, but I'm happy to be persuaded otherwise.

Say with mac/brew you want to link against static libraries, if the toolchain package doesn't include them you may need to --enable-static in the formula then brew reinstall --build-from-source --formula /path/to/formula.rb. I think brew gcc ships with static libs but a different toolchain may not?

One question I have is whether user provided arguments should override all the defaults passed to the bootstrapper or whether they should be diffed somehow?

I think for intel we need to diff the component selection and/or extract it from provided args, since by default we select compiler components only — wouldn't be necessary if we included everything from hpc kit by default on windows like we do on mac but the windows install is painfully slow so we try to keep it minimal.

But then I think install-intel-windows.bat could become, assuming components are in %2 and remaining args are in %3

@echo off

:: download and unpack installer
curl.exe --output %TEMP%\webimage.exe --url %1 --retry 5 --retry-delay 5
start /b /wait %TEMP%\webimage.exe -s -x -f %TEMP%\webimage_extracted --log %TEMP%\extract.log
del %TEMP%\webimage.exe

:: run installer
- %TEMP%\webimage_extracted\bootstrapper.exe -s --action install --components=%2 --eula=accept -p=NEED_VS2017_INTEGRATION=0 -p=NEED_VS2019_INTEGRATION=0 -p=NEED_VS2022_INTEGRATION=0 --log-dir=%TEMP%
+ %TEMP%\webimage_extracted\bootstrapper.exe -s --action install --components=%2 --eula=accept --log-dir=%TEMP% %3

[H0R5E]

@wpbonelli

I'm looking at https://www.intel.com/content/www/us/en/docs/oneapi/installation-guide-windows/2025-0/command-line-options.html

Great, thanks, I could not get Google to help me find this.

I've actually managed to get my builds working using the examples in the oneapi-src/oneapi-ci repo. It's a really verbose solution, but it works for my particular needs. As such, I'm going to close this issue.

I understand that a general solution for supporting arbitrary toolchains is desirable, but I really don't feel confident implementing this, sorry.

Thanks so much for your help and best wishes,

Mat

[wpbonelli]

Excellent, glad you found a solution, I'd be curious to see the setup-oneapi solution if it is public by the way? We have wondered about this action's overlap with that one before.

Sorry for all the complications to a simple request- will post an update here if we end up supporting this in some way. Thanks for raising and walking thru this.

edit I see you said oneapi-ci, not setup-oneapi.

[H0R5E]

I'd be curious to see the setup-oneapi solution if it is public by the way?

Sure, it's the same workflow as before:

https://github.com/DTOcean/NEMOH/actions/workflows/release.yml

It references a bunch of scripts in the .github/scripts directory.

Thanks again for your help.