At least this happens on OSX. This causes the dreaded 'MAXPROJ Undefined' error. Fixed.
Added to the README:
If you get the error 'MAXPROJ Undefined' while building the hdfeos
code, then look at your shell environment for paths on CPPFLAGS, etc.,
and check for developer installs of the 'proj' library on any paths
they name.
The hdfeos build contains an include named 'proj.h' that defines
a symbol 'MAXPROJ'. However, you might have an installed version of
the 'proj' library using (Homebrew on OSX?) and that also has a
header named, yes, 'proj.h' which does not define MAXPROJ. If you
have the include path set using CPPFLAGS=-I/opt/homebrew/include,
for example, then the build may fail with the MAXPROJ Undefined
message because that path will get precedence over the paths in
hdfeos Makefile.
At least this happens on OSX. This causes the dreaded 'MAXPROJ Undefined' error. Fixed.
Added to the README:
If you get the error 'MAXPROJ Undefined' while building the hdfeos
code, then look at your shell environment for paths on CPPFLAGS, etc.,
and check for developer installs of the 'proj' library on any paths
they name.
The hdfeos build contains an include named 'proj.h' that defines
a symbol 'MAXPROJ'. However, you might have an installed version of
the 'proj' library using (Homebrew on OSX?) and that also has a
header named, yes, 'proj.h' which does not define MAXPROJ. If you
have the include path set using CPPFLAGS=-I/opt/homebrew/include,
for example, then the build may fail with the MAXPROJ Undefined
message because that path will get precedence over the paths in
hdfeos Makefile.