I'd like to rename configure.in to configure.ac so it's more "correct". Does anyone have any objections to this? Are there any other autoconf/make cleanups that need doing?
On Wed, 27 Oct 2004, Kees Cook wrote:
I'd like to rename configure.in to configure.ac so it's more "correct". Does anyone have any objections to this? Are there any other autoconf/make cleanups that need doing?
It'd be nice to move some of the growing number of build scripts moved to a subdir. Also, are there files in the root dir that we no longer need?
Bryce
On Wed, Oct 27, 2004 at 10:42:08AM -0700, Bryce Harrington wrote:
It'd be nice to move some of the growing number of build scripts moved to a subdir. Also, are there files in the root dir that we no longer need?
I can move the autoconf tools into a separate directory. I think the intltool folks solved all their bugs in that area. I don't know about the rest of the stuff. The biggest set of "extra" files are the .ico, .png, and .nsi files but I'm not sure where those should live.
On Wed, 27 Oct 2004, Kees Cook wrote:
On Wed, Oct 27, 2004 at 10:42:08AM -0700, Bryce Harrington wrote:
It'd be nice to move some of the growing number of build scripts moved to a subdir. Also, are there files in the root dir that we no longer need?
I can move the autoconf tools into a separate directory. I think the intltool folks solved all their bugs in that area. I don't know about the rest of the stuff. The biggest set of "extra" files are the .ico, .png, and .nsi files but I'm not sure where those should live.
The .nsi is part of the windows build stuff I believe (I think it's for the install-shield type installer thingee).
Of the icons, I *believe* that only one of them is actually used, but I'm not certain. In any case I bet they could be moved into a subdir if the references to them were similarly updated. I'm not sure what requires the inkscape.png logo; it might be there only because there was no place better to put it.
Bryce
Bryce Harrington wrote:
The .nsi is part of the windows build stuff I believe (I think it's for the install-shield type installer thingee).
Yes, they can go elsewhere, like /dist or some place that is for distro stuff.
Of the icons, I *believe* that only one of them is actually used, but I'm not certain. In any case I bet they could be moved into a subdir if the references to them were similarly updated.
/src/inkscape.rc points at one of them. If they are moved, please update that file.
btw: Sourceforge allowed me to add the "Snapshots" release. But it isn't allowing me to add files to it. Maybe it is temporary; I'll try again later.
Bob
Kees Cook wrote:
I'd like to rename configure.in to configure.ac so it's more "correct". Does anyone have any objections to this? Are there any other autoconf/make cleanups that need doing?
We need to make certain that autogen.sh still works properly.
But I didn't know that .in was improper. Most projects I have seen, use that instead of .ac .
Bob
On Wed, Oct 27, 2004 at 01:45:12PM -0500, Bob Jamison wrote:
We need to make certain that autogen.sh still works properly.
Absolutely. :)
But I didn't know that .in was improper. Most projects I have seen, use that instead of .ac .
Yeah, that's the old method. Many project haven't changed because it doesn't break anything. It's just cleaner -- and I keep trying to edit 'configure.ac' only to get an empty file. ;)
Here's the quote from section 3.1 of the autoconf manual:
Previous versions of Autoconf promoted the name `configure.in', which is somewhat ambiguous (the tool needed to process this file is not described by its extension), and introduces a slight confusion with `config.h.in' and so on (for which `.in' means "to be processed by configure"). Using `configure.ac' is now preferred.
Kees Cook wrote:
Here's the quote from section 3.1 of the autoconf manual:
Previous versions of Autoconf promoted the name `configure.in', which is somewhat ambiguous (the tool needed to process this file is not described by its extension), and introduces a slight confusion with `config.h.in' and so on (for which `.in' means "to be processed by configure"). Using `configure.ac' is now preferred.
The same rationale for not using .xml for SVG files!
participants (3)
-
Bob Jamison -
Bryce Harrington -
Kees Cook