Maintainers please note: Currently although the build succeeds, I can't use this package to build qtutilities, because of an issue with making this package split to multiple outputs - the .cmake files end up in the default out output's directory and not in the dev output's directory. I'm working on a fix for that now.

Update: I've removed the outputs' split - there's only out now. The problem is that the .cmake files in $out/share/c++utilities/ point to paths with ../../../ and I don't think it would would have been safe / easy to use sed and hardcode $dev instead. I don't know cmake syntax good enough to know how to do it.

But indeed, this makes the package be a bit big in terms of disk size because of the headers and every file that's not a shared library in it's output. If anyone has any suggestions / ideas, I'm all ears.

Besides this small imperfectness, I think it's ready for others to test.

if the package gets too big then split outputs look the way forward. I don't know how other packages do it, maybe you can find one and look how they do it. You may need upstream changes or use substituteAll (the nix abstraction over sed)

Thanks for commenting @teto, this package is not that big with the development files included. It's just a sort of opinion of mine I tried to elevate when trying to split this package - In general, I think when a user installs a package he shouldn't even download to the his /nix/store development files.

I'll might talk about this with the upstream developer - to make this easier for us or get a hint at how I can use our sed abstractions to fix the paths on our end. In the meantime we'll just stick with having only 1 output. I'll note also that qtutilities which depends on this and it will be packaged in an upcoming PR, compiles fine with the single output.

All commits were squashed, it's ready for testing, please tell me if there's anything else to take care of.

@GrahamcOfBorg build cpp-utilities

Thanks!