Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

forked repo - Appveyor build fails with deprecated SWIG typemaps #1725

Closed
ghost opened this issue Jul 16, 2019 · 3 comments
Closed

forked repo - Appveyor build fails with deprecated SWIG typemaps #1725

ghost opened this issue Jul 16, 2019 · 3 comments

Comments

@ghost
Copy link

ghost commented Jul 16, 2019

Expected behavior and actual behavior.

When building GlenRice-NOAA/gdal on Appveyor (using the root appveyor.yml), both builds fail with the following error:

Error: A deprecated csdestruct typemap was found for {type}, please remove it and replace all csdestruct, csdestruct_derived and csfinalize typemaps by the csdispose, csdispose_derived, csdisposing and csdisposing_derived typemaps.

for the following types:

RasterIOExtraArg
XMLNode
MajorObject
Driver
ColorEntry
GCP
AsyncReader
Dataset
Band
ColorTable
RasterAttributeTable
Transformer
GDALInfoOptions
GDALTranslateOptions
GDALWarpAppOptions
GDALVectorTranslateOptions
GDALDEMProcessingOptions
GDALNearblackOptions
GDALGridOptions
GDALRasterizeOptions
GDALBuildVRTOptions

is additional configuration required to build?

Steps to reproduce the problem.

  1. fork repository
  2. connect Appveyor
  3. start build

Operating system

GDAL version and provenance

master

@rouault
Copy link
Member

rouault commented Jul 16, 2019

is additional configuration required to build?

I don't think so. Doesn't ring a bell. Works well with other forks

@rouault
Copy link
Member

rouault commented Jul 16, 2019

ok, comparing build logs, I found the issue. In your fork which is new SWIG 4.0 is installed by Chocalatey, whereas in existing forks like the OSGeo/gdal one or my own fork, it uses an older cached version (3.0.12). #1727 is an attempt to workaround this

@rouault
Copy link
Member

rouault commented Jul 17, 2019

Fixed by 8676b95

@rouault rouault closed this as completed Jul 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant