Re: Nonstandard dependency installation directories

Am 01. October 2017 um 15:14 Uhr -0500 schrieb Bob Friesenhahn <[email protected]>:
> In the documentation you read, 'X' is not a placeholder variable meant to
> have something else substituted. The 'X' is a trademark for MIT X11, which
> is still the graphical system supported by most Unix/Linux desktops.

*facepalm* I could have known that. It doesn't naturally occur to you
when you're writing a programme for Windows.

> In order to find dependency headers and libraries, you should use the
> CPPFLAGS and LDFLAGS arguments to configure.

I tried and it works. I work with a mostly clean MSYS2/MinGW environment
(only compiler toolchain installed) so that the potential for conflict
with the libraries in the MinGW tree is minimised. I guess that if the
environment wouldn't be that clean and the libraries would show up both
in the MinGW directory tree and my custom tree, the configure script
would detect the ones in the MinGW tree since with CPPFLAGS and LDFLAGS
to my knowledge I can append to the compiler search path, but not
prepend to it. I have seen other projects provide flags like
--with-<dependency>=DIR to explicitely override what configure detects
for (I guess) specifically this conflict situation.

> Please make sure that any paths used do not contain any embedded spaces.
> The Unix-style configure script does not deal with embedded spaces since
> spaces are traditionally used as delimiters.  This is one of the main
> annoyances when building using MinGW and MSYS.

I know this issue and I have wisely avoided pathes with spaces in it.

Thanks for the hints.

Greetings
Marvin

-- 
Blog: https://www.guelkerdev.de
PGP/GPG ID: F1D8799FBCC8BC4F

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot