[libblockdev 0/4] Would like to use scons instead of make

David Shea dshea at redhat.com
Wed Jul 9 21:45:09 UTC 2014


On 07/09/2014 04:56 PM, Anne Mulhern wrote:
>
> * Does scons handle soname/soversion/other shared object stuff correctly?
>
> All the rumours are bad, but also old. It definitely has some version stuff
> for shared objects.

Ok. I asked because I tried using scons a while back for something, I 
forget what, and the shared objects it generated were broken in some 
exciting and confusing ways. This some years ago. It looks like they 
added soname in 2.3, so maybe it works now.

>
> * Is there a DESTDIR equivalent?
>
> This will require more looking around, it's not obvious. I'm guessing that
> sprung to mind because it's very handy for packaging?

Yeah. It might have something that does something similar, and if it 
doesn't then it's going to be super annoying to package. And if it does, 
given the above discovery that they only figured out how to make a 
library in 2013, it would be worth a look to ensure that installing to a 
non-root directory doesn't try add a crazy rpath or anything like that.

> My thought is that maybe we should come up with something that we know
> is going to be difficult, and that we know is necessary, and see if it's
> possible to pull it off with scons. If it is not...then we give up. What do
> you think is a good candidate?

I like autotools because it (usually) makes things pretty 
straightforward for someone trying to compile the software. There are no 
extra package requirements for the build system, configure/make/make 
install don't require additional documentation, and if you plan to 
create a library that you intend to work outside of Linux then libtool, 
though annoying, is the best bet. But there's another two votes for 
scons, so if it works, go with it. It would be nice if there were a 
readme file explaining how to use it.



More information about the anaconda-patches mailing list