Writing own Makefiles

bash

(srs-- most of my development is embedded boards, where compile/link/build of the whole project is just a second or two.)

I like cmake because it has prettier build output

Please whatever you do please do not use cmake it's terrible for the users and its bloated as fuck.

How so? I'm curious because I've never actually used/installed cmake and probably never will have a use for it.

Write your own make files because it's simple and quickly done and anyone who lurks here is not going to write any complex software ever, anyway

Cmake is theoretically awesome but not quite so in practice. Last time I used it documentation was fairly shit and you can bet your ass that you'll end up writing a bunch of platform-specific shit for anything non-trivial. The syntax is pretty horrid and you'll have to learn it if you need to write any custom library finding module (which fairly likely).

scons is pretty epic

just use UNIX makefiles which can be run in any make.

touch Makefile

Makefile:
CFLAGS=-O69 -optimize-omg -other-shitCXXFLAGS=-std=c++11 -other-shitall: shit1 shit2shit1: dependenciesoffoo gcc foo $CFLAGSshit2: dependenciesofbaz g++ baz $CXXFLAGS

if you maintain your makefiles well it won't become ugly unlike the other fag says, unless it's a bloated piece of shit with 239487 dependencies and alternative switches and options

You shouldn't need make files if you are programming your own software. Make files are for people who are outside of the development environment but need the ability to compile specific options. That's all the purpose they serve.

I don't know what kind of non-trivial build requirements you have that aren't already covered in Cmake. Can you point to any public projects that cannot be solved with the existing Cmake system? Is your only objection about writing Cmake modules for searching libraries?