Or do I just post to this forum?
If I can figure out how the code works, I may be able to do some bug squashing next month. At the very least, I should be able to do some crash reporting.
I haven't been near C++ in a very long time, but did some significant Qt coding back then (probably Qt3, perhaps Qt4).
My first task is to git the source tree and compile/install it to a non-root location (my sandbox). I'm running debian stable with the stock kernel (it's not RT, but there is a RT kernel package in the distribution if I need it, and I can compile my own if necessary). I want to keep things as vanilla as possible.
The first thing I found is that in the README, under Building MusE under Debian/Ubuntu:, the apt-get list should include the package
extra-cmake-modules
The second is that neither README nor README.developer say how to change the installation location, say to a home directory. Only KDE developers are likely to know how to manipulate the extra-cmake-modules script. The rest of us will be mystified, since the standard cmake way is to use the --prefix option, which doesn't work. (The information is on the website, but it should be in the src tarball.)
What is the standard/expected tool for generating API documentation? In the old days, doxygen was common, but I didn't see any doxygen markup in the (rather lean) source comments. My world has been python for a long time, so I don't know what C++ users do these days.
Statistics: Posted by anxrun — Sat Nov 16, 2024 2:33 pm