[flagged]
Show HN: I built a Cargo-like build tool for C/C++
171–180 of 181 posts
Re: Show HN: I built a Cargo-like build tool for C/C++
#172Earlier quoted context omitted.
If you'd just left off "to fuck" you'd end up way less downvoted, if it even happened at all.
Probably not. This isn't prime time TV, some foul language is tolerated - but complaining about down-votes, especially preemptively, has a predictable response (IMO rightfully so).
No complaints about down votes, simply warning the OP that (s)he will be getting some. Personally I quite like them, they indicate that I've irritated a Rust evangelist; that gives me a warm feeling inside.
Re: Show HN: I built a Cargo-like build tool for C/C++
#173Earlier quoted context omitted.
… not everyone uses the cloud? Some people, gasp , run physical hardware, that they bought.
So you buy exact same generation of Intel and AMD chips to your developers than your servers and your cutomsers? And encode this requirement into your development process for the future?
[flagged]
Re: Show HN: I built a Cargo-like build tool for C/C++
#174KDE already has a meta-build tool for C++ called Craft, which handles dependency management and cross - compilation for CMake-built applications and libraries.
AFAIK, Craft is only the most popular tool to build KDE software on (or perhaps for) Windows. On Linux, it's kdesrc-build (OG, Perl) or kde-builder (more recent, Python).
Re: Show HN: I built a Cargo-like build tool for C/C++
#175If you think cmake isn't very good, the solution isn't to add more layers of crap around cmake, but to replace it. Cmake itself exists because a lot of humans haven't bothered to read the gnu make manual, and added more cruft to manage this. Please don't add to this problem. It's a disease
CMake does three main things: Compilation with dependency tracking, finding external dependencies, and platform-independence. Make only does one of them.
Another comment suggested batch files - these do zero out of three.
Re: Show HN: I built a Cargo-like build tool for C/C++
#176[flagged]
Craft has a few commands to handle dependencies: craft add, craft update, craft remove. Craft add can take a path to a local Craft project and link it, or it can take a git url which will be cloned and linked automatically. Craft update updates a specific git dependency in your project to the newest version or updates all. Craft remove removes a dependency from your project.
Re: Show HN: I built a Cargo-like build tool for C/C++
#177In the age of AI tools like this are pointless. Especially new ones, given existence of make, cmake, premake and a bunch of others. C++ build system, at the core, boils down to calling gcc foo.c -o foo.obj / link foo.obj foo.exe (please forgive if I got they syntax wrong). Sure, you have more .c files, and you pass some flags but that's the core. I've recently started a new C++ program from scratch. What build system…
You're missing finding library/include paths, build configuration (`-D` flags for conditional compilation), fetching these from remote repositories, and versioning.
Also other tasks like compiling resource or translation files.
Re: Show HN: I built a Cargo-like build tool for C/C++
#178[dead]
Re: Show HN: I built a Cargo-like build tool for C/C++
#179this is really interesting +1 star
PS is there a plan to include hermetic builds, from local sources / git submodules?
Re: Show HN: I built a Cargo-like build tool for C/C++
#180Earlier quoted context omitted.
What part of the build process is different for C?
I explained why C/C++ rubbed op the wrong way. It has nothing to do with a build process. It is probably true that more average C programs can be built with plain Makefiles or even without a Makefile than C++, though. You can of course add dependencies on configure scripts, m4, cmake, go, python or rust when building a plain self-contained C program and indeed many do.
Well the post is about build tools, so I assumed we were talking about that.