We're in the process of upgrading from IVF 11.1 on VS2008 to IVF Composer XE 2013. We have a large solution (200+ projects) with a mixture of C++ & Fortran DLL projects that have many dependencies between them. I understand that implicit linking of Fortran DLL projects with dependant C++ DLL projects using the project dependencies no longer works. I've moved to explicit linking of the dependencies using the 'Additional Dependencies' linker option as suggested, but this approach doesn't allow me to specify which are the dependant projects and hence the build order. If I leave the project dendencies in place, as well as specifying the explicit linkage, the link fails with messages like this:
1>------ Build started: Project: CLib2, Configuration: Debug Win32 ------
1> stdafx.cpp
1> CLib2.cpp
1> dllmain.cpp
1> Creating library C:\Data\MixedLanguage\MixedLanguage\Fortran_Calls_C\Debug\CLib2.lib and object C:\Data\MixedLanguage\MixedLanguage\Fortran_Calls_C\Debug\CLib2.exp
1> CLib2.vcxproj -> C:\Data\MixedLanguage\MixedLanguage\Fortran_Calls_C\Debug\CLib2.dll
2>------ Build started: Project: Fmain2, Configuration: Debug Win32 ------
2>Compiling with Intel(R) Visual Fortran Compiler XE 13.0.1.119 [IA-32]...
2>Fmain2.f90
2>Linking...
2>ipo: error #11018: Cannot open C:\WINDOWS\system32\C:\Data\MixedLanguage\MixedLanguage\Fortran_Calls_C\Debug\Fmain2.lib
2>LINK : fatal error LNK1104: cannot open file 'C:\WINDOWS\system32\C:\Data\MixedLanguage\MixedLanguage\Fortran_Calls_C\Debug\Fmain2.lib'
2>
2>Build log written to "file://C:\Data\MixedLanguage\MixedLanguage\Fortran_Calls_C\Fmain2\Debug\BuildLog.htm"
2>Fmain2 - 2 error(s), 0 warning(s)
========== Build: 1 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
How do I specify that the dependant C++ projects are built first?
Thanks
Dave