Re: [Gtk-osx-users] jhbuild running ./autogen.sh with wrong options

[John Ralls <jralls ceridwen fremont ca us>]

On Mar 9, 2010, at 4:33 AM, Olivier Sessink wrote:

for now I changed the command to ./configure and I run ./autogen.sh
manually. As far as I understand now, jhbuild runs only one command if
no makefile exists (./autogen.sh), but not ./configure ?? How do other
people manage this?

Olivier

2010/3/9 Olivier Sessink <oliviersessink gmail com>:

Hi all,

I'm trying to get jhbuild to build from svn. the svn checkout works.

But then jhbuild tries to run

./autogen.sh --prefix /Users/olivier/gtk/inst --libdir

'/Users/olivier/gtk/inst/lib'  --disable-static

and the ./autogen script doesn't know the options --prefix --libdir

and --disable-static so it returns an error. How can I configure

jhbuild to run ./autogen.sh without options?

The jhbuild manual: http://library.gnome.org/devel/jhbuild/unstable/

I presume that you're asking about your own module for Bluefish. Take a look at the autogen-template argument under moduleset-syntax, autotools. The default template assumes that autogen.sh passes its arguments to configure as its last command, but you can change the template to 

%(srcdir)s/%(autogen-sh)s && %(srcdir)s/%(configure)s --prefix %(prefix)s --libdir %(libdir)s %(autogenargs)s

to have it do what you're asking. 

jhbuild will run autogen regardless of whether there's a makefile. That's important for a VCS module, where an update might require autogening even if there's a Makefile already present.

Regards,

John Ralls