I moved the instructions here as per an Ardour dev's request: https://github.com/defcronyke/ardour/blob/win64-mingw-msys/doc/unofficial_mingw64_msys2_build_instructions.txt
And here is a pull request where the howto is being considered: https://github.com/Ardour/ardour/pull/278
As far as I have been told, no-one has been attempting Ardour builds on MinGW64 MSYS2, compiling for Windows on Windows for quite some time, and you only have to try it for yourself to see that the build process on Windows doesn't work. I will be using Windows for a while now, so I'd like to help bring better Windows support to Ardour.
The nightly Windows builds are cross-compiles AFAIK, so even if those were working, which they currently aren't: https://nightly.ardour.org/i/A_WIN_x86_64/build_log.txt
... that doesn't mean Ardour will build on Windows.
Also, Ardour devs don't want to share their Windows build scripts for some reason, so I'd like to fill in what they leave out.
The reason I announce this on LAU is because I am a Linux audio user who has recently moved to Windows (I still use Linux in a VM for most things, but VMWare Player doesn't play nice with Ardour/Jack, so I'm stuck using Ardour in Windows), and now I am going to great lengths to make sure I can use my favourite Linux software on Windows. And I would like other potential Windows Ardour devs to have an easier time getting set up than I did. Ardour and Zyn are really Linux software, they were born into Linux, and they work best on Linux, so I still think this thread is relevant for LAU.
Regards,
Jeremy Carter
On Mon, Oct 3, 2016 at 9:28 AM, Chris Caudle <chris@xxxxxxxxxxxxxxx> wrote:
> https://github.com/defcronyke/ardour/tree/win64-mingw-msys/ mingw
404 not found error
> It's not easy as neither projects would build on Windows without patching
> many files,
That seems very odd, as Windows is an officially supported platform for
Ardour now, and in fact the nightly builds now build for Ardour every day.
I would think it very unlikely that Ardour would need "many files"
patched to get it to build on Windows, as a broken nightly build would be
noticed very quickly (certainly within 24 hours).
Have you been in contact with the Ardour developers to determine why there
is a disconnect between your experience and the other Ardour on Windows
developers?
And just a philosophical question, why would you announce information
about Windows builds on the Linux Audio mailing list instead of the Ardour
Users mailing list? The latter users you know are already interested in
Ardour, the former users you (should) know are (most likely) not
interested in Windows.
--
Chris Caudle
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
_______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/listinfo/linux-audio-user
