Hi! Sorry for the delayed reply. I appended to $ac_configure_args and it now works. I did it by adding something like ac_configure_args="$ac_configure_args --with-your-options" somewhere in configure.ac. For those who will be reading this post in the future, just google $ac_configure_args for more examples.
Thanks. On Mon, Mar 3, 2008 at 11:03 AM, Christian Alis <[EMAIL PROTECTED]> wrote: > Hi! > > Thank you for your response. I have also thought about that but felt > it was a kludge. I have browsed the [EMAIL PROTECTED] archives and > found several related topics. Some of the suggestions were even made > by you. :) I should have checked it first before posting here. I'll > try doing some of the suggestions and get back to you if I found > something that worked or found none that did. > > Thanks. > > > > On Mon, Mar 3, 2008 at 2:04 AM, Ralf Wildenhues <[EMAIL PROTECTED]> wrote: > > Hello ianalis, > > > > * ianalis wrote on Sun, Mar 02, 2008 at 02:23:48PM CET: > > > > > > > > > > I placed a copy of each autoconfiscated third-party dependency of my > > > software as a subdirectory. I then followed the instructions for > > > building subpackages in autotools (http://www.gnu.org/software/ > > > automake/manual/html_node/Subpackages.html#Subpackages). However, > > > there is a subpackage that needs to have certain parameters passed to > > > its configure script. The macro AC_CONFIG_SUBDIRS passes the command > > > line parameters to the configure script of each subpackage but I do > > > not want the user to worry about the exact parameters to pass to > > > configure. > > > > > > My question now is how do I set the parameters to pass to configure in > > > my subpackages? > > > > It's not a documented Autoconf interface, but you can append to > > $ac_configure_args. Note that with newer Autoconf, this macro > > will be eval-expanded and use re-quoting for allowing to pass arbitrary > > input. > > > > This question would have been even better on the [EMAIL PROTECTED] > > mailing list. > > > > Cheers, > > Ralf > > >
