* Added portfile and control
* Added patch file to support MSVC
* Added description for msgpack11 in CONTROL
* added homepage to Control, code refactoring for portfile
* refactored portfile
* made align changes
* Update portfile.cmake
* Update CONTROL
removed v from the version
* added ref properly
Co-authored-by: Mayank Kataruka <37381526+mayankkt9@users.noreply.github.com>
* [anyrpc] Updated to latest commit
Updated to latest commit and removed patch, as it
is no longer needed.
* [anyrpc] Updated to latest commit
Removed deprecated `include(vcpkg_common_functions)`.
Only the current and the previous version of doxygen can be downloaded
from: http://doxygen.nl
Sourceforge provides the current version and any previously released
versions for download: https://sourceforge.net/projects/doxygen/files/
Add sourceforge as alternative download URL. This avoids situations,
when the version of doxygen in vcpkg is n-2 and cannot be downloaded
any more, see e.g. commit: 526f937580
* [open62541] Update to v1.0
* Remove dependency on python-six
* Fix CI
* Manually specify the version
* Fix install binaries directory
* Fix end line
* Add homepage and modernize cmake
* enable ssl feature on selected under linux
* Complete implementation of ACE's installtion method under Linux
* reorder code logic structure of ACE's portfile
* add some debug log for ACE's portfile
* Bump tweak version of ACE CONTROL file
* fix invalid CL error for build/install perl scripts under Linux
* [ace] replace vcpkg_execute_required_process with vcpkg_execute_build_process
* [xerces-c] Update REF and SHA512
* [sfml] re-trigger ci
* [pcl] re-trigger ci
* [boost-signals] re-trigger ci
* [tmxparser] re-trigger ci
* [soil2] switch repo to github
* [gtest] re-trigger ci
* Fix tinyfiledialogs not being fetchable from sourceforge
Fix tinyfiledialogs not being fetchable from sourceforge. Use github instead.
* Update CONTROL
* Update portfile.cmake
* Update portfile.cmake
Update source url
* Update CONTROL
* Add support for building with MinGW
Tested with MSYS2 MinGW 8.3.0, gcc-mcf.lhmouse MinGW 9.2.1,
and StephanTLavavej/mingw-distro!
* Add MinGW toolchain
From your MinGW configured shell you could just use vcpkg to
configure packages.
An x64-mingw triplet would look like:
```
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE static)
set(VCPKG_ENV_PASSTHROUGH PATH)
set(VCPKG_CMAKE_SYSTEM_NAME MinGW)
```
* Add MinGW community tripplets
x64 tested with https://github.com/StephanTLavavej/mingw-distro
x86, arm64, arm tested with https://github.com/mstorsjo/llvm-mingw
* Move untested triplets to Community Triplets
* Document community triplets
* Load community triplets by default and alert when using one
* [triplets] Merge documentation of community triplets
* Bump version
* added cleanup command to embree3 port for static build
* updated CONTROL file with version tag
* check if file exists before cleanups
* fix baseline
Co-authored-by: nicole mazzuca <mazzucan@outlook.com>
To install a specific version of a package via homebrew, an `@` symbol must be placed in-between the package name and its version.
Added missing symbol to `toolsrc/CMakeLists.txt`
See homebrew console output for reference:
```
Kristofs-Mac-Pro:vcpkg kristofdaja$ brew search gcc
==> Formulae
gcc gcc@5 gcc@7 x86_64-elf-gcc
gcc@4.9 gcc@6 gcc@8
```
* [boost-python] Support Python2 as feature, fix build with installed Python2
* [boost-python] Update generate script to support Python2 mod
* Re-generate boost ports
* [boost-modular-build-helper] Update to 1.71.
[boost-build] Update to 1.71.
* [boost-modular-build-helper] Remove manual library name changing
[boost-iostreams] Use boost-modular-headers.cmake script
* Delete temporary file.
* Revert changes in modular build script.
* Update ports versions.
* [boost-modular-build-helper] Fix build boost-iostreams with LZMA and ZSTD
* [boost] Update to 1.72.0
* [libtorrent] Fix build with Boost 1.72.0
Original PR: https://github.com/arvidn/libtorrent/pull/4091
* Update ci.baseline.txt:
- fail libgo:* due to use the removed class from Boost.Context 1.72.0 (reported issue https://github.com/yyzybb537/libgo/issues/214)
- pass boost-context:arm64-windows
- fix typo
* Folly only supports the x64 architecture
* fail boost-coroutine:arm64-windows=fail and boost-fiber:arm64-windows=fail because they use fcontext_t from Boost.Context which is not implemented for Windows on ARM64 (reported issue https://github.com/boostorg/context/issues/130)
* Fix globbing-expressions
* Add vcpkg_buildpath_length_warning(37) for boost-system.
Revert boost-iostreams port changes.
* Update ci.baseline.txt
* fixes to get vcpkg up and running when behind corporate proxy
* clean up of code to check if HTTP_PROXY environment variable is set
* fixed compiler errors for non win32 systems
* [vcpkg] Simplify HTTPS_PROXY code for WinHTTP
Co-authored-by: Robert Schumacher <roschuma@microsoft.com>
Use write_basic_package_version_file() to create the
libffiConfigVersion.cmake file.
This allows detection of the libffi version using cmake.
An example, where this is relevant is e.g. glib 2.62, with the
following code in meson.build:
libffi_dep = dependency('libffi', version : '>= 3.0.0',
fallback : ['libffi', 'ffi_dep'])
When the libffiConfigVersion.cmake file is present, the following output
can be found in the meson-build.log:
Run-time dependency libffi found: YES 3.1
