Note that there are some explanatory texts on larger screens.

plurals
  1. POMakefile generators: premake vs bakefile?
    primarykey
    data
    text
    <p>For my C++ build process, I am using <a href="http://www.bakefile.org/index.html" rel="noreferrer">Bakefile</a>, a nice little Makefile generator, which lets you specify your build targets in XML, and it can generate various Makefiles or project files from it. It works fine and I use it to generate the GNU autotools scripts. </p> <p>Now I heard of <a href="http://premake.sourceforge.net/" rel="noreferrer">Premake</a>, which seems to have a similar functionality. You specify your targets in <a href="http://www.lua.org/" rel="noreferrer">Lua</a>, and it generates Makefiles accordingly.</p> <p>Does anyone know the differences between Bakefile and Premake? Does anyone have experience with both? Premake seems more recent and with more active development?</p> <p>The XML parser <a href="http://code.google.com/p/ticpp/source/browse/trunk/build_instructions.txt" rel="noreferrer">ticpp</a> uses Premake, but it requires you to download premake before you build ticpp. Can't they just pre-generate Makefiles for various systems so you don't have to download and install premake first?</p> <p><strong>Note:</strong> I know there are various SO threads about what the best build tool is, and usually the answer is <a href="http://www.cmake.org/" rel="noreferrer">CMake</a>, <a href="http://www.scons.org/" rel="noreferrer">SCons</a> or <a href="http://www.perforce.com/jam/jam.html" rel="noreferrer">Jam</a>. However, I am interested in something that my users won't have to download before they build my project. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload