4 ms·

Closed the page when I saw cmake mentioned

• benreesman 6y ago
  What should we be using? I’ve had nothing but trouble with Bazel and Buck (I’m a Buck committer). autotools is notoriously painful. Hand-written makefiles can be nice for smaller projects but get cumbersome with bigger projects. What am I missing?
  • dgellow 6y ago
    For small personal projects I started using dds: https://github.com/vector-of-bool/dds https://github.com/vector-of-bool/dds It's still very very young and in development, so not ready for prime time, but it "just works" and doesn't make me feel stupide the way CMake does...
    • benreesman 6y ago
      Thanks for the pointer, I'll take a look. CMake is definitely one of those tools where I look at the last project I was working on when I can to remember how to do stuff.
  • oscargrouch 6y ago
    I would recommend GN (https://gn.googlesource.com/gn/ https://gn.googlesource.com/gn/) It has almost the same syntax as Bazel, but its implemented in C++. Super-fast and tend focus on Ninja build files. I've even created a fork that works for Swift here and it works pretty well. Its the meta-build project for Chrome, so its optimized for big projects with a lot of dependencies. I dont actually understand why is not much widespread giving the bad shape of meta-build systems (like CMake).
• figomore 6y ago
  Cmake is used to generate the json file that clangd uses to do the autocompletion. You can use other tool, like meson, or even create the json file by hand.