FWIW: there is something fundamentally wrong with a meta-meta build system. I don't think you should bother generating or wrapping CMake, you should be replacing it.
Show HN: I built a Cargo-like build tool for C/C++
11–20 of 181 posts
Re: Show HN: I built a Cargo-like build tool for C/C++
#12The installation instructions being a `curl | sh` writing to the user's bashrc does not inspire confidence.
Re: Show HN: I built a Cargo-like build tool for C/C++
#13The installation instructions being a `curl | sh` writing to the user's bashrc does not inspire confidence.
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | shRe: Show HN: I built a Cargo-like build tool for C/C++
#14FWIW: there is something fundamentally wrong with a meta-meta build system. I don't think you should bother generating or wrapping CMake, you should be replacing it.
Just alone reverse engineering the Xcode and Visual Studio project file formats for each IDE version isn't fun, but this "boring" grunt work is what makes cmake so valuable.
The core ideas of cmake are sound, it's only the scripting language that sucks.
Re: Show HN: I built a Cargo-like build tool for C/C++
#15Re: Show HN: I built a Cargo-like build tool for C/C++
#16Re: Show HN: I built a Cargo-like build tool for C/C++
#17FWIW: there is something fundamentally wrong with a meta-meta build system. I don't think you should bother generating or wrapping CMake, you should be replacing it.
My thoughts exactly. I thought this was going to be some new thing, but it's just yet another reason that I'll stick with Makefiles.
Re: Show HN: I built a Cargo-like build tool for C/C++
#18How does craft handle these 'diamond' patterns where 2 dependencies may depend on versions of the same library as transitive dependencies (either for static or dynamic linking or as header-only includes) without custom build scripts like the Conan approach?