Skip to content
This repository has been archived by the owner on Oct 1, 2020. It is now read-only.

Only setting PG_CONFIG if it hasn't already been set. #16

Closed
wants to merge 1 commit into from

Conversation

tonyarkles
Copy link

My machine has two different copies of libpg installed on it. Specifying PG_CONFIG
should encourage the build to use the value of that for calling pg_config.

My machine has two different copies of libpg installed on it. Specifying PG_CONFIG
should encourage the build to use the value of that for calling pg_config.
@markokr
Copy link
Collaborator

markokr commented Nov 1, 2012

Variables from environment or command line already override variables in Makefile.

?= is only useful for checking if variable is defined earlier in same makefile.

So this patch is unnecessary.

Or does it actually change anything?

@tonyarkles
Copy link
Author

Hmmmm. That's really interesting. I'm going to have to have a look at it again. From what I remember, it wouldn't accept a different PG_CONFIG without that change (it would just use the system default).

@markokr
Copy link
Collaborator

markokr commented Dec 28, 2012

Seems unnecessary. Closed.

@markokr markokr closed this Dec 28, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants