On Tue, Jul 31, 2001 at 10:32:33AM +0200, Emiliano wrote:
> > I didn't look at all thread , but did You make:
> > # mkall /usr/local/midgard ?
> >
> > mkall is just a script which calls configure , make , make install and
> > some testing , doing this that way You point the configure script where
> > You have header midgard files.
>
> mkall no longer uses the value passed to it. Midgard-config must be in your
> path to succesfully build midgard-php4. We could re-introduce the parameter
> to have it add it to the PATH during the run of configure. Depending on
> that is sorta nice, sorta tricky. If there happens to be another midgard-
> config which is in your path, and the parameter supplied with mkall is
> off... OK, so that's a pretty contrived example. Personally I think it's a
> good idea to have config executables in your path, especially if multiple
> modules make use of it. Plus, 'midgard-config --report' hands out useful
> info for developers when debugging.
In glib similar method is used though they have huge macros for detecting
$prefix/bin/glib-config and retrieving values from there. See
/usr/share/aclocal/glib.m4 for details.
--
/ Alexander Bokovoy
$ cat /proc/identity >~/.signature
`Senior software developer and analyst for SaM-Solutions Ltd.`
---
Art is Nature speeded up and God slowed down.
-- Chazal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
