Dear hackers,
> Agreed. I would also like to see Makefile.global installed.
> pg_config.h has C-level configs, and Makefile.global has the
> Makefile-level configs.
There is also "config.status" which is definitely of interest as it
allows to recreate the build tree, and which is not installed by default.
Independently of the actual file list to be included, where
could these makefiles be installed?
- share is for "architecture independent" files. Not really the case.
- include is rather for C files... but Makefile.global and others are
actually included, so it may make sense? If so, should it be directly
in the include/postgresql subdir, or some special subdir, say
"include/postgresql/config"?
- some other directory?
I would tend to put everything in "include/postgresql/config":
- Makefile.global
- a copy of Makefile.port (the actual file, not the link)
- config.status
- possibly other included files (NLS? win32? cygwin?)
Another issue is that Makefile.global seems hardwired to be in
the "src" subdirectory of a postgresql source tree, and to find other
files there:
# Pull in platform-specific magic
include $(top_builddir)/src/Makefile.port
This is an issue for external tools that would like to include
Makefile.global so as to be in the same environment as the server
compilation.
Any idea? The best I have would be to create a "src" subdir in the
installation, so that top_builddir could be set to
".../include/postgresql/config" and everything would work from that
point of view.
--
Fabien COELHO _ http://www.cri.ensmp.fr/~coelho _ [EMAIL PROTECTED]
CRI-ENSMP, 35, rue Saint-Honoré, 77305 Fontainebleau cedex, France
phone: (+33|0) 1 64 69 {voice: 48 52, fax: 47 09, standard: 47 08}
________ All opinions expressed here are mine _________
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
