Fairly certain this will be universal.
The tarball contains an issue wherein the proper -I flags are not being passed the c++ compiler relating specifically to the imagemagick, boost and python libraries.
Of note the configure script is filling the variables:
$(PYTHON_CPPFLAGS)
$(BOOST_CPPFLAGS)
$(MAGICKPP_CFLAGS)
With the correct values, they're just never making it to the c++ call
I fixed this by moving the following statements to just before the
"all" target, in the Makefile.in files contained in the project.
CXXFLAGS=$(PYTHON_CPPFLAGS) $(BOOST_CPPFLAGS) $(MAGICKPP_CFLAGS)
CXXCOMPILE = $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES)
$(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS)
LTCXXCOMPILE = $(LIBTOOL) $(AM_V_lt) --tag=CXX $(AM_LIBTOOLFLAGS)
$(LIBTOOLFLAGS) --mode=compile $(CXX) $(DEFS)
$(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS)
$(AM_CXXFLAGS) $(CXXFLAGS)
Fairly certain this will be universal.
The tarball contains an issue wherein the proper -I flags are not being passed the c++ compiler relating specifically to the imagemagick, boost and python libraries.
Of note the configure script is filling the variables:
$(PYTHON_CPPFLAGS)
$(BOOST_CPPFLAGS)
$(MAGICKPP_CFLAGS)
With the correct values, they're just never making it to the c++ call
I fixed this by moving the following statements to just before the
"all" target, in the Makefile.in files contained in the project.
CXXFLAGS=$(PYTHON_CPPFLAGS)$(BOOST_CPPFLAGS) $ (MAGICKPP_CFLAGS)
CXXCOMPILE =$(CXX) $ (DEFS) $(DEFAULT_INCLUDES) $ (INCLUDES)
$(AM_CPPFLAGS) $ (CPPFLAGS) $(AM_CXXFLAGS) $ (CXXFLAGS)$(LIBTOOL) $ (AM_V_lt) --tag=CXX $(AM_LIBTOOLFLAGS)
$(LIBTOOLFLAGS) --mode=compile $ (CXX) $(DEFS)
$(DEFAULT_INCLUDES) $ (INCLUDES) $(AM_CPPFLAGS) $ (CPPFLAGS)
$(AM_CXXFLAGS) $ (CXXFLAGS)
LTCXXCOMPILE =