Hello All: For include paths of the form gdal/cpl_config.h would lead easier to do MAC Framworks where one can create a gdal.framework and use the gdal/ convention.
Take care Garrett On Nov 3, 2011, at 5:24 PM, David Burken wrote: > Mateusz, > > Just wondering if you've thought about namespacing the include paths? That > is: > > #include "cpl_config.h" > #include "gdal_frmts.h" > > Becomes: > #include <gdal/port/cpl_config.h> > #include <gdal/gcore/gdal_frmts.h> > > Or (flattened): > #include <gdal/cpl_config.h> > #include <gdal/gdal_frmts.h> > > This would make installs / uninstalls cleaner. Say your install prefix is: > > /usr/local > > Then your includes go to: > > /usr/local/include/gdal > > Instead of straight to: > /usr/local/include > > I realize this would be a big change. Just thought since you're taking the > plunge on cmake it's something to consider. > > Take care, > Dave > > > > > > > _______________________________________________ > gdal-dev mailing list > gdal-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/gdal-dev _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
