Long story short: Still havent managed to successfully run Ardour. I built mostly using MSYS2 MINGW64 on Windows, to build a version for windows. After configuration and installation, running the exe would give me errors, so I used an open source app called Dependencies to see which dlls were needed for all .exe’s in the lib and bin folder.
After managing to copy most of the listed dependencies using some scripts, the following dlls were missing (2 of them repeated):
For the lib folder: ext-ms-win-gdi-edgegdi-l1-1-0.dll
ext-ms-win-oobe-query-l1-1-0.dll
ext-ms-win32-subsystem-query-l1-1-0.dll
For the bin folder:
ext-ms-win-oobe-query-l1-1-0.dll
ext-ms-win32-subsystem-query-l1-1-0.dll
I put the (?) in the topic name because they’re apparently virtual/stub .dlls, and aren’t real files.
I assume trying to run the ardour .exe again and again to see which dll’s it lists as missing, after having copied most of the missing dll’s, will only make me go in circles.
Any ideas on how to proceed? I won’t count out trying to rebuild and reinstall ardour.
Edit: No more problem with missing .dll’s. I ended up using a command in MSYS2 to open Ardour, which worked: cmd //c "C:\\Ardour\\lib\\ardour9\\ardour-9.0.pre0.1864.exe (The name of the .exe will be different for you)
Please keep us informed about your progress. It’d be nice if there was an easy way to compile Ardour natively on Windows. So far only @John_E managed to pull that off with a custom setup that is not trivial to reuse.
Bit of an update. The ardour folder that I was using at the time of the 1st post had the ./waf configure --prefix as --prefix=/c/ardour. I’ve done a fresh install with the prefix set to --prefix=/mingw64, like my predecessors.
One key difference regarding the .dll’s missing: I had used scripts to copy missing .dll’s to the lib and bin subfolders, from /mingw64/bin. So the current attempt of copying the missing .dlls needed less copying for the bin folder, since some of ardour’s files ended up there. That being said, I still have to deal with the files in mingw64\lib\ardour9, especially since that’s where the ardour-9.0.pre0.1842.exe is. So I’ rephrase me saying “I’ve found the root problem” to “I’ve been taking the longer road.” [Well the less long road is still long…]
During this process, I’ve learnt to use -modules for the Dependencies command line tool. However, I think one or more of the scripts (in this 2nd attempt) made the others useless. So I have a little… cleanup, so to speak, to do.
