------- You are receiving this mail because: -------
You are on the CC list for the bug.
http://bugs.exim.org/show_bug.cgi?id=1198
--- Comment #1 from Philip Hazel <ph10@???> 2012-01-13 16:03:25 ---
On Fri, 13 Jan 2012, Stephen Kelly wrote:
> However, it might make more sense to define them directly in pcre.h? Is there
> any advantage to defining them in the ./configure stuff (I don't know anything
> about that kind of buildsystem. There might be very good reasons).
There is a good reason. Originally the values were indeed in pcre.h, but
now having the values in configure.ac means they are available to that
build system for other uses. For example, to build the release tarballs
I just run the command "make distcheck". It creates files with the
appropriate names. So I don't think we can remove them from
configure.ac. (Note: I'm not a configure expert myself; most of the
original construction of these files was done by others. I just tinker
from time to time. :-)
> Sure, I think at least it should be possible to parse it out of configure.ac.
> If it makes sense to move the variables out of there into a separate file that
> both systems can use, that's fine too. I'm happy to implement either one.
I am not sure how one would import them back into configure.ac, so if
you can implement parsing them out of configure.ac that would be great.
I'll then put a note into configure.ac that the form of those lines
should not be altered, so as not to break your parsing. If it would help
to put a stylized comment around the relevant lines, I'm happy to do
that too.
Philip
--
Configure bugmail:
http://bugs.exim.org/userprefs.cgi?tab=email
