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

[gdal] linux build does not get dependencies from vcpkg #8943

Closed
pwm1234 opened this issue Nov 7, 2019 · 5 comments
Closed

[gdal] linux build does not get dependencies from vcpkg #8943

pwm1234 opened this issue Nov 7, 2019 · 5 comments
Assignees
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist

Comments

@pwm1234
Copy link

pwm1234 commented Nov 7, 2019

Is your feature request related to a problem? Please describe.
The linux vcpkg build of gdal does not get its dependencies from vcpkg. The configure command needs to refer to the vcpkg install path so it finds its dependencies there. For example, xerces-c or tiff. They are found in /usr not in the vcpkg install path.

I am not sure how to change to portfile, but here is how I built gdal using the vcpkg install directory as $vcpkg

LDFLAGS=-L$vcpkg/lib \
    CFLAGS=-I$vcpkg/include \
    ./configure \
        --prefix=$pkg \
        --disable-shared \
        --enable-static \
        --with-pic \
        --with-curl=$vcpkg \
        --with-expat=$vcpkg \
        --with-geos=yes \
        --with-geotiff=$vcpkg \
        --with-hdf5=$vcpkg \
        --with-libkml=$vcpkg \
        --with-liblzma=yes \
        --with-libtiff=$vcpkg\
        --with-libz=$vcpkg\
        --with-openjpeg=$vcpkg \
        --with-png=$vcpkg \
        --with-proj=$vcpkg \
        --with-proj=$vcpkg \
        --with-spatialite=$vcpkg \
        --with-sqlite3=$vcpkg \
        --with-webp=$vcpkg \
        --with-xerces=$vcpkg \
        --with-xml2=$vcpkg 

(I am not sure if the gdal build is using the vcpkg geos -- there is some strange behavior regarding the [missing] geos config file.)

@pwm1234 pwm1234 added the category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist label Nov 7, 2019
@JackBoosY JackBoosY self-assigned this Nov 8, 2019
@jumpinjackie
Copy link
Contributor

I believe #6752 is somewhat blocking this effort in that making vcpkg symlink debug/include is better than an invasive patch for gdal's ./configure script and m4 macros to distinguish between the various vcpkg paths.

Not familiar with the vcpkg source though to try adding support for this.

@lakinwecker
Copy link
Contributor

I am also currently running into this issue. If I have netcdf/gdal installed from the arch repositories, then gdal will attempt to compile and link against them, and then I run into compatibility issues because arch linux includes newer versions.

@pwm1234
Copy link
Author

pwm1234 commented Nov 21, 2019

Yes, these problems with gdal have made me give up using vcpkg with linux. I have found vcpkg works great on windows, but on linux where it is rather difficult to exclude pre-installed packages in /usr, I am encountering inconsistencies with packages that sometimes get dependencies from vcpkg and sometimes from what has been apt-get installed.

@dg0yt
Copy link
Contributor

dg0yt commented Jul 23, 2021

This issue should be fixed now.

@JackBoosY
Copy link
Contributor

Please reopen this issue if it still exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-feature The issue is with a library, which is requesting new capabilities that didn’t exist
Projects
None yet
Development

No branches or pull requests

5 participants