| ▲ | monkeyelite 16 hours ago | |||||||||||||||||||||||||
You can use make without configure. If needed, you can also write your own configure instead of using auto tools. Creating a make file is about 10 lines and is the lowest friction for me to get programming of any environment. Familiarity is part of that. | ||||||||||||||||||||||||||
| ▲ | viraptor 15 hours ago | parent | next [-] | |||||||||||||||||||||||||
It's a bit of a balance once you get bigger dependencies. A generic autoconf is annoying to write, but rarely an issue when packaging for a distro. Most issues I've had to fix in nixpkgs were for custom builds unfortunately. But if you don't plan to distribute things widely (or have no deps).. Whatever, just do what works for you. | ||||||||||||||||||||||||||
| ▲ | edoceo 15 hours ago | parent | prev [-] | |||||||||||||||||||||||||
Write your own configure? For an internal project, where much is under domain control, sure. But for the 1000s of projects trying to multi-plarform and/or support flavours/versions - oh gosh. | ||||||||||||||||||||||||||
| ||||||||||||||||||||||||||