They apparently only have Makefiles as a common use standard.
Why are there no standard package managers for C/C++
Christian Walker
Other urls found in this thread:
Matthew Miller
Because projects back then were not so much monolithic.
Think about windows. It's terrabytes of codes.
Plus internet wasn't popular back in the early '80s.
It's a mistake C/C++ cannot and will not be able to fix.
Gabriel Sanchez
Just use your system's package manager, idiot.
Nathan Walker
Because the C and C++ ecosystems are much more broad and complicated than you seem to think.
Henry Myers
Every fucking time
Evan Cruz
No. Moron.
I use windows. And you can't use the chocolatey-package-manager for windows to package and build c applications on their own
Liam Collins
elaborate plox
Elijah Price
>I use windows.
My condolences
David Powell
If the standard's committee were to ask for a package manager, then most implementations would become non-standard, because there's a lot of complicated shenanigans behind making and maintaining a package manager, not to mention one that can span multiple OSs, architectures and environments.
Xavier Ramirez
BTFO
Jason Rodriguez
As a developer I don't want a package manager for C/C++. It's bad enough when shit auto updates and other people's programs break. I don't want shit to auto update and break my own code.
Consistency > all
Samuel Richardson
Because C and C++ compiler vendors and the standard committees can't even agree on how to fry much smaller fishes.
Basically , although the standard library and tools could be modular enough to span multiple OSs, architectures, environments and what not.
Jonathan King
>emerge libwhatever
Was that so difficult?
Robert Robinson
Rust and Cargo are like a dream
Julian Taylor
...
Adam Sanders
>Cargo is like a dream
Good joke.
Jaxon Robinson
>Not adopting the most versatile, stable and source-friendly option as the default
shiggy your diggies you aptfags
Blake Perez
What alternative do you have, brainlet?
Zachary Cruz
vcpkg MSVC
msys2 mingw.
No excuses.
Adam Jackson
This.
All you have to do is [package] and few other details
"cargo build" and builds the entire thing! So easy! None of that $(cc) -o $(objects) -w $(Libs) nonsense in c//++ that makes everything fragmented and too complex and buggy
Oliver Moore
>Having an install script instead of just creating a package for the package manager
Thomas Adams
>No excuses.
INFERIOR COMPILER
Robert Campbell
>having leftovers from the install script
Thomas Roberts
Because
>Header files.
Rust will fix this.
Ethan Davis
no need for them
>Makefiles
make is not a package manager
Chase Diaz
> inferior compiler
> produces better code
> dozens of plugins
i hope u are joking :)
Camden Howard
Create a Docker image that has the dependencies.
Then, in your makefile, do:
build\ in\ container:
docker container run -v $(shell pwd):/src/ my_build_image
Now, run make 'build in container'.
Dependency problem solved on Linux.
/thread
Brandon Rogers
apt install boost-devel
Austin Rodriguez
>solved
but I don't have docker
Christopher Ortiz