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

Interesting Linker/OneAPI integration issue

jimdempseyatthecove
Honored Contributor III
124 Views

Today, (working from memory) I opened a solution that I've been using for decades (and recently used without problems).

The Solution has multiple projects in Fortran (ifort due to debugging symbols issues) and icx C++ on MS VS Community 2022.

This time MS VS poped up a dialog asking to update the Solution (Projects) to use the current version of MS VS CRTL's  .AND. OneAPI icx

Like a noob, I said yes.

 

The interesting part is I can build a Release version (with different configuration name and minor option differences) with no problem. However, when I change the configuration to Debug, the build works, except two icx static libraries, which get built without error, are not linked. Resulting in missing symbols and obj's.

 

Checking the dependencies, the projects are selected (they were built on build all), but not linked.  I tried removing the dependencies and adding them back, but the link still failed.

Looking at the build logs from the working configuration and the non-working Debug configuration it is clear that the .lib files from those two projects were not linked.

My fix was to explicitly add the affected .lib files to the Solution's Source Files of the project with the linking issue. While this works, it is prone to potential error (should I relocate the solution)

 

Has anyone else had similar experience?

 

Jim Dempsey

0 Kudos
0 Replies
Reply