C++ header files and crash issue

[René J.V. Bertin]

On Monday July 08 2019 13:18:50 Steve the Fiddle wrote:
>We previously had a Linux developer that was very keen on make /
>autotools, hence our reliance on that tool chain on Linux. Personally I
>would very much like us to use cmake on all platforms

I have begun to notice that many core Linux/GNU projects are moving to Meson, so even "those guys" must have begun to notice the overhead of using autoconf/automake (including build overhead because every build command is handled by a script that has grown a lot no longer takes a negligible processing time.

You already have a cmake system that works on one of the supported platforms. It shouldn't be rocket science to start adding support for at least Linux, given the way Audacity's sources are organised and the way cmake works. Cmake has much more of a traditional programming language than autoconf, and doesn't have the separation between template configure files and template makefiles.

>In most cases, when building from the command line, Audacity will build
>against a system installed wxWidgets without needing to specify where it is
>installed.

A proper build system doesn't concern itself only with the "most cases". One very common reason why you'd at least want to document this particular aspect is that wxW. is designed to support multiple concurrent versions that each come with their own wx-config script.

>current kDevelop AppImage, and the previous 5.2 version. I'd be surprised
>if it is not repeatable for other users with that (Audacity) code and the
>kDevelop AppImage. If this email list is not the correct place to report
>crash problems, I'll be happy to repost this specific issue if you can
>point me to the correct place.

Didn't you say something about RTFM? :P It's all documented (and almost every full-blown KDE application has a menu command for reporting bugs).

R.