[gdal-dev] How to build py-gdal using the C++ compiler

Ryan Schmidt gdal at ryandesign.com
Wed Jun 17 15:37:23 PDT 2020

On Jun 17, 2020, at 08:38, Even Rouault wrote:

> On mardi 16 juin 2020 20:41:28 CEST Ryan Schmidt wrote:
> > Hello, I'm a developer with MacPorts. We have this problem: py-gdal is
> > written in C++ but it gets compiled using the C compiler and CFLAGS and
> > linked using the C++ compiler and LDFLAGS. We would like it to be compiled
> > using the C++ compiler and CXXFLAGS. How can this be accomplished? We have
> > a need to supply the build with certain flags in CXXFLAGS but they are
> > currently being ignored, resulting in build failures like this:
> > 
> > https://trac.macports.org/ticket/57621
> > 
> > I know that distutils simply has the defect that it does not support C++
> > software at all, resulting in the above condition. This bug was never fixed
> > before distutils was retired.
> > 
> > https://bugs.python.org/issue1222585
> > 
> > I am trying to figure out whether distutils' replacement setuptools is still
> > suffering from the same problem and needs to be fixed or whether there is
> > something that needs to be changed in py-gdal and other similar projects to
> > make it work. Do you know?
> What is py-gdal exactly ? A build of the "official" GDAL SWIG Python bindings ? 


> Python extension building is always a bit of black magick to me, but our continuous integration does include building them on the Mac. For example, 
> https://github.com/OSGeo/gdal/runs/779871427 . I guess this must be through setuptools

The HTML5ness of that CI result interface is making it impossible for me to determine whether it is building the python extension and if so to determine whether it has the same problem I'm seeing. The find function on that page isn't working right for me, and I can't see any way to download or copy the entire build log so that I can examine it in my editor.

More information about the gdal-dev mailing list