Import CCHOME from the environment when building with GCC on Windows
authorSteve Hay <steve.m.hay@googlemail.com>
Mon, 25 Jun 2012 17:03:18 +0000 (18:03 +0100)
committerSteve Hay <steve.m.hay@googlemail.com>
Mon, 25 Jun 2012 17:03:54 +0000 (18:03 +0100)
commit256aa5e6f36285b09b3ba67ad9926c9d4f9ea7bc
tree701c3706d3dab49475dcf5e27fc137fc74f98ac2
parent9df8bd1db54cceb60e2db0a139ff7db66d12a3de
Import CCHOME from the environment when building with GCC on Windows

Using the environment for such things is preferable to always having to
specify a CCHOME= command-line argument, and is akin to setting various
environment variables via vcvars32.bat for VC++ builds.

Also remove a blank line to make it more obvious that copying DLLs to the
t/ folder is part of the test-prep target. (This is one thing which
doesn't work if CCHOME has not been set and MinGW isn't installed in its
default location.)
win32/makefile.mk