> This is from an extension module author's point of view. My module will
> reference these two files only:
>
> Makefile.global
> Makefile.shlib
These files possibly include other makefiles.
> I'm not the least interested in how these files are organized internally
Sure.
> If I have a "pg_config --makefiledir" that tells me where to find the
> files, that should be all I need:
>
> makefiledir := $(shell pg_config --makefiledir)
> include $(makefiledir)/Makefile.global
> ...
> Just trying to give you a bit more freedom to place your files :-)
You do not understand how bad it is from the inside;-)
In the current Makefile.global, you find things like:
include $(top_...)/src/Makefile.port
That is the makefile knows where it is expected to reside wrt the source
tree, and use this information. In order to allow what you describe, I
would have to fix this issue, that is rewrite somehow Makefile.global and
other makefiles. Maybe I could do that, but I was trying hard to avoid
it, as there may be some kind of portability issues.
Thanks for you comment,
--
Fabien Coelho - [EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
