4 ms·
I admit the C/C++ build setup has deterred me from prototyping at times. I used to solve this by keeping a sandbox project where I replace code in main().
by arketyp 4y ago
I admit the C/C++ build setup has deterred me from prototyping at times. I used to solve this by keeping a sandbox project where I replace code in main().
- c0balt 4y agoSimiliar story for me with rust and js. The cost for the first setup with everything dialed in just right (proper linker, comp flags...) is often deterring for the prototyping stage. Maybe that's a case for boilerplates? Idk, though I really liked the idea of create-react-app and co.
- jhgb 4y agoI got lazy and installed https://github.com/ryanmjacobs/c https://github.com/ryanmjacobs/c . (Other than that, I intend to learn Zig including its C++ build capabilities.)
- arinlen 4y ago> I admit the C/C++ build setup has deterred me from prototyping at times. I don't understand how that can be a barrier to entry. There are plenty of free IDEs which already create ready-to-go projects, and build systems such as cmake make it quite trivial to setup a C++ project from scratch. Case in point: project(foo LANGUAGES CXX) add_executable(foo main.cpp) https://cmake.org/cmake/help/latest/guide/tutorial/A%20Basic%20Starting%20Point.html https://cmake.org/cmake/help/latest/guide/tutorial/A%20Basic...