Unresolved external symbol while building Installer Framework

**ikarona** · 16th March 2025, 16:33

Hi! Thank you for you reply!
I'm calling

Qt Code:

Switch view

call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x64 10.0.17763.0

call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x64 10.0.17763.0

To copy to clipboard, switch view to plain text mode

On every build. It's script which setups env variables

**d_stranz** · 16th March 2025, 20:35

Are the environment variables set using the "call" command preserved after the call returns? I usually run build scripts from inside a developer command prompt. This guarantees that anything executed within that prompt inherits the build environment. Try commenting out your "call" statement and then executing your script inside the developer command window.

**ikarona** · 16th March 2025, 20:52

I made this a single script file:

Qt Code:

Switch view

call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x64 10.0.17763.0
SET QTDIR=D:\tfgit\qt\qt_test2\qt_test\qt5\qt5_build\qtbase
SET QTDIR_LIB=%QTDIR%\lib
SET PATH=%QTDIR%\bin;%QTDIR%\..\..\gnuwin32\bin;%QTDIR_LIB%;D:\tfgit\qt\qt_test2\installer-framework\lib;%PATH%
 
call qmake.exe "LIBS+= -LD:\tfgit\qt\qt_test2\qt_test\qt5\qt5_build\qtbase\lib -LD:\tfgit\qt\qt_test2\qt_test\qt5\qt5_build\qtbase\bin -LD:\tfgit\qt\qt_test2\installer-framework\lib" && ^
call nmake && ^
call nmake install

call "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" x64 10.0.17763.0
SET QTDIR=D:\tfgit\qt\qt_test2\qt_test\qt5\qt5_build\qtbase
SET QTDIR_LIB=%QTDIR%\lib
SET PATH=%QTDIR%\bin;%QTDIR%\..\..\gnuwin32\bin;%QTDIR_LIB%;D:\tfgit\qt\qt_test2\installer-framework\lib;%PATH%
 
call qmake.exe "LIBS+= -LD:\tfgit\qt\qt_test2\qt_test\qt5\qt5_build\qtbase\lib -LD:\tfgit\qt\qt_test2\qt_test\qt5\qt5_build\qtbase\bin -LD:\tfgit\qt\qt_test2\installer-framework\lib" && ^
call nmake && ^
call nmake install

To copy to clipboard, switch view to plain text mode

So after call vcvarsall.bat is executed all variables are definitely set during build-script execution. Otherwise nmake command wouldn't have been be found.

I tried simply running it from developer command prompt(vs 2017): same result, no changes: 38 unresolved external symbols.

**d_stranz** · 17th March 2025, 13:27

Well, sorry. Are you sure that you are linking to the correct libraries? In Windows, you cannot mix Release and Debug or 32- and 64-bit libraries. A 64-bit Debug build must be linked with 64-bit Debug libraries, likewise for Release and 32-bit builds. Turn on a verbose build and have it write a log file so you can see all the details.

Otherwise, I do not know what else to suggest.