opencv even has
`message(WARNING "The python module is currently unsupported on Windows
when building static OpenCV libraries")`
In general static python builds don't support extensions on windows as
such a pyd build against a static python can never be used.
What would work -> static extensions linked into a final executable.
There is no proper way to deactivate extensions if python was statically
build on windows.
Two questions remain here:
Should python be build dynamically on windows for static triplets so
that we get a broader CI test? (maybe add a forbidden feature for only
windows&static which allows building the static python instead)
#35084 introduced a regression for native ARM Linux builds where the
toolchain would mistakenly try to reference a cross-compiler (e.g.
`aarch64-linux-gnu-gcc`) despite building natively because vcpkg spells
the architecture differently from what the system reports (`arm64` vs.
`aarch64`).
This fixes the issue by checking whether the
`CMAKE_HOST_SYSTEM_PROCESSOR` matches the target (in CMake's spelling of
the architecture).
---------
Co-authored-by: Kai Pastor <dg0yt@darc.de>
<!-- If your PR fixes issues, please note that here by adding "Fixes
#NNNNNN." for each fixed issue on separate lines. -->
<!-- If you are still working on the PR, open it as a Draft:
https://github.blog/2019-02-14-introducing-draft-pull-requests/. -->
- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- ~~[ ] SHA512s are updated for each updated download.~~
- ~~[ ] The "supports" clause reflects platforms that may be fixed by
this new version.~~
- ~~[ ] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.~~
- ~~[ ] Any patches that are no longer applied are deleted from the
port's directory.~~
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
Also:
- fixes Android compilation which wasn't tested the last time this port
was modified
- Exclude `uwp` which was indirectly excluded by another optional
dependency
---------
Co-authored-by: Kai Pastor <dg0yt@darc.de>
Fixes#37974
png, jpeg and tiff support are [optional in
gdk-pixbuf](0edaedc560/meson_options.txt (L5)),
however [vcpkg has them
hard-wired](c5da4bafbd/ports/gdk-pixbuf/portfile.cmake (L37)).
Turn `png`,` jpeg` and `tiff` into features, and enable those 3 by
default to preserve compatibility.
- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] ~~SHA512s are updated for each updated download.~~
- [ ] ~~The "supports" clause reflects platforms that may be fixed by
this new version.~~
- [ ] ~~Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.~~
- [ ] ~~Any patches that are no longer applied are deleted from the
port's directory.~~
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
---------
Co-authored-by: Jon <v-zhli17@microsoft.com>
Fixes#32691: unneeded warnings.
Fixes#36928: windows dynamic linkage for icu et al.
These DLLs are possible now (subject to features):
~~~
skia:x64-windows:/bin/dawn_native.dll
skia:x64-windows:/bin/dawn_platform.dll
skia:x64-windows:/bin/dawn_proc.dll
skia:x64-windows:/bin/skia.dll
skia:x64-windows:/bin/skshaper.dll
skia:x64-windows:/bin/skunicode.dll
~~~
The custom CMakeLists.txt in the port installs headers under `rply/` and
expects `#include <rply/rply.h>` correspondingly as the include.
However, the code samples in the RPly project use a plain `#include
"rply.h"` instead: https://w3.impa.br/~diego/software/rply/
This PR adds `include/rply/` to the `target_include_directories()` to
support both conventions.
The project exports only two distinctly-named headers (`rply.h` and
`rplyfile.h`) so the non-prefixed includes causing a collision somewhere
is unlikely.
Also added license info to vcpkg.json and a usage file.
This contains high priority active security things to adopt trusted
launch, and managed identity rather than SAS tokens when minting the
images, and 1ES Hosted Pools.
Some instructions are rough around the edges because I'm not sure
everything is repeatable yet while this is all in flux...
Previously the REQUIRED flag made CMake fail with an error if
`powershell` wasn't found on line 193. This prevented the `else` block
on lines 197-198 from ever running.
While authoring vcpkg_from_git to authenticated servers documentation,
@JavierMatosD and I discovered some failure modes that are not clear in
the output.
Example with REF set to a branch name:
```console
The port under test is:
vcpkg_from_git(
OUT_SOURCE_PATH out
URL https://github.com/microsoft/vcpkg
REF 2024.01.12
)
========== BEFORE ===============
Computing installation plan...
The following packages will be built and installed:
test-port:x64-windows@1 -- D:\test\test-port
Detecting compiler hash for triplet x64-windows...
Installing 1/1 test-port:x64-windows@1...
Building test-port:x64-windows@1...
-- Installing port from location: D:\test\test-port
-- Fetching https://github.com/microsoft/vcpkg 2024.01.12...
CMake Error at scripts/cmake/vcpkg_from_git.cmake:141 (message):
unable to rev-parse 2024.01.12 after fetching git repository
Call Stack (most recent call first):
D:/test/test-port/portfile.cmake:1 (vcpkg_from_git)
scripts/ports.cmake:170 (include)
error: building test-port:x64-windows failed with: BUILD_FAILED
Elapsed time to handle test-port:x64-windows: 1.8 s
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+test-port
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[test-port]+Build+error+on+x64-windows&body=Copy+issue+body+from+D%3A%2Fvcpkg2%2Finstalled%2Fvcpkg%2Fissue_body.md
========== AFTER ================
Computing installation plan...
The following packages will be built and installed:
test-port:x64-windows@1 -- D:\test\test-port
Detecting compiler hash for triplet x64-windows...
Installing 1/1 test-port:x64-windows@1...
Building test-port:x64-windows@1...
-- Installing port from location: D:\test\test-port
-- Fetching https://github.com/microsoft/vcpkg 2024.01.12...
CMake Error at scripts/cmake/vcpkg_from_git.cmake:142 (message):
After fetching 2024.01.12, the target ref 2024.01.12 appears inaccessible.
A common cause of this failure is setting REF to a named branch or tag
rather than a commit SHA. REF must be a commit SHA. If the git server
does not advertise commit SHAs (uploadpack.allowReachableSHA1InWant is
false), you can set FETCH_REF to a named branch in which the desired commit
SHA is in the history. For example, you may be able to fix this error by
changing "REF 2024.01.12" to "REF a-commit-sha FETCH_REF 2024.01.12". (git
rev-parse 2024.01.12 failed)
Call Stack (most recent call first):
D:/test/test-port/portfile.cmake:1 (vcpkg_from_git)
scripts/ports.cmake:170 (include)
error: building test-port:x64-windows failed with: BUILD_FAILED
Elapsed time to handle test-port:x64-windows: 1.9 s
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+test-port
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[test-port]+Build+error+on+x64-windows&body=Copy+issue+body+from+D%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
```
Example with REF ste to a branch name with FETCH_REF set:
```console
PS D:\test> run-test
The following packages are not installed:
test-port:x64-windows
The following packages are not installed:
test-port:x64-windows
The port under test is:
vcpkg_from_git(
OUT_SOURCE_PATH out
URL https://github.com/microsoft/vcpkg
REF 2024.01.12
FETCH_REF master
)
========== BEFORE ===============
Computing installation plan...
The following packages will be built and installed:
test-port:x64-windows@1 -- D:\test\test-port
Detecting compiler hash for triplet x64-windows...
Installing 1/1 test-port:x64-windows@1...
Building test-port:x64-windows@1...
-- Installing port from location: D:\test\test-port
-- Fetching https://github.com/microsoft/vcpkg master...
CMake Error at scripts/cmake/vcpkg_from_git.cmake:141 (message):
unable to rev-parse 2024.01.12 after fetching git repository
Call Stack (most recent call first):
D:/test/test-port/portfile.cmake:1 (vcpkg_from_git)
scripts/ports.cmake:170 (include)
error: building test-port:x64-windows failed with: BUILD_FAILED
Elapsed time to handle test-port:x64-windows: 1.6 s
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+test-port
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[test-port]+Build+error+on+x64-windows&body=Copy+issue+body+from+D%3A%2Fvcpkg2%2Finstalled%2Fvcpkg%2Fissue_body.md
========== AFTER ================
Computing installation plan...
The following packages will be built and installed:
test-port:x64-windows@1 -- D:\test\test-port
Detecting compiler hash for triplet x64-windows...
Installing 1/1 test-port:x64-windows@1...
Building test-port:x64-windows@1...
-- Installing port from location: D:\test\test-port
-- Fetching https://github.com/microsoft/vcpkg master...
CMake Error at scripts/cmake/vcpkg_from_git.cmake:138 (message):
After fetching master, the target ref 2024.01.12 appears inaccessible. A
common cause of this failure is setting REF to a named branch or tag rather
than a commit SHA. REF must be a commit SHA. (git rev-parse 2024.01.12
failed)
Call Stack (most recent call first):
D:/test/test-port/portfile.cmake:1 (vcpkg_from_git)
scripts/ports.cmake:170 (include)
error: building test-port:x64-windows failed with: BUILD_FAILED
Elapsed time to handle test-port:x64-windows: 1.5 s
Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+test-port
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[test-port]+Build+error+on+x64-windows&body=Copy+issue+body+from+D%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
```
---------
Co-authored-by: Thomas1664 <46387399+Thomas1664@users.noreply.github.com>
Cherry-picked from #35437:
Add a test port which covers non-default features of `gdal`.
Fix duplicate symbol definition in poppler and paraview found by the
test-port.
(https://github.com/microsoft/vcpkg/pull/35437#issuecomment-1837431578.
paraview using vtk using gdal using poppler.)
Disallow cascaded failure of gdal.
---------
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
CBL-Mariner ( https://github.com/micro…soft/azurelinux )
This resolves a Service360 alert caused by Ubuntu refusing to make a
security patch publicly available for Ubuntu 22.04 LTS, see
https://ubuntu.com/security/notices/USN-6472-1 .
It seems likely that we will need to reconsider Ubuntu being our
'default' test environment following this type of behavior, since it's
likely vcpkg customers will be similarly affected.
<!-- If your PR fixes issues, please note that here by adding "Fixes
#NNNNNN." for each fixed issue on separate lines. -->
<!-- If you are still working on the PR, open it as a Draft:
https://github.blog/2019-02-14-introducing-draft-pull-requests/. -->
If this PR updates an existing port, please uncomment and fill out this
checklist:
- [ x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ x] SHA512s are updated for each updated download.
- [ x] The "supports" clause reflects platforms that may be fixed by
this new version.
- [ x] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [ x] Any patches that are no longer applied are deleted from the
port's directory.
- [ x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [ x] Only one version is added to each modified port's versions file.
---------
Co-authored-by: WangWeiLin-MV <156736127+WangWeiLin-MV@users.noreply.github.com>
Pass `share/pkgconfig` instead of `debug/share/pkgconfig`: The `share`
location is for config-independent data.
Integrate `CURRENT_PACKAGES_DIR` locations.
Change the function interface to take a CONFIG parameter instead of
prefix list (suggested below).
Use `z_vcpkg_setup_pkgconfig_path` also for `vcpkg_fixup_pkgconfig`
(which already had proper handling of `CURRENT_PACKAGES_DIR` and
`share`).
Remove redundant trailing slash.
Extend unit test.
Fixes consuming `wayland-protocols` and similar.
Passing on
https://dev.azure.com/vcpkg/public/_build/results?buildId=99959&view=results.
Added `openblas` to ci.baseline.txt by
https://github.com/microsoft/vcpkg/pull/29406, which has been fixed by
https://github.com/microsoft/vcpkg/pull/36072:
```
PASSING, REMOVE FROM FAIL LIST: openblas:arm-neon-android
PASSING, REMOVE FROM FAIL LIST: openblas:arm64-android
```
Add the following ports to the ci.baseline.txt because they are
direct/indirect downstream of `openblas`:
```
REGRESSION: blas:arm-neon-android failed with BUILD_FAILED. If expected, add blas:arm-neon-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: lapack-reference:arm64-android failed with BUILD_FAILED. If expected, add lapack-reference:arm64-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: clapack:arm64-android failed with BUILD_FAILED. If expected, add clapack:arm64-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: shogun:arm64-android failed with BUILD_FAILED. If expected, add shogun:arm64-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
```
- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] ~SHA512s are updated for each updated download.~
- [x] The "supports" clause reflects platforms that may be fixed by this
new version.
- [ ] ~Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.~
- [ ] ~Any patches that are no longer applied are deleted from the
port's directory.~
- [x] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [x] Only one version is added to each modified port's versions file.
---------
Co-authored-by: Monica <v-liumonica@microsoft.com>
Reason:
```
-- Adjusting original rpath of: '/mnt/e/all/vcpkg/installed/x64-linux-release/lib/pkgconfig/../../lib/intel64/'
-- Fixed rpath in: '/mnt/e/all/vcpkg/packages/numpy_x64-linux-release/lib/python3.11/site-packages/numpy/linalg/lapack_lite.cpython-311-x86_64-linux-gnu.so' ('$ORIGIN:$ORIGIN/../../../../:$ORIGIN/../../../../intel64/')
```
needed `$ORIGIN/../../../../intel64/` in there which came from a pc file
via `-Wl,-rpath='${libdir}'`
---------
Co-authored-by: Osyotr <Osyotr@users.noreply.github.com>
<!-- If your PR fixes issues, please note that here by adding "Fixes
#NNNNNN." for each fixed issue on separate lines. -->
```
PASSING, REMOVE FROM FAIL LIST: fdk-aac:arm-neon-android
PASSING, REMOVE FROM FAIL LIST: fdk-aac:x64-android
PASSING, REMOVE FROM FAIL LIST: fdk-aac:arm64-android
```
Passing on
https://dev.azure.com/vcpkg/public/_build/results?buildId=99817&view=results.
Fixed by PR https://github.com/microsoft/vcpkg/pull/36891.
<!-- If you are still working on the PR, open it as a Draft:
https://github.blog/2019-02-14-introducing-draft-pull-requests/. -->
- [x] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] ~~SHA512s are updated for each updated download.~~
- [ ] ~~The "supports" clause reflects platforms that may be fixed by
this new version.~~
- [x] Any fixed [CI
baseline](https://github.com/microsoft/vcpkg/blob/master/scripts/ci.baseline.txt)
entries are removed from that file.
- [ ] ~~Any patches that are no longer applied are deleted from the
port's directory.~~
- [ ] ~~The version database is fixed by rerunning `./vcpkg
x-add-version --all` and committing the result.~~
- [ ] ~~Only one version is added to each modified port's versions
file.~~
<!-- If this PR adds a new port, please uncomment and fill out this
checklist:
- [ ] Changes comply with the [maintainer
guide](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/contributing/maintainer-guide.md).
- [ ] The name of the port matches an existing name for this component
on https://repology.org/ if possible, and/or is strongly associated with
that component on search engines.
- [ ] Optional dependencies are resolved in exactly one way. For
example, if the component is built with CMake, all `find_package` calls
are REQUIRED, are satisfied by `vcpkg.json`'s declared dependencies, or
disabled with
[CMAKE_DISABLE_FIND_PACKAGE_Xxx](https://cmake.org/cmake/help/latest/variable/CMAKE_DISABLE_FIND_PACKAGE_PackageName.html).
- [ ] The versioning scheme in `vcpkg.json` matches what upstream says.
- [ ] The license declaration in `vcpkg.json` matches what upstream
says.
- [ ] The installed as the "copyright" file matches what upstream says.
- [ ] The source code of the component installed comes from an
authoritative source.
- [ ] The generated "usage text" is accurate. See
[adding-usage](https://github.com/microsoft/vcpkg-docs/blob/main/vcpkg/examples/adding-usage.md)
for context.
- [ ] The version database is fixed by rerunning `./vcpkg x-add-version
--all` and committing the result.
- [ ] Only one version is in the new port's versions file.
- [ ] Only one version is added to each modified port's versions file.
END OF NEW PORT CHECKLIST (delete this line) -->
Co-authored-by: Lily Wang <v-lilywang@microsoft.com>
Based on https://github.com/microsoft/vcpkg/pull/36518, credits @abique.
This update makes skia use vcpkg vulkan. There are still vendored
dependencies (abseil, spirv-*, maybe also dawn, graphite), but I don't
want to touch that now.
---------
Co-authored-by: Alexandre Bique <bique.alexandre@gmail.com>
* Add robotraconteur port
* version database
* Add robotraconteur-companion port
* version database
* Install usage
* Update manifests
* Add dbus and libusb dependencies on linux
* version database
* Add back vcpkg-cmake dependency
* version database
* Disable robotraconteur on linux
* version database
* usage newline
* Use vcpkg_cmake_config_fixup
* Add back linux support
* version database
* Improve check for libbluetooth using pkgconfig
* version database
* Change libbluetooth check to warning
* version database
* Set PACKAGE_NAME in vcpkg_cmake_config_fixup
* version database
* Limit CI
* Update msys2
* Declare msys packages for pkgconfig and fortran...
... with explicit DEPS and PROVIDES, instead of using DIRECT_PACKAGES.
This change makes it possible to notice changed dependencies
in `vcpkg-ci-msys2` update checks. (Current case: zstd.)
It also enables reuse of general declarations from `vcpkg_acquire_msys`
in specialized cases (`vpckg_find_fortran`).
Last not least, using the the Z_DECLARE_EXTRA_PACKAGES_COMMAND
simplifies the implementation of `vcpkg-ci-msys2`, in particular for
checks across platform boundaries.
* Revert "Limit CI"
* [libtorch] update to 2.1.2
* adjust features and deps
* remove dep
* fix onnx case
* use system fxdiv
* update xnnpack
* fxdiv fix in libtorch
* add newline
* xnnpack does not install configs
* more patching
* fix patch
* more fixes
* use full lib for sleef.
* fix glog symbol on osx
* try fixing msvc ice
* ok renaming did nothing
* v db
* remove comments
* v db
* cuda is only for x64
* v db
* fix usage since cuda is still external to vcpkg
* v db
---------
Co-authored-by: Jim wang (BEYONDSOFT CONSULTING INC) <v-wangjim@microsoft.com>
* Replace uwp does not support functions
* update version
* fix patch
* update version
* del baseline
---------
Co-authored-by: Jim wang (BEYONDSOFT CONSULTING INC) <v-wangjim@microsoft.com>
macOS 14.2.1 on amd64, 14.3 on arm64
XCode Console Tools 15.1
Other changes:
macOS install is done from the installers rather than from the recovery partition
readme.md is now written for a vcpkg-team audience
vagrant is removed as a dependency so that discussion of how to persist the VMs between machines could be included
arm64 is added using https://github.com/s-u/macosvm
* Fix lib suffix matching
* Preserve flags when transforming standard libs
* Use separate_arguments
* Fix transform
* [vcpkg_configure_make] Fix SKIP_CONFIGURE
* Update linker flags
* Update linker flags
* Fix regex substitution
* Restore full CI
* Reuse configure's linker flags setup
* Handle ldflags separately from linker flags
* Factor out common definitions
* Control docdir and mandir for debug
* Use vcpkg_list APPEND
* Don't pass -avoid-version into configure
* Restore lost escaping
* Copy --target from LDFLAGS to CC/CXX
* Consolidate macros into one function
* Elaborate ABI flags
* Elaborate flag processing
* Update warnings for embedded space
* Update windows tool path fixup
* [libudns] No cross builds
* [vcpkg_find_acquire_program] Add VSCLANG
Find VS's clang without fallback to the giant LLVM download.
* [gmp] Update CCAS setup
* [nettle] Update CCAS setup
* Fix VSCLANG
* WIP
* Restore processing of isysroot
* [nettle] Fix assembler option
* [liburing] Adjust
* Variable name changes
* Remove redundant separate arguments
* Move -m32/-m64 to ABI flags
* Unify ABIFLAGS spelling
* CI
* Revert VSCLANG
* Use GNU Make to build autotools ports on FreeBSD (microsoft/vcpkg#32282)
* Fix flag removal
* Drop separation of ABI flags
* Handle '-arch=...'
* Revert "Control docdir and mandir for debug"
This reverts commit d8293a1997.
* [icu] Pass uwp option to pkgdata
* Restore old osx flags hook
* Add triplet variable to make libtool pass --target to linker
---------
Co-authored-by: Schaich, Alonso <alonsoschaich@fastmail.fm>
* Add magma port
* fix patch
* no cmake config to fix
* deleted wrong dir
* mark magma fail in ci baseline
* v db
* fix Cflags
* v db
---------
Co-authored-by: MonicaLiu <liuyumei01@beyondsoft.com>
* [vulkan-sdk] Separate port
* Update ci.baseline.txt
* [hikogui] Using glslc from shaderc
* [vulkan] Drop LICENSE.txt
* [vulkan-sdk-components] Avoid vulkan-sdk name
* [vulkan] Fixup copyright text
* Install vulkan.
* add gfxreconstruct
* format manifest and cr changes
* remove moltenvk
* fix ci part 1
* fix a dep
* more fixes
* remove vulkan failures from CI pipeline
* remove annoying stuff to deal with in static builds
* fix trailing ,
* remove vendored cmakelists
* force ci to be green
* format manifest
* Fix more ci issues
* fix hikogui
* make ci happier
* add jsoncpp dep
* only remove the debug folder if targeting windows
* bump port-version
* v db
* vulkan-loader add usage
* Rename vulkantools to lunarg-vulkantools
* Make VMA install headers platform dependent
* Remove vcpkg_check_linkage
* readd vulkan-validationlayers
* v db
* Extract vcpkg_extract_archive from vcpkg_find_acquire_program.
* Extract vcpkg_download_sourceforge from vcpkg_from_sourceforge.
This allows vcpkg_find_acquire_program to download from SourceForge without needing to temporarily change _VCPKG_EDITABLE.
* Use whether a URI is known for an entity to decide whether to downloads it rather than checking a separate supported_on_unix boolean.
* Add unparsed arguments check to vcpkg_extract_archive
* Hook up z-applocal, work started by @vicroms.
* Fix spelling of utf8
* Use standard warning formats.
* Don't get in the way of stdout.
* Don't try to Applocal deploy if the linker does not run.
* Make VcpkgUseBuiltInApplocalDeps docs a bit nicer.
* Change to (experimental) prefix.
* Add an X.
* [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.
* There is a space problem in modifying the file path
* Version database
* update version
* Update generate-ports.ps1
---------
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
* PASSING, REMOVE FROM FAIL LIST: chipmunk:arm64-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: chipmunk:x64-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
REGRESSION: fastrtps:arm-neon-android failed with BUILD_FAILED. If expected, add fastrtps:arm-neon-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: fastrtps:arm64-android failed with BUILD_FAILED. If expected, add fastrtps:arm64-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: fastrtps:x64-android failed with BUILD_FAILED. If expected, add fastrtps:x64-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
Previously blocked by:
PASSING, REMOVE FROM FAIL LIST: foonathan-memory:arm-neon-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: foonathan-memory:arm64-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: foonathan-memory:x64-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
REGRESSION: cmake-user:x86-windows cascaded, but it is required to pass. (C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt).
REGRESSION: hdf5:x86-windows failed with BUILD_FAILED. If expected, add hdf5:x86-windows=fail to C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: vcpkg-ci-mathgl:x86-windows cascaded, but it is required to pass. (C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt).
REGRESSION: vcpkg-ci-opencv:x86-windows cascaded, but it is required to pass. (C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt).
REGRESSION: vcpkg-ci-openimageio:x86-windows cascaded, but it is required to pass. (C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt).
REGRESSION: vcpkg-ci-paraview:x86-windows cascaded, but it is required to pass. (C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt).
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
Command failed: "C:/Program Files/PowerShell/7/pwsh.exe" -noprofile -executionpolicy Bypass -nologo -file C:/a/1/s/scripts/buildsystems/msbuild/applocal.ps1 -targetBinary D:/packages/hdf5_x86-windows/tools/hdf5/h5clear-shared.exe -installedDir D:/packages/hdf5_x86-windows/bin -verbose
Working Directory: C:/a/1/s
Error code: Access violation
See logs for more information:
D:\buildtrees\hdf5\copy-tool-dependencies-2-out.log
D:\buildtrees\hdf5\copy-tool-dependencies-2-err.log
Previous CI run passed, so I'm going to hope we got a bad machine or something and move on for now.
REGRESSION: openvino:x64-linux failed with BUILD_FAILED. If expected, add openvino:x64-linux=fail to /agent/_work/1/s/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: openvino:x64-osx failed with BUILD_FAILED. If expected, add openvino:x64-osx=fail to /Users/vagrant/Data/work/2/s/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: openvino:x64-windows failed with BUILD_FAILED. If expected, add openvino:x64-windows=fail to C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: openvino:x64-windows-static failed with BUILD_FAILED. If expected, add openvino:x64-windows-static=fail to C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: openvino:x64-windows-static-md failed with BUILD_FAILED. If expected, add openvino:x64-windows-static-md=fail to C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt.
See discussion in https://github.com/microsoft/vcpkg/pull/32418 / https://github.com/openvinotoolkit/openvino/issues/18465 -- openvino conflicts with oneDNN because the vcpkg copy is not the same as their forked copy.
REGRESSION: physx:x64-linux failed with FILE_CONFLICTS. If expected, add physx:x64-linux=fail to /agent/_work/1/s/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: physx:x64-windows failed with FILE_CONFLICTS. If expected, add physx:x64-windows=fail to C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: physx:x64-windows-static failed with FILE_CONFLICTS. If expected, add physx:x64-windows-static=fail to C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt.
REGRESSION: physx:x64-windows-static-md failed with FILE_CONFLICTS. If expected, add physx:x64-windows-static-md=fail to C:\a\1\s\scripts\azure-pipelines/../ci.baseline.txt.
See discussion in https://github.com/microsoft/vcpkg/pull/32432 -- omniverse-physx-sdk was added 5 days ago and conflicts.
REGRESSION: libev:arm-neon-android failed with FILE_CONFLICTS. If expected, add libev:arm-neon-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: libev:x64-android failed with FILE_CONFLICTS. If expected, add libev:x64-android=fail to /vcpkg/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: libev:x64-linux failed with FILE_CONFLICTS. If expected, add libev:x64-linux=fail to /agent/_work/1/s/scripts/azure-pipelines/../ci.baseline.txt.
REGRESSION: libev:x64-osx failed with FILE_CONFLICTS. If expected, add libev:x64-osx=fail to /Users/vagrant/Data/work/2/s/scripts/azure-pipelines/../ci.baseline.txt.
Fixed by https://github.com/microsoft/vcpkg/pull/32471
REGRESSION: ryu:x64-linux failed with FILE_CONFLICTS. If expected, add ryu:x64-linux=fail to /agent/_work/1/s/scripts/azure-pipelines/../ci.baseline.txt.
error: The following files are already installed in /mnt/vcpkg-ci/installed/x64-linux and are in conflict with ryu:x64-linux
Installed by bde:x64-linux
debug/lib/libryu.a
include/ryu/ryu.h
lib/libryu.a
* Exclude chipmunk:arm-neon-android with a supports expression rather than with ci.baseline.txt as this is explicitly blocked in the sources.
