initial qmake build system

[kaniini]

This is an early work in progress set of project files for building audacious with qmake. Absolutely no effort at this time is made towards supporting Gtk+ builds with these.

I think that the Qt builds should use qmake and the Gtk+ ones should use autotools. Then we just delete the old autoconf based system after 3.6 is released, but this will allow developers to at least get used to working with qmake for their plugins in the plugins tree.

A similar infrastructure will appear for audacious-plugins soon.

[tallica]

👍

[tallica]

Maybe we should already start a 4.0 branch? Then we can remove autotools and GTK+ completely. /cc @jlindgren90

[kaniini]

yes, i would like that better

[jlindgren90]

I think it would be good to keep autotools and GTK+ as options in 4.0, but I certainly see no problem with having a branch that is Qt- and qmake-only. @tallica -- please feel free to start one (or resurrect the qt-integration branch).

[kaniini]

yes, i agree that it is probably a good plan to keep gtk+ as an option in 4.0, but i think that integrating it into the qmake buildsystem right now is a lower priority item.

there's a lot we need to figure out with qmake first, if you look at libaudcore's build files you'll see some interesting things (HARDCODE_BINDIR et al) that we need to sanely define at the project root.

[kaniini]

I replaced this with meson, but Meson will only support Qt for now. Legacy build system for legacy stuff, amirite?

[jlindgren90]

Sounds good. I want to keep autotools and GTK2 working still, but I have no problem with meson builds being Qt-only.

[kaniini]

Yeah, btw you might want to try building with Meson on Windows, it produces a nice Visual Studio solution for all of this stuff.