"Gary V. Vaughan" <g...@gnu.org> writes: > Now that I think about it, I'd like to put the multi-gnulib support > directly into my bootstrap script so that it can be called by setting > some configuration variables in bootstrap.conf rather than proliferating > a hook function among all the projects that need this particular > functionality.
I think this makes sense. Multi-gnulib instances should not be a weird configuration that requires modifying scripts. > What project did you have in mind? I'll compare the needs of yours > and GNU M4, and bake in that functionality to the next version of > my bootstrap script. GNU Libidn is one that I released recently and is quite up to date. It has one configure script and two gnulib instances. If you want a smaller project, take a look at Libtasn1 or Libidn2 that also have one configure script and multiple gnulib instances. If you want a project with more than one configure script and multiple gnulib instances, take a look at OATH Toolkit or GNU SASL, they use gnulib a bit different (OATH Toolkit uses separate gnulib-tool --add-import invocations, GNU SASL doesn't). /Simon
