Re: svn configure probs

Hi,

On Sun, Feb 24, 2008 at 7:36 AM, C Leonhardt <rosc2112@yahoo.com> wrote:
>
> Greetings all;
>
> Seems the configure script from svn is forcing a static binary build,
> despite using --enable-shared and --disable-static. I put some "echo"
> lines in the configure script to see what's going on, and despite the
> flags being recognized earlier in the config process, near the end it
> still forces static compile.

`abiword' is always built as a static binary. When --enable-dynamic is
given, additionally `abiword-dynamic' is built for testing purpose
(but not installed). Maybe this will change during the 2.7 development
cycle, if someone works on bringing libabiword up to standards that
are commonly expected from shared lib in the gtk/gnome world
(interface stability, etc.).
See also http://abisource.com/mailinglists/abiword-dev/2008/Jan/0047.html

> Here's the bit of script that seems to be the problem:

[...]

> Also, something is screwy when trying to enable plugins. "configure
> --help" doesn't show --enable-default-plugins as an option; passing
> --enable-default-plugins doesn't enable them (unless I'm mistaken and the
> "default" plugin list is very short); and, there's no errors being shown
> if there are errors when trying to enable the plugins. The only plugin
> shown at the end of configure was opendocument. Seems like all the others
> were skipped, with no indication of any errors, nothing in the config.log
> either. I also tried --enable-plugins (with no other params.)

Look for `--disable-default-plugins'. Opendocument is the only default
plugin at the moment.

> I spoke to "hub" on irc tonight who mentioned there's some option to get
> configure to be more verbose and show the errors but neither of us know
> what it is. If I use --enable-plugins="list of plugins" then I get error
> messages for each of the plugins.
>
> It would make sense if --enable-plugins assumed "all" if the list was
> empty. It should show error messages along the way if something is missing
> while trying to enable a specific plugin, at the very least.

Defaulting to `all' would be an option, but we traditionally have some
plugins with rather exotic dependencies that are not packaged commonly
packaged by distros. This is a departure from previous behaviour,
where all plugins that could be configured were built. Now `configure'
bails on missing dependencies for plugins that were passed to
`--enable-plugins'. You get what you ask for.

See also
http://www.abisource.com/mailinglists/abiword-dev/2008/Jan/0003.html
http://abisource.com/mailinglists/abiword-dev/2008/Jan/0076.html

> Just seems like the configure script from svn needs a little cleaning up.

I am aware that the current behaviour is quite different to what it
used to be -- to the better we like to think. Let us know if we can
add more information to `./configure --help' to make things clearer.
Unfortunately it is already quite verbose after the plugins tree has
been merged.

HTH,
Rob
-----------------------------------------------
To unsubscribe from this list, send a message to
abiword-user-request@abisource.com with the word
unsubscribe in the message body.
Received on Mon Feb 25 10:37:14 2008