Installation and building of tools should be optional with CMake

[JayFoxRox]

I'm compiling for an embedded platform and the toolchain expects a system-wide install (so I use cmake .. -DCMAKE_TOOLCHAIN_FILE=[...] && make install).

The midifile library compiles fine.
However, compilation will still fail because the toolchain does not support some C++ features like cin which is used in tools/type0.cpp.
Because there won't be any way to run these tools I shouldn't even have to build them in the first place.

Therefore, compiling tools or examples should be made optional.
I only want to install the core library.

(I'll look for a different MIDI lib for now, but will keep an eye on this if I can't find a suitable alternative)

[julian-pfaul]

Section of the README file:

Using in your own project

The easiest way to use the midifile library in your own project is to copy the header files in the include directory and the source-code files in the src directory into your own project. You do not need to copy Options.h or Options.cpp since the MidiFile class is not dependent on them. The verovio and midiroll projects on Github both use this method to use the midifile library. Alternatively, you can fork the midifile repository and build a compiled library file of the source code that can be copied with the include directory contents into your project.

[JayFoxRox]

I understand it can be vendored, but it's entirely unrelated to problems when using CMake / installing system-wide.

I also consider vendoring a bad approach / anti-pattern as you wouldn't automatically get updates and you'd have to do manual steps for this particular project, rather than doing the standard CMake steps which work for many other software libraries.

However, since I created this issue, this was - at least partially - fixed in #117.
There are, however, still some problems as mentioned in #117 (comment).

[julian-pfaul]

You're right, I apologize. My comment was unnecessary! :)