Re: configure --something= location of GraphicsMagick-config

On 5 Jan 2004, David N. Welton wrote:
>
> > Ideally the top GraphicsMagick/ImageMagick configure script would be
> > enhanced so that TclMagick is subordinate and doesn't even need its
> > own configure script.  Most of what TclMagick needs is already known
> > to GraphicsMagick's configure script so only a Makefile.am would be
> > necessary.  This way there is no doubt what form of Magick is being
> > used, and if it is compatible.
>
> Ok, but if TclMagick is in the extensions/ module... that is going to
> be difficult.

My original idea for TclMagick is that it is distributed with the base
GraphicsMagick as PerlMagick already is.  If TclMagick is kept slim
(e.g. re-use IM/GM's sequence.miff rather than include a copy for
TclMagick) then there should not be a problem with that.  With this
approach TclMagick gets a lot more exposure, and it is much easier to
install.

Even though TclMagick is an 'extensions' module, for GraphicsMagick it
is automatically checked out from CVS.  It is not yet packaged
in the GraphicsMagick tarball.

> That makes sense.  Maybe --with-gm and --with-im, but what I was
> really after is the way to just get it working at all, rather than
> worrying about the two systems.
>
> To do that I need, I suppose, a configure option that points to the
> GraphicsMagic-config script.  Is that what the above does with the
> $withval variable?

While it could be done that way, my example expects that $withval is
either 'yes' or 'no'.  The GraphicsMagic-config script should be in
the user's executable search path if it is to be used.

> > and then you would test to see if with_graphicsmagick is set to 'no'
> > or 'yes' in order to decide which package should be used.
>
> Would a separate, mutually exclusive --with-imagemagick be a bit
> clearer?

Sure that would be fine.  Usually users expect that they can simply
execute 'configure' and that the defaults are likely to build
something.   With this approach they user always needs to provide an
option.

> > Naturally the option should be --without-graphicsmagick for the
> > purposes of this list. :-)
>
> Sure, that's what I'm interested in for now...

Of course the latest TclMagick doesn't compile with GraphicsMagick
yet. :-(

Bob
======================================
Bob Friesenhahn
[email protected]
http://www.simplesystems.org/users/bfriesen



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click