Premake whopping rocks! (or how Boost Build whopping sucks, or how to build Luabind for iOS proper)
Last time I wrote about how to build Luabind on OS X. Well, it turned out that was only half the battle won. Building Luabind for iOS (ARMV7) architecture just plain doesn’t work. It seems like some people have managed to make it work but none of what I have found actually worked. If you are reading this, I suppose you are also tired of jumping through hoops just to compile the damn thing, well, Premake to the rescue.
Let me tell you, this is how building stuff in C++ is meant to work:
Just create a file premake4.lua
1 2 3 4 5 6 7 8 9 10 | -- premake4.lua solution "luabind" configurations { "Release" } project "luabind" language "C++" kind "StaticLib" flags { "Optimize" } includedirs { ".", "/usr/local/include", "/where/is/your/lua" } files { "src/**" } |
That is ALL THERE IS TO IT!
1 2 3 | $ premake4 xcode3 $ xcodebuild -sdk iphonesimulator -configuration Release -arch i386 $ xcodebuild -sdk iphoneos -configuration Release -arch armv7 |
Boost Build whopping sucks. Premake is written by one guy and this turns out to be so trivial (as it should be).
Hope it helps.
Yeah definitely ! You can do simple things in a simple way with premake, but you can also do much more complex things (several configurations like debug, release, 32bit, 64bit, windows, macOS) and it never gets too complicated. We use premake to manage our code AND all our dependencies, passing the version numbers as options. Single click solution building
Comment by Denis on January 12, 2012 at 8:10 am
Now it’s also possible to use Premake for building Qt projects. More details in announcement here:
http://industriousone.com/topic/full-stack-qt-based-development-premake-available-download
Comment by Konstantin Tokarev on January 27, 2012 at 12:35 am