Same concept, but completely different implementation.

still slow, even if it does multiple processes - lots of "discovery" that are only on your machine, or whatever the CI machine had in mind. Instead it should be - "You should expect this, that and that", and by nature of building it - it fails.

Discovery is the wrong thing to do nowadays.

▲

ahartmetz 3 months ago | parent [-]

I don't think I'd want a "fail late with a possibly unclear error" build system. There is also the problem that finding the path of dependencies happens at the same time as finding if you have them, and removing one without the other doesn't seem to be very useful.

At best, I think you could have a system that defers some / most dependency discovery until after configure time, but still aborts the build with "required libfoo >= 0.81.0 not found" if necessary.

And no, you are not going to be able to tell everyone exactly where everything needs to be installed unless it's an internal product.

	▲	malkia 3 months ago \| parent [-]
		Sure, to all to their needs. In my case I want reproducible build, but to start I first want build that at least passes the same compiler flags around, and links same things no matter what the computer is (it can still be different when comes to OS).