search

jamulussoftware / jamulus

Jamulus enables musicians to perform real-time jam sessions over the internet.
https://jamulus.io
Other
997 stars 222 forks source link

Windows build reports Error: The clangbackend executable could not be started #1088

Closed pljones closed 3 years ago

pljones commented 3 years ago

Describe the bug Changes to the Windows build process have had an adverse effect.

EDIT ((FAILED)Still to do(FAILED): reproduce initial problem with warnings about character sets... My computer turned itself off before I could cut-n-paste those..!! Very strange for it to do that - it was really struggling with the build. EDIT2 Very strange. I can't reproduce the issue with the character set warnings.)

To Reproduce

  1. Install MSVC2017, jom and Qt Creator 4.11.0
  2. Download the Jamulus repo and install ASIOSDK2.3 (as windows\ASIOSDK2)
  3. Configure Qt Creator

Expected behavior No "error" messages and a successful build.

Screenshots

2021-02-22T18:10:26 Clang Code Model: Error: The clangbackend executable "D:\Qt\Tools\QtCreator\bin\clangbackend.exe" could not be started (timeout after 10000ms).
Project MESSAGE: building version "3.6.2dev-6e630f4-dirty" (intermediate in git repository)
Project MESSAGE: building version "3.6.2dev-6e630f4-dirty" (intermediate in git repository)

Operating system Windows 10.

Version of Jamulus Git master source

ann0see commented 3 years ago

I‘m a bit surprised of that. The new build script shouldn’t touch compilation of the jamulus source at all. Maybe it’s related to the change with the version number?

hoffie commented 3 years ago

Can you run a test with a known-good version (r3_6_2?) in that same environment? Could it be just some generic Qt problem? Just found that people report such problems all over the place, sometimes with "If I try multiple times, it sometimes works" or "won't work at all": https://bugreports.qt.io/browse/QTCREATORBUG-20791

pljones commented 3 years ago

r3_6_2 doesn't give those messages.

From opening Qt Creator with r3_6_2 (cleaned, and deleted build folders):

jom 1.1.3 - empower your cores

22:40:16: The process "D:\Qt\Tools\QtCreator\bin\jom.exe" exited normally. 22:40:16: Starting: "D:\Qt\Tools\QtCreator\bin\jom.exe" D:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Release ... link /NOLOGO /DYNAMICBASE /NXCOMPAT /DYNAMICBASE:NO /INCREMENTAL:NO /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='' processorArchitecture=''" /VERSION:3.6 /MANIFEST:embed /OUT:release\Jamulus.exe @D:\TEMP\Jamulus.exe.2900.90641.jom Creating library release\Jamulus.lib and object release\Jamulus.exp 22:41:50: The process "D:\Qt\Tools\QtCreator\bin\jom.exe" exited normally. 22:41:51: Elapsed time: 01:50.


-----

From opening Qt Creator with master@0a3dad19 (cleaned, and deleted build folders)
* General Message

Running Windows Runtime device detection. No winrtrunner.exe found. Running Windows Runtime device detection. No winrtrunner.exe found. Running Windows Runtime device detection. No winrtrunner.exe found. Project MESSAGE: building version "3.6.2dev-0a3dad1-dirty" (intermediate in git repository) Project MESSAGE: building version "3.6.2dev-0a3dad1-dirty" (intermediate in git repository)

So the

2021-02-22T18:10:26 Clang Code Model: Error: The clangbackend executable "D:\Qt\Tools\QtCreator\bin\clangbackend.exe" could not be started (timeout after 10000ms).

has gone away.  I'll have to put it down to _Windows Behaving Badly_.

(empty compile window)
Then build...
* Compile output

22:47:34: Running steps for project Jamulus... 22:47:34: Starting: "D:\Qt\5.12.2\msvc2017_64-static\bin\qmake.exe" O:\git\Jamulus-wip\Jamulus.pro -spec win32-msvc "CONFIG+=qtquickcompiler" Info: creating stash file D:\TEMP\build-Jamulus-Desktop_Qt_5_12_2_MSVC2017_64bit_static-Release.qmake.stash Project MESSAGE: building version "3.6.2dev-0a3dad1-dirty" (intermediate in git repository) Project MESSAGE: building version "3.6.2dev-0a3dad1-dirty" (intermediate in git repository) Project MESSAGE: building version "3.6.2dev-0a3dad1-dirty" (intermediate in git repository) 22:47:52: The process "D:\Qt\5.12.2\msvc2017_64-static\bin\qmake.exe" exited normally. 22:47:52: Starting: "D:\Qt\Tools\QtCreator\bin\jom.exe" -f D:/TEMP/build-Jamulus-Desktop_Qt_5_12_2_MSVC2017_64bit_static-Release/Makefile qmake_all

jom 1.1.3 - empower your cores

22:47:52: The process "D:\Qt\Tools\QtCreator\bin\jom.exe" exited normally. 22:47:52: Starting: "D:\Qt\Tools\QtCreator\bin\jom.exe" D:\Qt\Tools\QtCreator\bin\jom.exe -f Makefile.Release ... link /NOLOGO /DYNAMICBASE /NXCOMPAT /DYNAMICBASE:NO /INCREMENTAL:NO /SUBSYSTEM:WINDOWS "/MANIFESTDEPENDENCY:type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' publicKeyToken='6595b64144ccf1df' language='' processorArchitecture=''" /VERSION:3.6 /MANIFEST:embed /OUT:release\Jamulus.exe @D:\TEMP\Jamulus.exe.6180.96125.jom Creating library release\Jamulus.lib and object release\Jamulus.exp 22:49:32: The process "D:\Qt\Tools\QtCreator\bin\jom.exe" exited normally. 22:49:32: Elapsed time: 01:58.


It really is quite insistent about

Project MESSAGE: building version "3.6.2dev-0a3dad1-dirty" (intermediate in git repository)


though :)
ann0see commented 3 years ago

Just one thing I just came up with: the qt installer file was changed too: https://github.com/jamulussoftware/jamulus/blob/master/windows/qt-installer-windows.qs

hoffie commented 3 years ago

Just one thing I just came up with: the qt installer file was changed too: https://github.com/jamulussoftware/jamulus/blob/master/windows/qt-installer-windows.qs

If reverting that for testing doesn't help, someone who can reproduce could try a git bisect? It's a bit time-consuming, but almost guaranteed to lead to the problem in the fastest, strucuted way if one can easily tell known good / known bad apart.

pljones commented 3 years ago

I couldn't actually reproduce it - scrubbed all the build files away with Qt Creator closed and it stayed gone. My PC was definitely having a bad day. Windows... gotta love it...

pljones commented 3 years ago

Closing.