On Mon, Jul 16, 2018 at 10:44:52AM -0700, Omar Sandoval wrote: > On Mon, Jul 16, 2018 at 04:56:57PM +0200, David Sterba wrote: > > On Thu, Jul 12, 2018 at 04:11:19PM -0700, Omar Sandoval wrote: > > > From: Omar Sandoval <osan...@fb.com> > > > > > > We have a build system internally which only needs to build the > > > libraries out of a repository, not any binaries. I looked at how this > > > works with other projects, and the best example was util-linux, which > > > makes it possible to enable or disable everything individually. This is > > > nice and really flexible, so let's do the same. This way, if you only > > > want to build and install libbtrfsutil, you can simply do > > > > > > ./configure --disable-documentation --disable-all-programs > > > --enable-libbtrfsutil > > > make > > > make install > > > > I think this is an overkill and abusing the --enable-XXX options. You > > want to avoid building the tools by default, so adding an option for > > that is fine. Selectively building only certain tools can utilize that > > option too and just follow with 'make btrfs-image' etc. > > Yeah, it's easy to build stuff selectively, but `make install` will > still try to build everything, that's the part I'm more concerned with.
Oh right, installation. What if it installs just the binaries that are built? The default actions done by configure & make & make install would not change, but there could be configure --disable-all, then selectively make and final make install would be for p in $(progs_install); if test -f $p && $(INSTALL) ...; fi > > The number of --enable-* will stay minimal and we don't even have to > > discuss how to find a good naming scheme (that works for util-linux but > > looks a bit confusing for btrfs-progs). > > Ok, I can collapse these into just --disable-programs/--enable-programs, > and --disable-libraries/--enable-libraries? That would be enough for me. Sounds ok. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
