Hi,
I was not referring to David's information, but on experience of my own.
I was just using this thread to propose an imporvement.
Richard Frith-Macdonald wrote:
I think we just added a little check to see if the 'configure' script had been
changed more recently than the build,
and reconfigure if it has. I think also we (core developers) decided that in
them event of a config change doing
a fresh config was more likely to give good results than re-using old config
settings. That could just be a bad
judgment call?
If you do a first install and type "make" or "make install" then you can
just assume to run ./configure or fail.
However, base/gui/back (I don't remember make itself) have a dependency
on configure itself: if it is changed it is rerun
I think it is a fine idea to reconfigure, but the original options
should be used! That is, not old "config results" (as in existing
config.h) but old config settings as in "parameters and env. variables
passed to configure" are important.
To perform this "./config.status --recheck && ./config.status" needs to
be used: that will run all tests again, but using the old command line
options which really should be preferred. Imagine you first configured
with a certain prefix or with art backend, then you run everything again
and you could end installing in another prefix with the default cairo
backend!
In my experience this is what other packages do if they offer the nicety
of running configure again.
Riccardo
_______________________________________________
Discuss-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnustep
