embedded programmers: 
i just came back from cramming the whole coke bottle in to this 32kb toaster we're about to implant in some guy's heart. i dunno we just used a makefile and two or three c files or something what do you mean build systems
chrome programmers:
i just came back from cramming the whole coke bottle in to this 32kb toaster we're about to implant in some guy's heart. i dunno we just used a makefile and two or three c files or something what do you mean build systemschrome programmers:
@icedquinn build systems you say?
>only writes sh
>only writes sh
@Mia ye i need to write some cards later.
mk 1 build systems are just that. some shell script that runs gcc.
mk 2's are the actual makefile/mk files
mk 3's are the ones that generate rules themselves like xmake and blaze.
cmake and jam are i dunno. i think those are still mark 2's in spirit because they still rely on hardcoded rules.
mk 1 build systems are just that. some shell script that runs gcc.
mk 2's are the actual makefile/mk files
mk 3's are the ones that generate rules themselves like xmake and blaze.
cmake and jam are i dunno. i think those are still mark 2's in spirit because they still rely on hardcoded rules.
Follow
@icedquinn @Mia
mk 4 is when your makefiles are interacting with a CI API.
@swiley @Mia 
how is that not just the script that generates the lower makefile
how is that not just the script that generates the lower makefile
@icedquinn @Mia It also triggers the build on another machine.
