Hmmm, using the referenced G-P code here is easy enough.

Even that is overkill, we could probably just stick a `-std=c99` into the `CFLAGS` and nobody would ever notice. AFAIK all the compilers we support or care about support that (gcc, clang, intel, even watcom and others). MSVC notoriously doesn't support C99 anyway (at least until recently, somewhat), but we don't support that anyway, really, and the referenced code doesn't either, AFAICT.

My only concern are the Windows builds. If anyone wants to continue providing the Windows releases in an adequate quality, then let's drop Waf now.

How much of it is Waf-specific? Is it the case that if the Autotools build system could generate nice win32 binaries (geany.exe+libgeany.dll, with resources compiled-in, etc), that you could use most of your release process still, or is a lot of it automated by Waf scripting?

It's a pain having multiple build systems sometimes, but IMO quality win32 releases are much more important.

--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/679#issuecomment-146385400

MSYS2 builds are just as high quality has waf ones.

what is this in reference to? and what MSYS2 builds?

--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/679#issuecomment-146553197

My concerns are not only about building the code itself, getting the code compiled into geany.exe and libgeany.dll is easy enough, with autotools, Waf and even hand-written Makefiles. The fun begins with the stuff around, basically the 'make install' part with all those Windows specials, renaming text files (README, etc.) to *.txt , signing binaries, creating the GTK runtime bundle and last but not least the installer.

If @kugel- can guarantee all this for Geany and Geany-Plugins in the same or better quality than before, then I'd be fine to drop Waf immediately. But if not, we first need to sort remaining problems out.

--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/679#issuecomment-147093487

To some extend, yes. The next release is about in four weeks. I, for myself, probably will not be able to port the Windows builds to MSYS2 including plugins in that time completely.

Maybe I said I will have a look, if so, I didn't :(. Did you continue working on the bundle?

In case we won't drop Waf for 1.26, I guess we should declare dropping Waf and finishing MSYS2 support for Geany and plugins as a goal for 1.27 to finally get it done.

--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/679#issuecomment-147250283

Ok. My suggestion: let's keep Waf for one more release, 1.26 and then work hard on getting it removed by finishing the MSYS2 support, for Geany *and* plugins.

@b4n, @kugel- agree?

--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/679#issuecomment-147841365

Fine with me too.

However, MSYS2 creates fine builds today, so you can just set that up and try :-) IIRC the only challange was creating the zip with all of geany's dependencies

--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/679#issuecomment-147863341

If WAF is going to be dropped, maybe it should give a deprecated message when its run?

--- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/679#issuecomment-148525367