8 ms·
Here is all that you need for a small C project, say an executable. project('hello', 'c') executable('hello', 'hello.c') Obviously use what you are co
by tristan957 4y ago
Here is all that you need for a small C project, say an executable.
project('hello', 'c')
executable('hello', 'hello.c')
Obviously use what you are comfortable with, but I don't see how this is overly complicated.
- Koshkin 4y agoI guess, the point was, you do not actually need this for a small project, and for a larger project it would look dreadfully complex.
- tristan957 4y agoIf you are the only contributor, target one compiler, and one platform, then sure. > for a larger project it would look dreadfully complex How so? How do you avoid complexity?
- vbezhenar 4y agoNow add something like clang with custom wasm flags there. Or Tigress for obfuscation. Launch node.js app for testing after build. Few obvious lines in shell script. I guess few weeks of learning the tools with other approaches. My unprofessional approach to C so far was to avoid libraries, even most standard library and write very simple C code (avoid C++ as well). Simple C code compiles at tremendous speed. Something like 100k lines per second or even faster. Especially if you don't need optimization (for development cycles). So you don't need to think about incremental compilation and things like that and it makes everything dumb simple.