Fixes `OUTPUT_VARIABLE`, `ERROR_VARIABLE`.
vcpkg always wants logfiles. CMake (`execute_process`) doesn't send
stdout/stderr to files and variables at the same time, and even "the
precedence is not specified". So simultaneous output has to be handled
in `vcpkg_execute_required_process`.
At this occasion, port the arguments for stripping trailing whitespace.
`tensorflow-common` implicitly relied on the broken behavior. I chose
the minimal fix: drop the pointless calls, just set the empty value.
while playing with qtbase on x64-uwp i found that it could not pass a
try_compile command since important variables are not correctly
forwarded. As such I concluded that the handling of try_compile in vcpkg
is completely wrong.
Fixes#37189
- [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.
Fixes:
~~~
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
Compatibility with CMake < 3.5 will be removed from a future version of
CMake.
~~~
Add test-engine feature to the imgui port:
https://github.com/ocornut/imgui_test_engine
I made it a feature because they both depend on each other to build,
that's why it is a feature instead of a new port.
- [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.
- [ ] ~~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.
- Change homepage URLs to point to documentation instead of GH.
- Allow encoding alternative propagation of `supports`/`platform` so
that changes don't need to be selected manually.
- Allow to suppress the generated dependency `platform` expression when
a dependency is non-optional.
(`boost-parameter` requires `boost-python`, and the dependency
transitively determines the supported platforms of the dependent port.)
- For port `boost`, generate `platform` expression from transitive
`supports` limitations.
(`boost-parameter` platform expression must account for `boost-python`.)
This fixes port `boost` for uwp. And so it can now be directly
referenced from `vcpkg-ci-boost` which is already enforced to `pass` in
ci.baseline.txt. 🎉
- Restores sorting of `$portData`.
- Use the same tarball download area and naming as `vcpkg install`.
This PR doesn't include the updates to `boost-container` (#38806),
`bost-interprocess` (#38815) and boost-math (#38728)
Refactor curl port:
- Add test
- Refine dependencies patch
- gssapi feature is not for windows
<!-- 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).
- [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.
<!-- 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: WangWeiLin-MV <156736127+WangWeiLin-MV@users.noreply.github.com>
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)
<!-- 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#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
~~~
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>
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.
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>
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>
* 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"
* pulling has_synchro bits from https://github.com/microsoft/vcpkg/pull/27694
* bump port version
* version
* fix clang
* bump version
* version
* oops
* bump dependency version for boost-atomic's boost-module-build-helper dependency
* version
* revert renaming stuff -.-
* version
* remove detection stuff for lib prefix/suffix
* version
* fix indentation
* version
* forgot one
* version
* one more!
* version
* revert changes to cmake-get-vars
* version
* generate ports
* version db
* generate ports
* version db
---------
Co-authored-by: Alexander Neumann <30894796+Neumann-A@users.noreply.github.com>
* [vcpkg-ci-msys2] Add clangarm64 support
UCRT binaries for ARM64, built with clang.
* [vcpkg_find_acquire_program(PKGCONFIG)] Switch to pkgconf, add arm64
* CI
* [vcpkg-ci-msys2] New test port for msys2 freshness
* Add features for script updates
* Remove duplicate libbz2 entry
* Automatically update all msys packages, add autoconf-wrapper
* Update primary URL and mirrors
* Follow repo renames
* Fix dependencies of 'file'
* Resolve dependencies at runtime
Don't require msys2 packages to be order from dependent to independent.
This allows to directly use the packages official dependencies, even
if they contain cycles.
It also allows to maintain a stable alphabetical order of the package
declarations, even if the dependencies change over time. This helps to
avoid duplicate declaration.
* Fix updating
* [gettext] Preset more MSVC checks
* Update msys2 packages
* gettext fixes
* CI
* Simplify: Remove update-critical
Desired changes can be picked in git gui etc..
* PKGCONFIG moved
---------
Co-authored-by: Monica <v-liumonica@microsoft.com>
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
* Print stack traces for failed unit tests
* Add test for vcpkg_fixup_pkgconfig.cmake
* Check for 'optimized' and 'debug' in pc files
* Check for 'NOTFOUND' and for 'ns::target' in pc files
* Check for, and fix, line continuations
* Test file path substitutions
* Move contents processing into separate function
* Update and leverage line break normalization
* Pass prefix to data processing
* Validate only the collapsed Libs
* Test removal of '<field>.private'
* Declare unit test license (same as vcpkg)
* Replace ';' with ' ' in 'Libs:'
* Disambiguate parameter variable names
* Test quoting of variables
* Fix quoting of variables
* Quote whole parameters
* Process and quote libs item-wise
* Resolve keywords 'optimized', 'debug', 'debug'
* Consistency
* CI [skip actions]
* CI [skip actions]
* Don't fail on detected errors
* Disable unit-testing for fatal errors
Co-authored-by: Billy O'Neal <bion@microsoft.com>
* [cgns] update to 4.2.0
* [vtk-m] update to 1.6.0
* [vtk] Update to 9.0.1-pv5.9.1
- VTK update to match release version of ParaView
* [ParaView] Update to 5.9.1
* version stuff
* fix automatic svg linkage in static builds
* update qt5-svg
* revisit vtk
- fix build with vtk-m 1.6
- remove unused patches
- remove comments
* bump version
* remove two commented lines
* version stuff
* remove old PR version
* commit stuff
* commit stuff
* update notes
* wip commit
* update paraview
* fix hdf5 patch
* fix patch
* fix patch
* fix portfile
* add mpi feature
* format manifest
* use relativ path
* trace
* retry
* move qml files again
* try with host triplet
* - use VCPKG_CRT_LINKAGE
- use METIS not metis
* fix casing Zlib
* hopefully more fixes on other platforms.
* fix patch
* fix missing ws
* fix typos
* scale down to warning
* revert jsoncpp change
fix zoltan on osx?
* move trace option to failing port
* move trace option to failing port
* Revert "trilinos vcpkg.json changes"
* verdict fix osx build ?
* fix patch
* fix internal find_package call
* also apply correct case for metis
* disable METIS on osx
* vtk-m don't support arm.
* force more features in Ci
* fix missing ,
* more fixes
* more vtk python try and error.
* - paraview python setup same as vtk
- remove openvr from platforms not supporting it
- trace openimageio
* fix case and remove fmt for openimageio.
* trying to fix stuff
* set hash to 0
* [skip actions] add missing module
* WebCore module moved to paraview&python
* fixes
* remove patch in vtk-dicom
* add var to maybe unused
* use correct 5.11 ref instead of the one in release
* Patch cleanup round 1
* remove empty patch parts
* fix vtkm configs
* reintegrate jsoncpp.patch
* fix patch
* add single seacas/kokkos/zoltan ports
* throw out trilinos, zoltan, kokkos
replace trilinos with seacas
make seacas work for dynamic windows
* fix mpi feature
* fix dependency
* retry dep fix
* rename target
* remove double line
* fix target
* fix patch
* retry
* remove cgns config
* fix cgns
* no seacas trace
* lowercase hdf5 target
* fix case of metis
* disable Fortran
* add iotr patch
* add additional config folder
* handel case sensitive Seacas again
* get trace again and force jsoncpp
* update cmake to 3.25.0
* bump port-version
* add patch from vtk upstream
* cleanup, format-manifest
* fix port version
* v db
* opencv4 always inject deps.
* fix test port to not require stuff which is not supported on x86
* Fix HDF5 lookup in opencv4
* only delete bin folder in static builds
* add license field
* v db
* add missing "
* v db
* trace again
* fix rtabmap python dep
* fix openimageio by deleting the find module
* v db
* cr cleanup
* v db
* opencv4 v db due to merge with master. Had to bump port version
* v db
* v db
* v db
* CR comments
* v db for cr comments
* trace theia output
* revert theia trace
* v db
* try without patch
* revert rtabmap changes
* v db after merge
* v db for all
* Use official zstd config
* Require packages for features
* Test zstd in CI
* Enable libtiffxx on arm
* Update versions
* Assume ZSTD_decompressStream
* Don't put targets into TIFF_LIBRARIES
* [qt5-imageformats] Use libtiff-4.pc
* [zstd] Revise thread lib export
* Mark link libs with LINK_ONLY
* Revert "[zstd] Revise thread lib export"
This reverts commit a99e6378a67adc68e9e43e6e193206a5ddcba60e.
* [qt5-imageformats] Get all tiff lflags
* [gdk-pixbuf] Use libtiff-4 pc file for msvc
* [qtimageformat] Workaround for QTBUG-95052
* Use expressive patch name
* Fix BROTLI_INCLUDE_DIR import
* glog is unused (off by default)
* Cleanup portfile, fix 'arrow[core]'
* Add CI test port
* Update to 8.0.1 [skip actions]
* Declare dependency source for substituted packages
* Trim obsolete patch chunks
* Fix static link libs export
* Use substituted targets directly, for proper export
* Fix snappy lib export to pc file
* Update versions
* Add license for test port
* Add =pass entries for the new "vcpkg-ci-Xxx" port.
Co-authored-by: Billy O'Neal <bion@microsoft.com>
* Revert "[wxwidgets] Remove debug asserts from Release build. (#25240)"
This reverts commit 6e16931acdf85ab5476973ba00d8eda733f42858.
* Update to 3.1.7
* Update installation layout
* Upstream CMake export is not ready for use
* Update versions
* Remove obsolete patch
* Use msvc layout for mingw on windows
* Add debug-support feature
* Update versions
* Fix condition
* Update versions
* Restore symlink patch
* Update versions
* Remove trace option from test port
* Enable testing without feature debug-support
* Fixup defaults for using without debug support
* Expect wxrc-3.1 for mingw cross builds ("unix" layout)
* Update versions
* Deduplicate platform restrictions
Ports might be installed even if excluded via 'platform' restrictions.
However, for this test ports it is fair to require that if a port can
be installed, the platform shall not be exlcuded, and the test shall
pass.
* Implement CMake version condition
* Fix mingw cross builds
* Extend cmake-user testing
* Update for hidden Iconv dependencies
* Format manifest
* Add uwp exclusions
* [wxWidgets] Remove debug asserts from Release build.
Currently when building wxWidgets in Release mode, the debug asserts are enabled.
This fixes this issue by providing a necessary define to disable them.
Ref: https://docs.wxwidgets.org/3.1.6/group__group__funcmacro__debug.html
[wxCharts, vcpkg-ci-wxwidgets] Update ports to include fix for wxWidgets release build with debug asserts off when building a dynamic/shared library.
Signed-off-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>
* Update wxcharts.json
Co-authored-by: LilyWangLL <94091114+LilyWangLL@users.noreply.github.com>
* Fix vcpkg_host_path unit test
* Fix unit test variable control
* Enable all test features by default
* Fix recognition of PREPEND
* CMake doesn't set env vars to empty value
* Remove pointless STATUS message
* [llvm] update to v14.0.0
* [llvm] BOLT sub-project support
* [llvm] fix tools install paths
* [halide] update to v14.0.0
* update versions
* [vcpkg-get-python-packages] fix "LOGNAME should be specified" warning
* [mesa] update to v22.0.1
* update versions
* update versions
* update version
* [mesa] update to 22.0.2
* update version
* [mesa] update patches
* update version
* [llvm] update to v14.0.3
* update version
* [llvm] remove depricated feature
* [llvm] allow to build OpenMP on Windows and remove incomplete cross-compile support
* update version
* [llvm] use vcpkg_cmake_get_vars
* [llvm/openmp] install CMake file in share/openmp
* [llvm] add vcpkg-cmake-get-vars dependency and slip post build check if OpenMP is enabled
* update version
* Skip wxwidgets test on Linux
On Linux, wxwidgets needs system libs which conflict with vcpkg ports.
* Test curl
* Execute build to detect wrong libs
* Add comment for wxwidgets
* Fix unused CMake variable warning
* Acquire msys only on Windows
* Revise APNG variable names and usage
* Fix download mode usability with APNG
* Uncompress APNG patch with gzip
gzip is a default package of MSYS2 and (most) other systems.
7z download is implemented for windows only.
* Revise main CMake patches
cmake.patch deals with libpng build configuration.
fix-export-targets deals with cmake config export.
* Revise pkgconfig patching and fixup
* Additional cleanup
* Add usage based on FindPNG.cmake
* Update versions
Co-authored-by: Leonid Pospelov <pospelovlm@yandex.ru>
* Verify library location for debug vs. release
* Use existing variables for wrapper
* Always install freetype wrapper
* Quote @expressions
* Set policies for freetype wrapper (#19459)
* Test JPEG
* Fix jpeg wrapper for CMake < 3.12
* Test TIFF
* Test with current and oldest supported CMake
* Test and fix icu cmake wrapper
* CMake policy fixes [skip actions]
* Update versions
* CI
* CI
* Nicole CRs
* Disable Curses test
* Prefer <Pkg>_VAR over <PKG>_VAR
Co-authored-by: JackBoosY <yuzaiyang@beyondsoft.com>
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
Co-authored-by: Billy Robert O'Neal III <bion@microsoft.com>
