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

[Chris Marsh]

To the right of the search box are 3 dots. Click that and 'view raw logs'

https://pipelines.actions.githubusercontent.com/yqaARdsLodWRtkoqajmNaa64Xp4JCsYwhgHYzJtTCVY8q4LFPT/_apis/pipelines/1/runs/546/signedlogcontent/3?urlExpires=2020-06-17T23%3A07%3A33.8599856Z&urlSigningMethod=HMACV1&urlSignature=lHpnB3bSeUyel1HOzHFRgrY3dg3RHkf4IQrqL%2BPKtu8%3D



On Wed, Jun 17, 2020 at 5:02 PM Ryan Schmidt <gdal at ryandesign.com> wrote:

> CAUTION: This email originated from outside of the University of
> Saskatchewan. Do not click links or open attachments unless you recognize
> the sender and know the content is safe. If in doubt, please forward
> suspicious emails to phishing at usask.ca
>
>
> 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 ?
>
> https://pypi.org/project/GDAL/
>
>
> > 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.
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev
>

Chris Marsh, PhD
University of Saskatchewan
chrismarsh.ca
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20200617/edc36f9b/attachment.html>