vcpkg
vcpkg copied to clipboard
[vcpkg scripts] Crosscompiling fixes
@m-kuhn any other additions necessary?
Sending it through the build pipeline now
Looks good, minimal additional changes are needed for iOS, either in here or as a follow up
https://github.com/Neumann-A/vcpkg/pull/9
@m-kuhn does the CMAKE_${lang}_OSX_DEPLOYMENT_TARGET_FLAG
change work for you?
@m-kuhn does the
CMAKE_${lang}_OSX_DEPLOYMENT_TARGET_FLAG
change work for you?
Yes, this looks good.
Sidenote: it took me an extra run to figure out that a change to scripts/get_cmake_vars/CMakeLists.txt
does not trigger a rebuild, so I had to fake a modification into scripts/cmake/vcpkg_configure_make.cmake
to force rebuild.
@JackBoosY another baseline regression...
@JackBoosY another baseline regression...
Fixing in https://github.com/microsoft/vcpkg/pull/26783.
@Neumann-A Could you please resolve the conflicts?
/azp run
Azure Pipelines successfully started running 1 pipeline(s).
Hmm don't know what happened to jemalloc on osx. Has been green in https://github.com/microsoft/vcpkg/pull/26617/commits/184abe3c41315e6a353b0016eb8ebce38c372b92 and only thing I did was merge with master. Looks like a concurrency issue?
Hmm don't know what happened to jemalloc on osx. Has been green in 184abe3 and only thing I did was merge with master. Looks like a concurrency issue?
install: mkdir /Users/vagrant/Data/packages/jemalloc_x64-osx/Users/vagrant/Data/installed: File exists
This is a typical symptom of concurrency issues during make install
on osx. We need a DISABLE_PARALLEL_INSTALL
and/or a reliable mkdir
wrapper for osx.
Should we wait for #27105 merge or just rerun the pipeline test?