Medo has a simple Jamfile, with no dependencies. This is so that a person can build Medo without bringing in the entire Haiku source tree (just in order to get the jamrules). So to compile, just type:
And it will create a debug version for you (x64 version). To build a x32 version, I need to find out how to modify the Jamfile so that it references the correct freetype2 header path (interestingly, it’s different on x32 vs x64 builds), and I haven’t spend any time figuring out how to make a dynamically configurable jamfile. These days Medo builds under both x32 and x64 without errors once the freetype2 header path issue is addressed.
The script “create_package” is used to package the final product (it takes care of compiling in Release mode, setting the icon, setting attributes and copying everything into the package file directory, as well as setting up Deskbar link).
I also have a cmake file which does the same thing:
The binary size will be bigger using this method, especially the addons (20Kb vs 450Kb per addon). I didn’t spend any time trying to resolve this issue since I use jam.
QtCreator uses CMakeFiles.txt for dealing with Projects, and works very well when dealing with a pristine folder. However, if you manually type cmake CMakeLists.txt, QtCreator is confused by the output when parsing the CMakeLists.txt. So the habit I got into is to leave the CMakeLists.txt for QtCreator, and just use jam from the terminal to build, this way QtCreator doesn’t get confused with the output of cmake. Another +1 for jam.
Hope that helps, and feel free to email me personally if you want to avoid the forum.
solaja AT gmail DOT com