* [vcpkg_configure_make] fix case sensitive comparison in PATH system dir search
* Fixes after code review
---------
Co-authored-by: Victor NIVET <vnivet@invoke.fr>
* [libmysql] Update to 8.0.34
* [libmysql] Fix deps
* [libmysql] Fix deps, cont.
* WIP
* WIP
* [libmysql] Don't wrap downstream Find modules
Downstream Find modules are not standardized and cannot be wrapped
reliably. By moving the legacy wrapper behaviour to a config module,
we can catch those users which were relying on the old usage, and
display the instructions for migrating to the canonical unofficial
usage.
* [libmysql] Cross build stuff
* [libmysql] Cross build stuff
* [libmysql] Cross build stuff
Results from build: https://dev.azure.com/vcpkg/public/_build/results?buildId=95281
PASSING, REMOVE FROM FAIL LIST: qcoro:x64-osx (/Users/vagrant/Data/work/2/s/scripts/azure-pipelines/../ci.baseline.txt).
Caused by https://github.com/microsoft/vcpkg/pull/33273
The comment says that it's an ICE but it passed in CI; this might be a form of intermittent compiler crash. If we get a failure next time we should change this to skip instead.
From https://dev.azure.com/vcpkg/public/_build/results?buildId=94820
REGRESSION: caffe2:arm64-windows is marked as fail but one dependency is not supported for arm64-windows.
REGRESSION: gtk:x64-windows-static is marked as fail but one dependency is not supported for x64-windows-static.
Fixed by https://github.com/microsoft/vcpkg/pull/33999
REGRESSION: omplapp:arm-neon-android failed with BUILD_FAILED. If expected, add omplapp:arm-neon-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
Previously blocked by:
PASSING, REMOVE FROM FAIL LIST: assimp:arm-neon-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: clblast:arm-neon-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: clblast:arm64-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: clblast:x64-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: openvdb:x64-windows-static (C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: openvdb:x64-windows-static-md (C:\a\2\s\scripts\azure-pipelines/../ci.baseline.txt).
* Add libcoro 0.7
* Update CI baseline
* Add "supports": "!windows"
* Update CI baseline
* Remove unneeded vcpkg-cmake-config dependency
* Update CI baseline
* Disable x64-linux and x64-osx in ci.baseline.txt
* Apply code review suggestions
* Update CI baseline
* Add patch to disable git config
* Update CI baseline
* Fix patch
* Update CI baseline
* Allow shared library builds
* Update CI baseline
* Update libcoro to version 0.8
* Update CI baseline
* Update CI baseline
* Fix line endings
* Update CI baseline
* Fix hash
* Update CI baseline
* Update version database
* Force rerun of CI pipeline
* Update to libcoro 0.9
* Update CI baseline
* Replace manual dependency check with manifest-based one
* Remove v0.8 version
* Update CI baseline
---------
Co-authored-by: chausner <chausner@users.noreply.github.com>
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
* [duktape] Update to 2.7.0 and don't require python2 to build.
Instead use a release tarball which includes all codegened stuff.
* [duktape] Enable in CI.
Don't enforce a hardcoded nesting limit as these limits are enforced by
GitLab itself and may change in the future. Furthermore I believe that
users can be trusted to successfully copy'n'paste the path portion of an
URL. Therefore we just require that the assumptions of our
implementation hold, i.e. that we can convert the repo path to a CMake
list by replacing `/` with `;` and that there is a repository name.
The current error message matching attempt is too strict as the error
message occasionally spells out the extension (i.e. `mt.exe` instead of
`mt`).
Co-authored-by: Monica <liuyumei01@beyondsoft.com>
* Support cross-compiling Objective C code using Meson
The glib port uses Objective C code and the Meson build system.
You'll end up cross compiling glib when compiling for x64 osx
on an arm64 osx machine, or vice versa.
For this to work, an Objective C compiler needs to be set
in the Meson cross file.
vcpkg generates this file based on the
`scripts/buildsystems/meson/meson.template.in` template, and expects
the `MESON_OBJC` CMake variable to be set.
That's the job of `z_vcpkg_meson_set_proglist_variables` in
`scripts/cmake/vcpkg_configure_meson.cmake`. It will only generate data
for an Objective C compiler if:
- The `Languages` argument includes `OBJC`
- CMake has detected a Objective C compiler, and has set `VCPKG_DETECTED_CMAKE_OBJC_COMPILER`
To make this work, this patch:
- Enables the OBJC and OBJCXX language on Apple platforms
- Updates the call to `vcpkg_configure_meson` in the glib port file
to include the OBJC OBJCXX languages.
Fixes https://github.com/microsoft/vcpkg/issues/26147
Fixes https://github.com/microsoft/vcpkg/issues/20341
Based on https://github.com/microsoft/vcpkg/pull/26259
Based on 27dee354e4
Tested on an arm64 mac to compile glib for x64 macos
* Update version database
* [python3] Update to 3.11.3
* Force set PythonForBuild on windows
* Set LD_LIBRARY_PATH on unix
* Always use vcpkg_find_acquire_program(PYTHON3) on windows
* Remove LD_LIBRARY_PATH shenanigans
* [vtk] Parse python version from include folder
* Fix static builds on windows
* Pass --with-build-python on unix
* [omniorb] Fix python version in patch
* Resurrect rpath patch
* [python3] fix usage
* [gobject-introspection] don't hardcode python version
* Update vcpkg_find_aquire_program(PYTHON3)
This is also required for gobject-introspection
* [paraview] don't hardcode python version
* [vtk-dicom] don't hardcode python version
* Update python in vcpkgTools.xml
* Fix host arch detection in vcpkg_find_acquire_program(PYTHON3)
* [libpq] Don't hardcode python version
* [shiva] Don't pass python variables
* [vcpkg-get-python-packages] Delete unused file, update hardcoded python version
* [python3] update to 3.11.4
* [omniorb] Use PREPEND in vcpkg_add_to_path
So that python from vcpkg is picked before system python
* libpq quickfix
* re-fix libpq
* fix vcpkg-get-python-packages
* Make windows 7 patch compatible with unix builds
* Copy pyd files to bin
Also fixes copying files that do not belong to current build tree
* Fix static builds
* Speculatively fix osx regression
* Fix omniorb on unix
* [gobject-introspection] fix windows builds
* [vtk] Update vendored copy of mpi4py for python 3.11 support
* [mdl-sdk] Fix python
* [gobject-introspection] fix the fix of a fix...
* Update versions
* Undo changes in gobject-introspection and vcpkg_find_aquire_program(PYTHON3)
---------
Co-authored-by: root <root@DESKTOP-UIPL9V8>
* [salome-configuration|medcoupling] new ports
* format manifest
* v db
* remove trace
* v db
* fix dep
* v db
* Apply suggestions from code review
Co-authored-by: jim wang <122244446+jimwang118@users.noreply.github.com>
* v db
* adjust SALOME_WITH_MPI depending on HDF5
* remove nuking of CMAKE_PREFIX_PATH from salome
* v db
* fix post build
* v db
* Fix med-fichier config on linux
* add supports
* format manifest
* v db
* don't want to investigate linux failure further
---------
Co-authored-by: jim wang <122244446+jimwang118@users.noreply.github.com>
* [libphonenumber] Bump to 8.13.17 & fix linux and macOS build
* update version database
* fix windows icui18n lib name
* update version database
* fix patches
* update version database
* fix ci.baseline.txt
* update cmake
* update to rc2
* use nightly build
* update to rc3 drop freebsd due to dead link and update git while i am at it
* fix missing sha
* fix relative path
* update to 3.27 release
* [paho-mqtt] remove usage of OPENSSL_ROOT_DIR
* [directxtex] control optional directx-headers dep
* v db
* IN LIST -> IN_LIST
* v db
* try fixing azure-storage-cpp
* v db
* update to 3.27.1
* scripts/msys => scripts/cmake
The "msys" directory looked like a "maintainer help" directory (like scripts/boost is) so it wasn't included in standalone distributions of vcpkg.
It seems like the correct fix for this is just to move it into the scripts/cmake directory.
Only take the COMPONENT part for the runtime settings like we
already do for the DESTINATION component. The install local dependencies
should only need to be run for RUNTIME components anyway.
