Martin Landa wrote: > > Although, personally I wouldn't bother with the --includes and --libs > > checks. Those flags are already included in the --cflags and --ldflags > > checks. Having separate variables could lead to confusion; e.g. using > > $(PYTHON_INCLUDES) instead of $(PYTHON_CFLAGS) might be sufficient on > > a developer's system but cause problems with a release. > > I renamed PYTHON_CFLAGS to PYTHONCFLAGS, etc. (to follow naming > rules), also removed PYTHON_LIBS since there is PYTHON_FDLAGS. I am > not sure about PYTHONINC (PYTHON_INCLUDES), when compiling C++ code > (vdigit) I should use PYTHONCFLAGS instead of PYTHONINC even if CFLAGS > defines C-related compiler switches?
I would assume so, as there is no separate --cxxflags switch. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-dev
