profile
viewpoint

diablodale/jit.openni 43

Max Jitter external for OpenNI middleware, supports Kinect, Windows and Mac OSx

diablodale/pinentry-wsl-ps1 25

GUI for GPG within Windows WSL for passwords, pinentry, etc.

diablodale/dp.kinect2 17

Microsoft Kinect v2 extension for Cycling '74 Max

diablodale/dp.kinect 15

Cycling 74 Max external using Microsoft Kinect SDK

diablodale/boids_max 10

Boids implementation for Cycling74 Max and Jitter

diablodale/nanodimmer 2

Aeotec Nano Dimmer device handler for SmartThings

diablodale/openni_recorder 2

A recorder of OpenNI data; uses a XML configuration file, good for Kinect

diablodale/basic-auth 1

Wordpress REST API Basic Authentication over HTTPS

diablodale/gnucash-dev-docker 1

Docker containers for automated OS setup and dev/build environ for gnucash v3+ binaries and docs

diablodale/amazon-ecs-cli 0

The Amazon ECS CLI enables users to run their applications on ECS/Fargate using the Docker Compose file format, quickly provision resources, push/pull images in ECR, and monitor running applications on ECS/Fargate.

issue openedmicrosoft/Azure-Kinect-Sensor-SDK

default logging to stout doesn't follow documented rules when debug message handler registered

Registering a debug log handler before open() does not stop default logging to stdout. This is errant with respect to documentation at https://microsoft.github.io/Azure-Kinect-Sensor-SDK/master/group___functions_ga77a5f83e56a04136df1398478353193d.html

If k4a_set_debug_message_handler registers a callback function before k4a_device_open() is called, then the default for environmental controls is as if K4A_ENABLE_LOG_TO_STDOUT=0 was specified.

Setup

  • Microsoft Windows [Version 10.0.19041.329]
  • Azure SDK 1.4.0
  • Visual Studio Community 16.6.3
  • Current Firmware Versions
    RGB camera firmware:      1.6.108
    Depth camera firmware:    1.6.79
    Depth config file:        6109.7
    Audio firmware:           1.6.14
    Build Config:             Production
    Certificate Type:         Microsoft
    

Repro

C code that:

  1. k4a_set_debug_message_handler(k4aLoggingMessageHandler, nullptr, K4A_LOG_LEVEL_WARNING);
  2. device::open()
  3. device.start_cameras()
  4. k4aLoggingMessageHandler() is a function that receives calls and does nothing within its function

Result

The stdout is spammed with countless log messages.

Expected

Silence. No logs. Why? Because k4aLoggingMessageHandler() does nothing. And the documentations writes that if I set a handler before open(), then "...is as if K4A_ENABLE_LOG_TO_STDOUT=0" and which that variable state causes "...disable logging to stdout".

Logs

As the issue is the logger itself, I'm unsure what to provide other than a sample of the log entries I see

[2020-07-03 18:36:56.970] [error] [t=4744] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\capturesync\capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS:  22666866 type:Color
[2020-07-03 18:36:57.003] [error] [t=4744] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\capturesync\capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS:  22700200 type:Color
[2020-07-03 18:36:57.034] [error] [t=4744] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\capturesync\capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS:  22733533 type:Color
[2020-07-03 18:36:57.066] [error] [t=14244] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\capturesync\capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS:  22766855 type:Color
[2020-07-03 18:36:57.098] [error] [t=14244] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\capturesync\capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS:  23600188 type:Color
[2020-07-03 18:36:57.130] [error] [t=14244] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\capturesync\capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS:  23633533 type:Color
[2020-07-03 18:36:57.163] [error] [t=14244] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\capturesync\capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS:  23666866 type:Color
[2020-07-03 18:36:57.194] [error] [t=14244] D:\a\1\s\extern\Azure-Kinect-Sensor-SDK\src\capturesync\capturesync.c (142): replace_sample(). capturesync_drop, releasing capture early due to full queue TS:  23700200 type:Color

Workaround

Manually set the environment variable K4A_ENABLE_LOG_TO_STDOUT=0.

created time in a day

issue openedmicrosoft/Azure-Kinect-Sensor-SDK

wrong log level for replace_sample(). capturesync_drop -- misclassification, spamming, etc.

The k4a_log_level_t of the below code is incorrectly set to error. This state in the code is a quite common natural state (up to 30 times per second) in which the underlying subsystem is managing its queue and keeping frames fresh. Nothing wrong, erroneous, dangerous, or warnful about having fresh frames.

Therefore, error is not appropriate and leads to spamming the console/message handler and making it exceedingly difficult to find the actual errors within the spam.

https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/52cfb4a87639b3db9cb176b8b9ac814e2b5a4900/src/capturesync/capturesync.c#L137-L142

My preference is K4A_LOG_LEVEL_TRACE At worst, it should be K4A_LOG_LEVEL_INFO

That it is not an error is also supported by @wes-b when they write "...There are other warnings generated..." at https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/1112#issuecomment-596688870

Fix

Trivial. Change LOG_ERROR to LOG_TRACE

created time in a day

issue commentmicrosoft/vcpkg

CMake Error at scripts/ports.cmake:14 (message) Your vcpkg executable is outdated

Running bootstrap-vcpkg -disableMetrics results in a vcpkg version which is the same version but has different ending modifiers. This re-bootstrap reports

Vcpkg package management program version 2020.02.04-nohash

while the version reported in the OP above is

Vcpkg package management program version 2020.02.04-nohash-external

vcpkg install for first package that failed to rebuild boost-build for each the four triplets worked with no visible errors.

C:\njs\vcpkg>vcpkg install boost-build:x64-windows-static-md-v142-sdk10b17134
Computing installation plan...
The following packages will be built and installed:
    boost-build[core]:x64-windows-static-md-v142-sdk10b17134
Starting package 1/1: boost-build:x64-windows-static-md-v142-sdk10b17134
Building package boost-build[core]:x64-windows-static-md-v142-sdk10b17134...
-- Using community triplet x64-windows-static-md-v142-sdk10b17134. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: C:\njs\vcpkg\triplets\community\x64-windows-static-md-v142-sdk10b17134.cmake
-- Using cached C:/njs/vcpkg/downloads/boostorg-build-boost-1.73.0.tar.gz
-- Using source at C:/njs/vcpkg/buildtrees/boost-build/src/ost-1.73.0-018fb008dd
-- Using cached C:/njs/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Using cached C:/njs/vcpkg/downloads/boost-1.73.0-boostcpp.jam
-- Installing: C:/njs/vcpkg/packages/boost-build_x64-windows-static-md-v142-sdk10b17134/share/boost-build/copyright
-- Installing: C:/njs/vcpkg/packages/boost-build_x64-windows-static-md-v142-sdk10b17134/tools/boost-build/boostcpp.jam
-- Bootstrapping...
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-build[core]:x64-windows-static-md-v142-sdk10b17134... done
Installing package boost-build[core]:x64-windows-static-md-v142-sdk10b17134...
Installing package boost-build[core]:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-build:x64-windows-static-md-v142-sdk10b17134: 40.13 s

Total elapsed time: 40.17 s


C:\njs\vcpkg>vcpkg install boost-build:x64-windows-static-md-v142-sdk81
Your feedback is important to improve Vcpkg! Please take 3 minutes to complete our survey by running: vcpkg contact --survey
Computing installation plan...
The following packages will be built and installed:
    boost-build[core]:x64-windows-static-md-v142-sdk81
Starting package 1/1: boost-build:x64-windows-static-md-v142-sdk81
Building package boost-build[core]:x64-windows-static-md-v142-sdk81...
-- Using community triplet x64-windows-static-md-v142-sdk81. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: C:\njs\vcpkg\triplets\community\x64-windows-static-md-v142-sdk81.cmake
-- Using cached C:/njs/vcpkg/downloads/boostorg-build-boost-1.73.0.tar.gz
-- Using source at C:/njs/vcpkg/buildtrees/boost-build/src/ost-1.73.0-018fb008dd
-- Using cached C:/njs/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Using cached C:/njs/vcpkg/downloads/boost-1.73.0-boostcpp.jam
-- Installing: C:/njs/vcpkg/packages/boost-build_x64-windows-static-md-v142-sdk81/share/boost-build/copyright
-- Installing: C:/njs/vcpkg/packages/boost-build_x64-windows-static-md-v142-sdk81/tools/boost-build/boostcpp.jam
-- Bootstrapping...
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-build[core]:x64-windows-static-md-v142-sdk81... done
Installing package boost-build[core]:x64-windows-static-md-v142-sdk81...
Installing package boost-build[core]:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-build:x64-windows-static-md-v142-sdk81: 31.04 s

Total elapsed time: 31.08 s


C:\njs\vcpkg>vcpkg install boost-build:x86-windows-static-md-v142-sdk10b17134
Computing installation plan...
The following packages will be built and installed:
    boost-build[core]:x86-windows-static-md-v142-sdk10b17134
Starting package 1/1: boost-build:x86-windows-static-md-v142-sdk10b17134
Building package boost-build[core]:x86-windows-static-md-v142-sdk10b17134...
-- Using community triplet x86-windows-static-md-v142-sdk10b17134. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: C:\njs\vcpkg\triplets\community\x86-windows-static-md-v142-sdk10b17134.cmake
-- Using cached C:/njs/vcpkg/downloads/boostorg-build-boost-1.73.0.tar.gz
-- Using source at C:/njs/vcpkg/buildtrees/boost-build/src/ost-1.73.0-018fb008dd
-- Using cached C:/njs/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Using cached C:/njs/vcpkg/downloads/boost-1.73.0-boostcpp.jam
-- Installing: C:/njs/vcpkg/packages/boost-build_x86-windows-static-md-v142-sdk10b17134/share/boost-build/copyright
-- Installing: C:/njs/vcpkg/packages/boost-build_x86-windows-static-md-v142-sdk10b17134/tools/boost-build/boostcpp.jam
-- Bootstrapping...
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-build[core]:x86-windows-static-md-v142-sdk10b17134... done
Installing package boost-build[core]:x86-windows-static-md-v142-sdk10b17134...
Installing package boost-build[core]:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-build:x86-windows-static-md-v142-sdk10b17134: 31.24 s

Total elapsed time: 31.28 s


C:\njs\vcpkg>vcpkg install boost-build:x86-windows-static-md-v142-sdk81
Computing installation plan...
The following packages will be built and installed:
    boost-build[core]:x86-windows-static-md-v142-sdk81
Starting package 1/1: boost-build:x86-windows-static-md-v142-sdk81
Building package boost-build[core]:x86-windows-static-md-v142-sdk81...
-- Using community triplet x86-windows-static-md-v142-sdk81. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: C:\njs\vcpkg\triplets\community\x86-windows-static-md-v142-sdk81.cmake
-- Using cached C:/njs/vcpkg/downloads/boostorg-build-boost-1.73.0.tar.gz
-- Using source at C:/njs/vcpkg/buildtrees/boost-build/src/ost-1.73.0-018fb008dd
-- Using cached C:/njs/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Using cached C:/njs/vcpkg/downloads/boost-1.73.0-boostcpp.jam
-- Installing: C:/njs/vcpkg/packages/boost-build_x86-windows-static-md-v142-sdk81/share/boost-build/copyright
-- Installing: C:/njs/vcpkg/packages/boost-build_x86-windows-static-md-v142-sdk81/tools/boost-build/boostcpp.jam
-- Bootstrapping...
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-build[core]:x86-windows-static-md-v142-sdk81... done
Installing package boost-build[core]:x86-windows-static-md-v142-sdk81...
Installing package boost-build[core]:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-build:x86-windows-static-md-v142-sdk81: 30.9 s

Total elapsed time: 30.94 s

vcpkg install of the 2nd library originally reported as outdated in the OP boost-context, is causing a cascade of installs of other boost libraries and is still ongoing as I type this. So far no errors.

diablodale

comment created time in 2 days

issue openedmicrosoft/vcpkg

CMake Error at scripts/ports.cmake:14 (message) Your vcpkg executable is outdated

After running: git pull, vcpkg update, vcpkg upgrade, I received the error

...
Purging package protobuf:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package protobuf:x64-windows-static-md-v142-sdk10b17134: 196.9 ms
Starting package 315/628: boost-build:x86-windows-static-md-v142-sdk10b17134
Building package boost-build[core]:x86-windows-static-md-v142-sdk10b17134...
-- Using community triplet x86-windows-static-md-v142-sdk10b17134. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: C:\njs\vcpkg\triplets\community\x86-windows-static-md-v142-sdk10b17134.cmake
CMake Error at scripts/ports.cmake:14 (message):
          Your vcpkg executable is outdated and is not compatible with the current CMake scripts.
          Please re-build vcpkg by running bootstrap-vcpkg.

Error: Building package boost-build:x86-windows-static-md-v142-sdk10b17134 failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: boost-build:x86-windows-static-md-v142-sdk10b17134
  Vcpkg version: 2020.02.04-nohash-external

Additionally, attach any relevant sections from the log files above.

Maybe 🤔 related to issue #11784

Setup

  • Microsoft Windows [Version 10.0.19041.329]
  • Visual Studio Community 16.6.3
  • Vcpkg package management program version 2020.02.04-nohash-external

Repro

Somewhat difficult as the previous state has been lost, so here is what I can see via copy/paste from my cmd prompt buffer.

git pull did this

remote: Enumerating objects: 26, done.
remote: Counting objects: 100% (26/26), done.
remote: Total 38 (delta 26), reused 26 (delta 26), pack-reused 12
Unpacking objects: 100% (38/38), 23.58 KiB | 55.00 KiB/s, done.
From https://github.com/Microsoft/vcpkg
   5a9d8011f..9ddf284ec  master     -> origin/master
Updating 3c34afc1c..9ddf284ec
Updating files: 100% (163/163), done.

vcpkg update reported this

Using local portfile versions. To update the local portfiles, use `git pull`.
The following packages differ from their port versions:
    boost-build:x64-windows-static-md-v142-sdk10b17134 1.73.0 -> 1.73.0-1
    boost-build:x64-windows-static-md-v142-sdk81 1.73.0 -> 1.73.0-1
    boost-build:x86-windows-static-md-v142-sdk10b17134 1.73.0 -> 1.73.0-1
    boost-build:x86-windows-static-md-v142-sdk81 1.73.0 -> 1.73.0-1
    boost-context:x64-windows-static-md-v142-sdk10b17134 1.73.0 -> 1.73.0-1
    boost-context:x64-windows-static-md-v142-sdk81 1.73.0 -> 1.73.0-1
    boost-context:x86-windows-static-md-v142-sdk10b17134 1.73.0 -> 1.73.0-1
    boost-context:x86-windows-static-md-v142-sdk81 1.73.0 -> 1.73.0-1
    boost-locale:x64-windows-static-md-v142-sdk10b17134 1.73.0 -> 1.73.0-1
    boost-locale:x64-windows-static-md-v142-sdk81 1.73.0 -> 1.73.0-1
    boost-locale:x86-windows-static-md-v142-sdk10b17134 1.73.0 -> 1.73.0-1
    boost-locale:x86-windows-static-md-v142-sdk81 1.73.0 -> 1.73.0-1
    boost-modular-build-helper:x64-windows-static-md-v142-sdk10b17134 1.73.0 -> 1.73.0-1
    boost-modular-build-helper:x64-windows-static-md-v142-sdk81 1.73.0 -> 1.73.0-1
    boost-modular-build-helper:x86-windows-static-md-v142-sdk10b17134 1.73.0 -> 1.73.0-1
    boost-modular-build-helper:x86-windows-static-md-v142-sdk81 1.73.0 -> 1.73.0-1
    cpprestsdk:x64-windows-static-md-v142-sdk10b17134 2.10.16 -> 2.10.16-3
    cpprestsdk:x64-windows-static-md-v142-sdk81 2.10.16 -> 2.10.16-3
    cpprestsdk:x86-windows-static-md-v142-sdk10b17134 2.10.16 -> 2.10.16-3
    cpprestsdk:x86-windows-static-md-v142-sdk81 2.10.16 -> 2.10.16-3
    hdf5:x64-windows-static-md-v142-sdk10b17134 1.10.5-12 -> 1.12.0
    hdf5:x86-windows-static-md-v142-sdk10b17134 1.10.5-12 -> 1.12.0
    opencv4:x64-windows-static-md-v142-sdk10b17134 4.1.1-5 -> 4.1.1-6
    opencv4:x86-windows-static-md-v142-sdk10b17134 4.1.1-5 -> 4.1.1-6
    openssl:x64-windows-static-md-v142-sdk10b17134 1.1.1d -> 1.1.1g
    openssl:x64-windows-static-md-v142-sdk81 1.1.1d -> 1.1.1g
    openssl:x86-windows-static-md-v142-sdk10b17134 1.1.1d -> 1.1.1g
    openssl:x86-windows-static-md-v142-sdk81 1.1.1d -> 1.1.1g
    openssl-windows:x64-windows-static-md-v142-sdk10b17134 1.1.1d-2 -> 1.1.1g
    openssl-windows:x64-windows-static-md-v142-sdk81 1.1.1d-2 -> 1.1.1g
    openssl-windows:x86-windows-static-md-v142-sdk10b17134 1.1.1d-2 -> 1.1.1g
    openssl-windows:x86-windows-static-md-v142-sdk81 1.1.1d-2 -> 1.1.1g
    protobuf:x64-windows-static-md-v142-sdk10b17134 3.12.0 -> 3.12.0-2
    protobuf:x86-windows-static-md-v142-sdk10b17134 3.12.0 -> 3.12.0-2
    python3:x64-windows-static-md-v142-sdk10b17134 3.7.3-3 -> 3.8.3
    python3:x64-windows-static-md-v142-sdk81 3.7.3-3 -> 3.8.3
    python3:x86-windows-static-md-v142-sdk10b17134 3.7.3-3 -> 3.8.3
    python3:x86-windows-static-md-v142-sdk81 3.7.3-3 -> 3.8.3

To update these packages and all dependencies, run
    .\vcpkg upgrade

To only remove outdated packages, run
    .\vcpkg remove --outdated

Then vcpkg upgrade --no-dry-run resulted in the actual failure...

Actual Failure

vcpkg upgrade --no-dry-run did this, purged ~300 packages, and failed at the first (re)build. Unfortunately, this results in lost of state of packages and now the need to manually install all those listed above. Here is what was seen...

<details> <summary>Click to 👀 see vcpkg running and error at end</summary>

C:\njs\vcpkg>vcpkg upgrade --no-dry-run
The following packages will be rebuilt:
  * boost[core]:x86-windows-static-md-v142-sdk10b17134
  * boost[core]:x86-windows-static-md-v142-sdk81
  * boost[core]:x64-windows-static-md-v142-sdk81
  * boost[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-accumulators[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-accumulators[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-accumulators[core]:x86-windows-static-md-v142-sdk81
  * boost-accumulators[core]:x64-windows-static-md-v142-sdk81
  * boost-algorithm[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-algorithm[core]:x64-windows-static-md-v142-sdk81
  * boost-algorithm[core]:x86-windows-static-md-v142-sdk81
  * boost-algorithm[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-asio[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-asio[core]:x64-windows-static-md-v142-sdk81
  * boost-asio[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-asio[core]:x86-windows-static-md-v142-sdk81
  * boost-assign[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-assign[core]:x64-windows-static-md-v142-sdk81
  * boost-assign[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-assign[core]:x86-windows-static-md-v142-sdk81
  * boost-atomic[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-atomic[core]:x86-windows-static-md-v142-sdk81
  * boost-atomic[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-atomic[core]:x64-windows-static-md-v142-sdk81
  * boost-beast[core]:x86-windows-static-md-v142-sdk81
  * boost-beast[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-beast[core]:x64-windows-static-md-v142-sdk81
  * boost-beast[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-bimap[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-bimap[core]:x64-windows-static-md-v142-sdk81
  * boost-bimap[core]:x86-windows-static-md-v142-sdk81
  * boost-bimap[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-build[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-build[core]:x86-windows-static-md-v142-sdk81
  * boost-build[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-build[core]:x64-windows-static-md-v142-sdk81
  * boost-chrono[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-chrono[core]:x86-windows-static-md-v142-sdk81
  * boost-chrono[core]:x64-windows-static-md-v142-sdk81
  * boost-chrono[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-compute[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-compute[core]:x64-windows-static-md-v142-sdk81
  * boost-compute[core]:x86-windows-static-md-v142-sdk81
  * boost-compute[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-container[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-container[core]:x86-windows-static-md-v142-sdk81
  * boost-container[core]:x64-windows-static-md-v142-sdk81
  * boost-container[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-context[core]:x86-windows-static-md-v142-sdk81
  * boost-context[core]:x64-windows-static-md-v142-sdk81
  * boost-context[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-context[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-contract[core]:x86-windows-static-md-v142-sdk81
  * boost-contract[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-contract[core]:x64-windows-static-md-v142-sdk81
  * boost-contract[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-convert[core]:x86-windows-static-md-v142-sdk81
  * boost-convert[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-convert[core]:x64-windows-static-md-v142-sdk81
  * boost-convert[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-coroutine[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-coroutine[core]:x64-windows-static-md-v142-sdk81
  * boost-coroutine[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-coroutine[core]:x86-windows-static-md-v142-sdk81
  * boost-coroutine2[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-coroutine2[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-coroutine2[core]:x64-windows-static-md-v142-sdk81
  * boost-coroutine2[core]:x86-windows-static-md-v142-sdk81
  * boost-date-time[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-date-time[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-date-time[core]:x86-windows-static-md-v142-sdk81
  * boost-date-time[core]:x64-windows-static-md-v142-sdk81
  * boost-dll[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-dll[core]:x64-windows-static-md-v142-sdk81
  * boost-dll[core]:x86-windows-static-md-v142-sdk81
  * boost-dll[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-exception[core]:x86-windows-static-md-v142-sdk81
  * boost-exception[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-exception[core]:x64-windows-static-md-v142-sdk81
  * boost-exception[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-fiber[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-fiber[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-fiber[core]:x64-windows-static-md-v142-sdk81
  * boost-fiber[core]:x86-windows-static-md-v142-sdk81
  * boost-filesystem[core]:x64-windows-static-md-v142-sdk81
  * boost-filesystem[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-filesystem[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-filesystem[core]:x86-windows-static-md-v142-sdk81
  * boost-flyweight[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-flyweight[core]:x64-windows-static-md-v142-sdk81
  * boost-flyweight[core]:x86-windows-static-md-v142-sdk81
  * boost-flyweight[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-foreach[core]:x86-windows-static-md-v142-sdk81
  * boost-foreach[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-foreach[core]:x64-windows-static-md-v142-sdk81
  * boost-foreach[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-geometry[core]:x86-windows-static-md-v142-sdk81
  * boost-geometry[core]:x64-windows-static-md-v142-sdk81
  * boost-geometry[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-geometry[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-gil[core]:x64-windows-static-md-v142-sdk81
  * boost-gil[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-gil[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-gil[core]:x86-windows-static-md-v142-sdk81
  * boost-graph[core]:x64-windows-static-md-v142-sdk81
  * boost-graph[core]:x86-windows-static-md-v142-sdk81
  * boost-graph[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-graph[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-graph-parallel[core]:x64-windows-static-md-v142-sdk81
  * boost-graph-parallel[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-graph-parallel[core]:x86-windows-static-md-v142-sdk81
  * boost-graph-parallel[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-histogram[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-histogram[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-histogram[core]:x86-windows-static-md-v142-sdk81
  * boost-histogram[core]:x64-windows-static-md-v142-sdk81
  * boost-icl[core]:x64-windows-static-md-v142-sdk81
  * boost-icl[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-icl[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-icl[core]:x86-windows-static-md-v142-sdk81
  * boost-interprocess[core]:x86-windows-static-md-v142-sdk81
  * boost-interprocess[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-interprocess[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-interprocess[core]:x64-windows-static-md-v142-sdk81
  * boost-iostreams[core]:x64-windows-static-md-v142-sdk81
  * boost-iostreams[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-iostreams[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-iostreams[core]:x86-windows-static-md-v142-sdk81
  * boost-lexical-cast[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-lexical-cast[core]:x64-windows-static-md-v142-sdk81
  * boost-lexical-cast[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-lexical-cast[core]:x86-windows-static-md-v142-sdk81
  * boost-locale[core]:x64-windows-static-md-v142-sdk81
  * boost-locale[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-locale[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-locale[core]:x86-windows-static-md-v142-sdk81
  * boost-lockfree[core]:x64-windows-static-md-v142-sdk81
  * boost-lockfree[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-lockfree[core]:x86-windows-static-md-v142-sdk81
  * boost-lockfree[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-log[core]:x86-windows-static-md-v142-sdk81
  * boost-log[core]:x64-windows-static-md-v142-sdk81
  * boost-log[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-log[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-math[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-math[core]:x86-windows-static-md-v142-sdk81
  * boost-math[core]:x64-windows-static-md-v142-sdk81
  * boost-math[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-modular-build-helper[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-modular-build-helper[core]:x86-windows-static-md-v142-sdk81
  * boost-modular-build-helper[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-modular-build-helper[core]:x64-windows-static-md-v142-sdk81
  * boost-msm[core]:x64-windows-static-md-v142-sdk81
  * boost-msm[core]:x86-windows-static-md-v142-sdk81
  * boost-msm[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-msm[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-multi-index[core]:x86-windows-static-md-v142-sdk81
  * boost-multi-index[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-multi-index[core]:x64-windows-static-md-v142-sdk81
  * boost-multi-index[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-multiprecision[core]:x86-windows-static-md-v142-sdk81
  * boost-multiprecision[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-multiprecision[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-multiprecision[core]:x64-windows-static-md-v142-sdk81
  * boost-nowide[core]:x64-windows-static-md-v142-sdk81
  * boost-nowide[core]:x86-windows-static-md-v142-sdk81
  * boost-nowide[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-nowide[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-odeint[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-odeint[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-odeint[core]:x64-windows-static-md-v142-sdk81
  * boost-odeint[core]:x86-windows-static-md-v142-sdk81
  * boost-parameter-python[core]:x64-windows-static-md-v142-sdk81
  * boost-parameter-python[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-parameter-python[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-parameter-python[core]:x86-windows-static-md-v142-sdk81
  * boost-phoenix[core]:x86-windows-static-md-v142-sdk81
  * boost-phoenix[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-phoenix[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-phoenix[core]:x64-windows-static-md-v142-sdk81
  * boost-poly-collection[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-poly-collection[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-poly-collection[core]:x86-windows-static-md-v142-sdk81
  * boost-poly-collection[core]:x64-windows-static-md-v142-sdk81
  * boost-process[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-process[core]:x64-windows-static-md-v142-sdk81
  * boost-process[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-process[core]:x86-windows-static-md-v142-sdk81
  * boost-program-options[core]:x64-windows-static-md-v142-sdk81
  * boost-program-options[core]:x86-windows-static-md-v142-sdk81
  * boost-program-options[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-program-options[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-property-map[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-property-map[core]:x86-windows-static-md-v142-sdk81
  * boost-property-map[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-property-map[core]:x64-windows-static-md-v142-sdk81
  * boost-property-tree[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-property-tree[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-property-tree[core]:x64-windows-static-md-v142-sdk81
  * boost-property-tree[core]:x86-windows-static-md-v142-sdk81
  * boost-proto[core]:x64-windows-static-md-v142-sdk81
  * boost-proto[core]:x86-windows-static-md-v142-sdk81
  * boost-proto[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-proto[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-ptr-container[core]:x64-windows-static-md-v142-sdk81
  * boost-ptr-container[core]:x86-windows-static-md-v142-sdk81
  * boost-ptr-container[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-ptr-container[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-python[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-python[core]:x64-windows-static-md-v142-sdk81
  * boost-python[core]:x86-windows-static-md-v142-sdk81
  * boost-python[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-qvm[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-qvm[core]:x64-windows-static-md-v142-sdk81
  * boost-qvm[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-qvm[core]:x86-windows-static-md-v142-sdk81
  * boost-random[core]:x86-windows-static-md-v142-sdk81
  * boost-random[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-random[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-random[core]:x64-windows-static-md-v142-sdk81
  * boost-range[core]:x64-windows-static-md-v142-sdk81
  * boost-range[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-range[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-range[core]:x86-windows-static-md-v142-sdk81
  * boost-regex[core]:x64-windows-static-md-v142-sdk81
  * boost-regex[core]:x86-windows-static-md-v142-sdk81
  * boost-regex[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-regex[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-serialization[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-serialization[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-serialization[core]:x64-windows-static-md-v142-sdk81
  * boost-serialization[core]:x86-windows-static-md-v142-sdk81
  * boost-sort[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-sort[core]:x86-windows-static-md-v142-sdk81
  * boost-sort[core]:x64-windows-static-md-v142-sdk81
  * boost-sort[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-spirit[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-spirit[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-spirit[core]:x86-windows-static-md-v142-sdk81
  * boost-spirit[core]:x64-windows-static-md-v142-sdk81
  * boost-stacktrace[core]:x86-windows-static-md-v142-sdk81
  * boost-stacktrace[core]:x64-windows-static-md-v142-sdk81
  * boost-stacktrace[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-stacktrace[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-statechart[core]:x86-windows-static-md-v142-sdk81
  * boost-statechart[core]:x64-windows-static-md-v142-sdk81
  * boost-statechart[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-statechart[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-system[core]:x64-windows-static-md-v142-sdk81
  * boost-system[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-system[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-system[core]:x86-windows-static-md-v142-sdk81
  * boost-test[core]:x64-windows-static-md-v142-sdk81
  * boost-test[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-test[core]:x86-windows-static-md-v142-sdk81
  * boost-test[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-thread[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-thread[core]:x86-windows-static-md-v142-sdk81
  * boost-thread[core]:x64-windows-static-md-v142-sdk81
  * boost-thread[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-timer[core]:x86-windows-static-md-v142-sdk81
  * boost-timer[core]:x64-windows-static-md-v142-sdk81
  * boost-timer[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-timer[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-type-erasure[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-type-erasure[core]:x64-windows-static-md-v142-sdk81
  * boost-type-erasure[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-type-erasure[core]:x86-windows-static-md-v142-sdk81
  * boost-ublas[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-ublas[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-ublas[core]:x86-windows-static-md-v142-sdk81
  * boost-ublas[core]:x64-windows-static-md-v142-sdk81
  * boost-units[core]:x86-windows-static-md-v142-sdk81
  * boost-units[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-units[core]:x64-windows-static-md-v142-sdk81
  * boost-units[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-unordered[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-unordered[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-unordered[core]:x86-windows-static-md-v142-sdk81
  * boost-unordered[core]:x64-windows-static-md-v142-sdk81
  * boost-uuid[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-uuid[core]:x86-windows-static-md-v142-sdk81
  * boost-uuid[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-uuid[core]:x64-windows-static-md-v142-sdk81
  * boost-wave[core]:x64-windows-static-md-v142-sdk81
  * boost-wave[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-wave[core]:x86-windows-static-md-v142-sdk81
  * boost-wave[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-xpressive[core]:x86-windows-static-md-v142-sdk10b17134
  * boost-xpressive[core]:x64-windows-static-md-v142-sdk10b17134
  * boost-xpressive[core]:x64-windows-static-md-v142-sdk81
  * boost-xpressive[core]:x86-windows-static-md-v142-sdk81
  * cpprestsdk[brotli,compression,core,default-features]:x64-windows-static-md-v142-sdk81
  * cpprestsdk[brotli,compression,core,default-features]:x64-windows-static-md-v142-sdk10b17134
  * cpprestsdk[brotli,compression,core,default-features]:x86-windows-static-md-v142-sdk10b17134
  * cpprestsdk[brotli,compression,core,default-features]:x86-windows-static-md-v142-sdk81
  * hdf5[core,szip,zlib]:x64-windows-static-md-v142-sdk10b17134
  * hdf5[core,szip,zlib]:x86-windows-static-md-v142-sdk10b17134
  * opencv4[contrib,core,cuda,dnn,eigen,ipp,jpeg,opengl,png,sfm,tiff,webp]:x64-windows-static-md-v142-sdk10b17134
  * opencv4[contrib,core,dnn,eigen,ipp,jpeg,opengl,png,sfm,tiff,webp]:x86-windows-static-md-v142-sdk10b17134
  * openssl[core]:x64-windows-static-md-v142-sdk10b17134
  * openssl[core]:x64-windows-static-md-v142-sdk81
  * openssl[core]:x86-windows-static-md-v142-sdk81
  * openssl[core]:x86-windows-static-md-v142-sdk10b17134
  * openssl-windows[core]:x64-windows-static-md-v142-sdk10b17134
  * openssl-windows[core]:x64-windows-static-md-v142-sdk81
  * openssl-windows[core]:x86-windows-static-md-v142-sdk81
  * openssl-windows[core]:x86-windows-static-md-v142-sdk10b17134
  * protobuf[core]:x86-windows-static-md-v142-sdk10b17134
  * protobuf[core]:x64-windows-static-md-v142-sdk10b17134
  * python3[core]:x64-windows-static-md-v142-sdk81
  * python3[core]:x64-windows-static-md-v142-sdk10b17134
  * python3[core]:x86-windows-static-md-v142-sdk10b17134
  * python3[core]:x86-windows-static-md-v142-sdk81
Additional packages (*) will be modified to complete this operation.
Starting package 1/628: boost:x86-windows-static-md-v142-sdk10b17134
Removing package boost:x86-windows-static-md-v142-sdk10b17134...
Removing package boost:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost:x86-windows-static-md-v142-sdk10b17134...
Purging package boost:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost:x86-windows-static-md-v142-sdk10b17134: 38.64 ms
Starting package 2/628: boost-accumulators:x86-windows-static-md-v142-sdk10b17134
Removing package boost-accumulators:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-accumulators:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-accumulators:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-accumulators:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-accumulators:x86-windows-static-md-v142-sdk10b17134: 149.1 ms
Starting package 3/628: boost-ublas:x86-windows-static-md-v142-sdk10b17134
Removing package boost-ublas:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-ublas:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-ublas:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-ublas:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-ublas:x86-windows-static-md-v142-sdk10b17134: 121.3 ms
Starting package 4/628: boost-odeint:x86-windows-static-md-v142-sdk10b17134
Removing package boost-odeint:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-odeint:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-odeint:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-odeint:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-odeint:x86-windows-static-md-v142-sdk10b17134: 248.5 ms
Starting package 5/628: boost-compute:x86-windows-static-md-v142-sdk10b17134
Removing package boost-compute:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-compute:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-compute:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-compute:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-compute:x86-windows-static-md-v142-sdk10b17134: 371 ms
Starting package 6/628: boost-beast:x86-windows-static-md-v142-sdk10b17134
Removing package boost-beast:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-beast:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-beast:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-beast:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-beast:x86-windows-static-md-v142-sdk10b17134: 377.7 ms
Starting package 7/628: boost-log:x86-windows-static-md-v142-sdk10b17134
Removing package boost-log:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-log:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-log:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-log:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-log:x86-windows-static-md-v142-sdk10b17134: 327.5 ms
Starting package 8/628: boost-process:x86-windows-static-md-v142-sdk10b17134
Removing package boost-process:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-process:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-process:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-process:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-process:x86-windows-static-md-v142-sdk10b17134: 157.5 ms
Starting package 9/628: boost-asio:x86-windows-static-md-v142-sdk10b17134
Removing package boost-asio:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-asio:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-asio:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-asio:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-asio:x86-windows-static-md-v142-sdk10b17134: 544 ms
Starting package 10/628: boost-statechart:x86-windows-static-md-v142-sdk10b17134
Removing package boost-statechart:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-statechart:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-statechart:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-statechart:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-statechart:x86-windows-static-md-v142-sdk10b17134: 73.7 ms
Starting package 11/628: boost-coroutine2:x86-windows-static-md-v142-sdk10b17134
Removing package boost-coroutine2:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-coroutine2:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-coroutine2:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-coroutine2:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-coroutine2:x86-windows-static-md-v142-sdk10b17134: 59.68 ms
Starting package 12/628: boost-coroutine:x86-windows-static-md-v142-sdk10b17134
Removing package boost-coroutine:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-coroutine:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-coroutine:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-coroutine:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-coroutine:x86-windows-static-md-v142-sdk10b17134: 81.74 ms
Starting package 13/628: boost-fiber:x86-windows-static-md-v142-sdk10b17134
Removing package boost-fiber:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-fiber:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-fiber:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-fiber:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-fiber:x86-windows-static-md-v142-sdk10b17134: 116.5 ms
Starting package 14/628: boost-context:x86-windows-static-md-v142-sdk10b17134
Removing package boost-context:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-context:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-context:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-context:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-context:x86-windows-static-md-v142-sdk10b17134: 77.53 ms
Starting package 15/628: boost-graph-parallel:x86-windows-static-md-v142-sdk10b17134
Removing package boost-graph-parallel:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-graph-parallel:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-graph-parallel:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-graph-parallel:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-graph-parallel:x86-windows-static-md-v142-sdk10b17134: 118.6 ms
Starting package 16/628: boost-parameter-python:x86-windows-static-md-v142-sdk10b17134
Removing package boost-parameter-python:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-parameter-python:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-parameter-python:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-parameter-python:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-parameter-python:x86-windows-static-md-v142-sdk10b17134: 49.15 ms
Starting package 17/628: boost-python:x86-windows-static-md-v142-sdk10b17134
Removing package boost-python:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-python:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-python:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-python:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-python:x86-windows-static-md-v142-sdk10b17134: 299.4 ms
Starting package 18/628: boost-graph:x86-windows-static-md-v142-sdk10b17134
Removing package boost-graph:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-graph:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-graph:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-graph:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-graph:x86-windows-static-md-v142-sdk10b17134: 262.8 ms
Starting package 19/628: boost-xpressive:x86-windows-static-md-v142-sdk10b17134
Removing package boost-xpressive:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-xpressive:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-xpressive:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-xpressive:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-xpressive:x86-windows-static-md-v142-sdk10b17134: 168.7 ms
Starting package 20/628: boost-convert:x86-windows-static-md-v142-sdk10b17134
Removing package boost-convert:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-convert:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-convert:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-convert:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-convert:x86-windows-static-md-v142-sdk10b17134: 57.5 ms
Starting package 21/628: boost-uuid:x86-windows-static-md-v142-sdk10b17134
Removing package boost-uuid:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-uuid:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-uuid:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-uuid:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-uuid:x86-windows-static-md-v142-sdk10b17134: 62.08 ms
Starting package 22/628: boost-flyweight:x86-windows-static-md-v142-sdk10b17134
Removing package boost-flyweight:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-flyweight:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-flyweight:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-flyweight:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-flyweight:x86-windows-static-md-v142-sdk10b17134: 76.67 ms
Starting package 23/628: boost-bimap:x86-windows-static-md-v142-sdk10b17134
Removing package boost-bimap:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-bimap:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-bimap:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-bimap:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-bimap:x86-windows-static-md-v142-sdk10b17134: 146.1 ms
Starting package 24/628: boost-histogram:x86-windows-static-md-v142-sdk10b17134
Removing package boost-histogram:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-histogram:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-histogram:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-histogram:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-histogram:x86-windows-static-md-v142-sdk10b17134: 126 ms
Starting package 25/628: boost-geometry:x86-windows-static-md-v142-sdk10b17134
Removing package boost-geometry:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-geometry:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-geometry:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-geometry:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-geometry:x86-windows-static-md-v142-sdk10b17134: 1.1 s
Starting package 26/628: boost-property-map:x86-windows-static-md-v142-sdk10b17134
Removing package boost-property-map:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-property-map:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-property-map:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-property-map:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-property-map:x86-windows-static-md-v142-sdk10b17134: 62.78 ms
Starting package 27/628: boost-msm:x86-windows-static-md-v142-sdk10b17134
Removing package boost-msm:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-msm:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-msm:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-msm:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-msm:x86-windows-static-md-v142-sdk10b17134: 95.63 ms
Starting package 28/628: boost-property-tree:x86-windows-static-md-v142-sdk10b17134
Removing package boost-property-tree:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-property-tree:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-property-tree:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-property-tree:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-property-tree:x86-windows-static-md-v142-sdk10b17134: 84.18 ms
Starting package 29/628: boost-wave:x86-windows-static-md-v142-sdk10b17134
Removing package boost-wave:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-wave:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-wave:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-wave:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-wave:x86-windows-static-md-v142-sdk10b17134: 108.9 ms
Starting package 30/628: boost-multi-index:x86-windows-static-md-v142-sdk10b17134
Removing package boost-multi-index:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-multi-index:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-multi-index:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-multi-index:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-multi-index:x86-windows-static-md-v142-sdk10b17134: 135.5 ms
Starting package 31/628: boost-assign:x86-windows-static-md-v142-sdk10b17134
Removing package boost-assign:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-assign:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-assign:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-assign:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-assign:x86-windows-static-md-v142-sdk10b17134: 60.41 ms
Starting package 32/628: boost-ptr-container:x86-windows-static-md-v142-sdk10b17134
Removing package boost-ptr-container:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-ptr-container:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-ptr-container:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-ptr-container:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-ptr-container:x86-windows-static-md-v142-sdk10b17134: 82.06 ms
Starting package 33/628: boost-sort:x86-windows-static-md-v142-sdk10b17134
Removing package boost-sort:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-sort:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-sort:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-sort:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-sort:x86-windows-static-md-v142-sdk10b17134: 100.2 ms
Starting package 34/628: boost-units:x86-windows-static-md-v142-sdk10b17134
Removing package boost-units:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-units:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-units:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-units:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-units:x86-windows-static-md-v142-sdk10b17134: 385.6 ms
Starting package 35/628: boost-serialization:x86-windows-static-md-v142-sdk10b17134
Removing package boost-serialization:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-serialization:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-serialization:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-serialization:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-serialization:x86-windows-static-md-v142-sdk10b17134: 281.8 ms
Starting package 36/628: boost-dll:x86-windows-static-md-v142-sdk10b17134
Removing package boost-dll:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-dll:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-dll:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-dll:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-dll:x86-windows-static-md-v142-sdk10b17134: 122.9 ms
Starting package 37/628: boost-spirit:x86-windows-static-md-v142-sdk10b17134
Removing package boost-spirit:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-spirit:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-spirit:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-spirit:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-spirit:x86-windows-static-md-v142-sdk10b17134: 1.294 s
Starting package 38/628: boost-locale:x86-windows-static-md-v142-sdk10b17134
Removing package boost-locale:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-locale:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-locale:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-locale:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-locale:x86-windows-static-md-v142-sdk10b17134: 73.84 ms
Starting package 39/628: boost-contract:x86-windows-static-md-v142-sdk10b17134
Removing package boost-contract:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-contract:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-contract:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-contract:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-contract:x86-windows-static-md-v142-sdk10b17134: 105.2 ms
Starting package 40/628: boost-poly-collection:x86-windows-static-md-v142-sdk10b17134
Removing package boost-poly-collection:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-poly-collection:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-poly-collection:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-poly-collection:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-poly-collection:x86-windows-static-md-v142-sdk10b17134: 81.29 ms
Starting package 41/628: boost-type-erasure:x86-windows-static-md-v142-sdk10b17134
Removing package boost-type-erasure:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-type-erasure:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-type-erasure:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-type-erasure:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-type-erasure:x86-windows-static-md-v142-sdk10b17134: 97.34 ms
Starting package 42/628: boost-thread:x86-windows-static-md-v142-sdk10b17134
Removing package boost-thread:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-thread:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-thread:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-thread:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-thread:x86-windows-static-md-v142-sdk10b17134: 238.1 ms
Starting package 43/628: boost-timer:x86-windows-static-md-v142-sdk10b17134
Removing package boost-timer:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-timer:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-timer:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-timer:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-timer:x86-windows-static-md-v142-sdk10b17134: 46.63 ms
Starting package 44/628: boost-chrono:x86-windows-static-md-v142-sdk10b17134
Removing package boost-chrono:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-chrono:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-chrono:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-chrono:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-chrono:x86-windows-static-md-v142-sdk10b17134: 102.4 ms
Starting package 45/628: boost:x64-windows-static-md-v142-sdk81
Removing package boost:x64-windows-static-md-v142-sdk81...
Removing package boost:x64-windows-static-md-v142-sdk81... done
Purging package boost:x64-windows-static-md-v142-sdk81...
Purging package boost:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost:x64-windows-static-md-v142-sdk81: 40.4 ms
Starting package 46/628: boost-graph-parallel:x64-windows-static-md-v142-sdk81
Removing package boost-graph-parallel:x64-windows-static-md-v142-sdk81...
Removing package boost-graph-parallel:x64-windows-static-md-v142-sdk81... done
Purging package boost-graph-parallel:x64-windows-static-md-v142-sdk81...
Purging package boost-graph-parallel:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-graph-parallel:x64-windows-static-md-v142-sdk81: 106.4 ms
Starting package 47/628: boost-parameter-python:x64-windows-static-md-v142-sdk81
Removing package boost-parameter-python:x64-windows-static-md-v142-sdk81...
Removing package boost-parameter-python:x64-windows-static-md-v142-sdk81... done
Purging package boost-parameter-python:x64-windows-static-md-v142-sdk81...
Purging package boost-parameter-python:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-parameter-python:x64-windows-static-md-v142-sdk81: 46.54 ms
Starting package 48/628: boost-python:x64-windows-static-md-v142-sdk81
Removing package boost-python:x64-windows-static-md-v142-sdk81...
Removing package boost-python:x64-windows-static-md-v142-sdk81... done
Purging package boost-python:x64-windows-static-md-v142-sdk81...
Purging package boost-python:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-python:x64-windows-static-md-v142-sdk81: 298.3 ms
Starting package 49/628: boost-graph:x64-windows-static-md-v142-sdk81
Removing package boost-graph:x64-windows-static-md-v142-sdk81...
Removing package boost-graph:x64-windows-static-md-v142-sdk81... done
Purging package boost-graph:x64-windows-static-md-v142-sdk81...
Purging package boost-graph:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-graph:x64-windows-static-md-v142-sdk81: 271.3 ms
Starting package 50/628: boost-log:x64-windows-static-md-v142-sdk81
Removing package boost-log:x64-windows-static-md-v142-sdk81...
Removing package boost-log:x64-windows-static-md-v142-sdk81... done
Purging package boost-log:x64-windows-static-md-v142-sdk81...
Purging package boost-log:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-log:x64-windows-static-md-v142-sdk81: 319.7 ms
Starting package 51/628: boost-xpressive:x64-windows-static-md-v142-sdk81
Removing package boost-xpressive:x64-windows-static-md-v142-sdk81...
Removing package boost-xpressive:x64-windows-static-md-v142-sdk81... done
Purging package boost-xpressive:x64-windows-static-md-v142-sdk81...
Purging package boost-xpressive:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-xpressive:x64-windows-static-md-v142-sdk81: 170.5 ms
Starting package 52/628: boost-convert:x64-windows-static-md-v142-sdk81
Removing package boost-convert:x64-windows-static-md-v142-sdk81...
Removing package boost-convert:x64-windows-static-md-v142-sdk81... done
Purging package boost-convert:x64-windows-static-md-v142-sdk81...
Purging package boost-convert:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-convert:x64-windows-static-md-v142-sdk81: 58.64 ms
Starting package 53/628: boost-accumulators:x64-windows-static-md-v142-sdk81
Removing package boost-accumulators:x64-windows-static-md-v142-sdk81...
Removing package boost-accumulators:x64-windows-static-md-v142-sdk81... done
Purging package boost-accumulators:x64-windows-static-md-v142-sdk81...
Purging package boost-accumulators:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-accumulators:x64-windows-static-md-v142-sdk81: 152.7 ms
Starting package 54/628: boost-ublas:x64-windows-static-md-v142-sdk81
Removing package boost-ublas:x64-windows-static-md-v142-sdk81...
Removing package boost-ublas:x64-windows-static-md-v142-sdk81... done
Purging package boost-ublas:x64-windows-static-md-v142-sdk81...
Purging package boost-ublas:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-ublas:x64-windows-static-md-v142-sdk81: 117.8 ms
Starting package 55/628: boost-odeint:x64-windows-static-md-v142-sdk81
Removing package boost-odeint:x64-windows-static-md-v142-sdk81...
Removing package boost-odeint:x64-windows-static-md-v142-sdk81... done
Purging package boost-odeint:x64-windows-static-md-v142-sdk81...
Purging package boost-odeint:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-odeint:x64-windows-static-md-v142-sdk81: 261.3 ms
Starting package 56/628: boost-compute:x64-windows-static-md-v142-sdk81
Removing package boost-compute:x64-windows-static-md-v142-sdk81...
Removing package boost-compute:x64-windows-static-md-v142-sdk81... done
Purging package boost-compute:x64-windows-static-md-v142-sdk81...
Purging package boost-compute:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-compute:x64-windows-static-md-v142-sdk81: 394.5 ms
Starting package 57/628: boost-uuid:x64-windows-static-md-v142-sdk81
Removing package boost-uuid:x64-windows-static-md-v142-sdk81...
Removing package boost-uuid:x64-windows-static-md-v142-sdk81... done
Purging package boost-uuid:x64-windows-static-md-v142-sdk81...
Purging package boost-uuid:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-uuid:x64-windows-static-md-v142-sdk81: 64.95 ms
Starting package 58/628: boost-flyweight:x64-windows-static-md-v142-sdk81
Removing package boost-flyweight:x64-windows-static-md-v142-sdk81...
Removing package boost-flyweight:x64-windows-static-md-v142-sdk81... done
Purging package boost-flyweight:x64-windows-static-md-v142-sdk81...
Purging package boost-flyweight:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-flyweight:x64-windows-static-md-v142-sdk81: 79.71 ms
Starting package 59/628: boost-bimap:x64-windows-static-md-v142-sdk81
Removing package boost-bimap:x64-windows-static-md-v142-sdk81...
Removing package boost-bimap:x64-windows-static-md-v142-sdk81... done
Purging package boost-bimap:x64-windows-static-md-v142-sdk81...
Purging package boost-bimap:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-bimap:x64-windows-static-md-v142-sdk81: 155.7 ms
Starting package 60/628: boost-histogram:x64-windows-static-md-v142-sdk81
Removing package boost-histogram:x64-windows-static-md-v142-sdk81...
Removing package boost-histogram:x64-windows-static-md-v142-sdk81... done
Purging package boost-histogram:x64-windows-static-md-v142-sdk81...
Purging package boost-histogram:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-histogram:x64-windows-static-md-v142-sdk81: 118.7 ms
Starting package 61/628: boost-geometry:x64-windows-static-md-v142-sdk81
Removing package boost-geometry:x64-windows-static-md-v142-sdk81...
Removing package boost-geometry:x64-windows-static-md-v142-sdk81... done
Purging package boost-geometry:x64-windows-static-md-v142-sdk81...
Purging package boost-geometry:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-geometry:x64-windows-static-md-v142-sdk81: 1.265 s
Starting package 62/628: boost-property-map:x64-windows-static-md-v142-sdk81
Removing package boost-property-map:x64-windows-static-md-v142-sdk81...
Removing package boost-property-map:x64-windows-static-md-v142-sdk81... done
Purging package boost-property-map:x64-windows-static-md-v142-sdk81...
Purging package boost-property-map:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-property-map:x64-windows-static-md-v142-sdk81: 63.97 ms
Starting package 63/628: boost-msm:x64-windows-static-md-v142-sdk81
Removing package boost-msm:x64-windows-static-md-v142-sdk81...
Removing package boost-msm:x64-windows-static-md-v142-sdk81... done
Purging package boost-msm:x64-windows-static-md-v142-sdk81...
Purging package boost-msm:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-msm:x64-windows-static-md-v142-sdk81: 108.9 ms
Starting package 64/628: boost-property-tree:x64-windows-static-md-v142-sdk81
Removing package boost-property-tree:x64-windows-static-md-v142-sdk81...
Removing package boost-property-tree:x64-windows-static-md-v142-sdk81... done
Purging package boost-property-tree:x64-windows-static-md-v142-sdk81...
Purging package boost-property-tree:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-property-tree:x64-windows-static-md-v142-sdk81: 75.54 ms
Starting package 65/628: boost-wave:x64-windows-static-md-v142-sdk81
Removing package boost-wave:x64-windows-static-md-v142-sdk81...
Removing package boost-wave:x64-windows-static-md-v142-sdk81... done
Purging package boost-wave:x64-windows-static-md-v142-sdk81...
Purging package boost-wave:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-wave:x64-windows-static-md-v142-sdk81: 122.7 ms
Starting package 66/628: boost-multi-index:x64-windows-static-md-v142-sdk81
Removing package boost-multi-index:x64-windows-static-md-v142-sdk81...
Removing package boost-multi-index:x64-windows-static-md-v142-sdk81... done
Purging package boost-multi-index:x64-windows-static-md-v142-sdk81...
Purging package boost-multi-index:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-multi-index:x64-windows-static-md-v142-sdk81: 142.2 ms
Starting package 67/628: boost-assign:x64-windows-static-md-v142-sdk81
Removing package boost-assign:x64-windows-static-md-v142-sdk81...
Removing package boost-assign:x64-windows-static-md-v142-sdk81... done
Purging package boost-assign:x64-windows-static-md-v142-sdk81...
Purging package boost-assign:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-assign:x64-windows-static-md-v142-sdk81: 56.08 ms
Starting package 68/628: boost-ptr-container:x64-windows-static-md-v142-sdk81
Removing package boost-ptr-container:x64-windows-static-md-v142-sdk81...
Removing package boost-ptr-container:x64-windows-static-md-v142-sdk81... done
Purging package boost-ptr-container:x64-windows-static-md-v142-sdk81...
Purging package boost-ptr-container:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-ptr-container:x64-windows-static-md-v142-sdk81: 85.07 ms
Starting package 69/628: boost-sort:x64-windows-static-md-v142-sdk81
Removing package boost-sort:x64-windows-static-md-v142-sdk81...
Removing package boost-sort:x64-windows-static-md-v142-sdk81... done
Purging package boost-sort:x64-windows-static-md-v142-sdk81...
Purging package boost-sort:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-sort:x64-windows-static-md-v142-sdk81: 112.5 ms
Starting package 70/628: boost-units:x64-windows-static-md-v142-sdk81
Removing package boost-units:x64-windows-static-md-v142-sdk81...
Removing package boost-units:x64-windows-static-md-v142-sdk81... done
Purging package boost-units:x64-windows-static-md-v142-sdk81...
Purging package boost-units:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-units:x64-windows-static-md-v142-sdk81: 399.8 ms
Starting package 71/628: boost-serialization:x64-windows-static-md-v142-sdk81
Removing package boost-serialization:x64-windows-static-md-v142-sdk81...
Removing package boost-serialization:x64-windows-static-md-v142-sdk81... done
Purging package boost-serialization:x64-windows-static-md-v142-sdk81...
Purging package boost-serialization:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-serialization:x64-windows-static-md-v142-sdk81: 283.9 ms
Starting package 72/628: boost-dll:x64-windows-static-md-v142-sdk81
Removing package boost-dll:x64-windows-static-md-v142-sdk81...
Removing package boost-dll:x64-windows-static-md-v142-sdk81... done
Purging package boost-dll:x64-windows-static-md-v142-sdk81...
Purging package boost-dll:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-dll:x64-windows-static-md-v142-sdk81: 74.52 ms
Starting package 73/628: boost-spirit:x64-windows-static-md-v142-sdk81
Removing package boost-spirit:x64-windows-static-md-v142-sdk81...
Removing package boost-spirit:x64-windows-static-md-v142-sdk81... done
Purging package boost-spirit:x64-windows-static-md-v142-sdk81...
Purging package boost-spirit:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-spirit:x64-windows-static-md-v142-sdk81: 1.243 s
Starting package 74/628: boost-iostreams:x64-windows-static-md-v142-sdk81
Removing package boost-iostreams:x64-windows-static-md-v142-sdk81...
Removing package boost-iostreams:x64-windows-static-md-v142-sdk81... done
Purging package boost-iostreams:x64-windows-static-md-v142-sdk81...
Purging package boost-iostreams:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-iostreams:x64-windows-static-md-v142-sdk81: 168.2 ms
Starting package 75/628: boost-beast:x64-windows-static-md-v142-sdk81
Removing package boost-beast:x64-windows-static-md-v142-sdk81...
Removing package boost-beast:x64-windows-static-md-v142-sdk81... done
Purging package boost-beast:x64-windows-static-md-v142-sdk81...
Purging package boost-beast:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-beast:x64-windows-static-md-v142-sdk81: 329.8 ms
Starting package 76/628: boost-process:x64-windows-static-md-v142-sdk81
Removing package boost-process:x64-windows-static-md-v142-sdk81...
Removing package boost-process:x64-windows-static-md-v142-sdk81... done
Purging package boost-process:x64-windows-static-md-v142-sdk81...
Purging package boost-process:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-process:x64-windows-static-md-v142-sdk81: 159.2 ms
Starting package 77/628: boost-asio:x64-windows-static-md-v142-sdk81
Removing package boost-asio:x64-windows-static-md-v142-sdk81...
Removing package boost-asio:x64-windows-static-md-v142-sdk81... done
Purging package boost-asio:x64-windows-static-md-v142-sdk81...
Purging package boost-asio:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-asio:x64-windows-static-md-v142-sdk81: 622.4 ms
Starting package 78/628: boost-statechart:x64-windows-static-md-v142-sdk81
Removing package boost-statechart:x64-windows-static-md-v142-sdk81...
Removing package boost-statechart:x64-windows-static-md-v142-sdk81... done
Purging package boost-statechart:x64-windows-static-md-v142-sdk81...
Purging package boost-statechart:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-statechart:x64-windows-static-md-v142-sdk81: 71.9 ms
Starting package 79/628: boost-coroutine2:x64-windows-static-md-v142-sdk81
Removing package boost-coroutine2:x64-windows-static-md-v142-sdk81...
Removing package boost-coroutine2:x64-windows-static-md-v142-sdk81... done
Purging package boost-coroutine2:x64-windows-static-md-v142-sdk81...
Purging package boost-coroutine2:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-coroutine2:x64-windows-static-md-v142-sdk81: 62.19 ms
Starting package 80/628: boost-coroutine:x64-windows-static-md-v142-sdk81
Removing package boost-coroutine:x64-windows-static-md-v142-sdk81...
Removing package boost-coroutine:x64-windows-static-md-v142-sdk81... done
Purging package boost-coroutine:x64-windows-static-md-v142-sdk81...
Purging package boost-coroutine:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-coroutine:x64-windows-static-md-v142-sdk81: 87.97 ms
Starting package 81/628: boost-fiber:x64-windows-static-md-v142-sdk81
Removing package boost-fiber:x64-windows-static-md-v142-sdk81...
Removing package boost-fiber:x64-windows-static-md-v142-sdk81... done
Purging package boost-fiber:x64-windows-static-md-v142-sdk81...
Purging package boost-fiber:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-fiber:x64-windows-static-md-v142-sdk81: 116.7 ms
Starting package 82/628: boost-context:x64-windows-static-md-v142-sdk81
Removing package boost-context:x64-windows-static-md-v142-sdk81...
Removing package boost-context:x64-windows-static-md-v142-sdk81... done
Purging package boost-context:x64-windows-static-md-v142-sdk81...
Purging package boost-context:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-context:x64-windows-static-md-v142-sdk81: 92.67 ms
Starting package 83/628: boost-locale:x64-windows-static-md-v142-sdk81
Removing package boost-locale:x64-windows-static-md-v142-sdk81...
Removing package boost-locale:x64-windows-static-md-v142-sdk81... done
Purging package boost-locale:x64-windows-static-md-v142-sdk81...
Purging package boost-locale:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-locale:x64-windows-static-md-v142-sdk81: 77.91 ms
Starting package 84/628: boost-contract:x64-windows-static-md-v142-sdk81
Removing package boost-contract:x64-windows-static-md-v142-sdk81...
Removing package boost-contract:x64-windows-static-md-v142-sdk81... done
Purging package boost-contract:x64-windows-static-md-v142-sdk81...
Purging package boost-contract:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-contract:x64-windows-static-md-v142-sdk81: 118.7 ms
Starting package 85/628: boost-poly-collection:x64-windows-static-md-v142-sdk81
Removing package boost-poly-collection:x64-windows-static-md-v142-sdk81...
Removing package boost-poly-collection:x64-windows-static-md-v142-sdk81... done
Purging package boost-poly-collection:x64-windows-static-md-v142-sdk81...
Purging package boost-poly-collection:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-poly-collection:x64-windows-static-md-v142-sdk81: 86.13 ms
Starting package 86/628: boost-type-erasure:x64-windows-static-md-v142-sdk81
Removing package boost-type-erasure:x64-windows-static-md-v142-sdk81...
Removing package boost-type-erasure:x64-windows-static-md-v142-sdk81... done
Purging package boost-type-erasure:x64-windows-static-md-v142-sdk81...
Purging package boost-type-erasure:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-type-erasure:x64-windows-static-md-v142-sdk81: 102.5 ms
Starting package 87/628: boost-thread:x64-windows-static-md-v142-sdk81
Removing package boost-thread:x64-windows-static-md-v142-sdk81...
Removing package boost-thread:x64-windows-static-md-v142-sdk81... done
Purging package boost-thread:x64-windows-static-md-v142-sdk81...
Purging package boost-thread:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-thread:x64-windows-static-md-v142-sdk81: 243.5 ms
Starting package 88/628: boost-timer:x64-windows-static-md-v142-sdk81
Removing package boost-timer:x64-windows-static-md-v142-sdk81...
Removing package boost-timer:x64-windows-static-md-v142-sdk81... done
Purging package boost-timer:x64-windows-static-md-v142-sdk81...
Purging package boost-timer:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-timer:x64-windows-static-md-v142-sdk81: 90.36 ms
Starting package 89/628: boost-chrono:x64-windows-static-md-v142-sdk81
Removing package boost-chrono:x64-windows-static-md-v142-sdk81...
Removing package boost-chrono:x64-windows-static-md-v142-sdk81... done
Purging package boost-chrono:x64-windows-static-md-v142-sdk81...
Purging package boost-chrono:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-chrono:x64-windows-static-md-v142-sdk81: 135.2 ms
Starting package 90/628: boost:x86-windows-static-md-v142-sdk81
Removing package boost:x86-windows-static-md-v142-sdk81...
Removing package boost:x86-windows-static-md-v142-sdk81... done
Purging package boost:x86-windows-static-md-v142-sdk81...
Purging package boost:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost:x86-windows-static-md-v142-sdk81: 48.78 ms
Starting package 91/628: boost:x64-windows-static-md-v142-sdk10b17134
Removing package boost:x64-windows-static-md-v142-sdk10b17134...
Removing package boost:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost:x64-windows-static-md-v142-sdk10b17134...
Purging package boost:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost:x64-windows-static-md-v142-sdk10b17134: 41.84 ms
Starting package 92/628: boost-graph-parallel:x86-windows-static-md-v142-sdk81
Removing package boost-graph-parallel:x86-windows-static-md-v142-sdk81...
Removing package boost-graph-parallel:x86-windows-static-md-v142-sdk81... done
Purging package boost-graph-parallel:x86-windows-static-md-v142-sdk81...
Purging package boost-graph-parallel:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-graph-parallel:x86-windows-static-md-v142-sdk81: 161.3 ms
Starting package 93/628: boost-parameter-python:x86-windows-static-md-v142-sdk81
Removing package boost-parameter-python:x86-windows-static-md-v142-sdk81...
Removing package boost-parameter-python:x86-windows-static-md-v142-sdk81... done
Purging package boost-parameter-python:x86-windows-static-md-v142-sdk81...
Purging package boost-parameter-python:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-parameter-python:x86-windows-static-md-v142-sdk81: 47.2 ms
Starting package 94/628: boost-python:x86-windows-static-md-v142-sdk81
Removing package boost-python:x86-windows-static-md-v142-sdk81...
Removing package boost-python:x86-windows-static-md-v142-sdk81... done
Purging package boost-python:x86-windows-static-md-v142-sdk81...
Purging package boost-python:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-python:x86-windows-static-md-v142-sdk81: 301.1 ms
Starting package 95/628: boost-graph:x86-windows-static-md-v142-sdk81
Removing package boost-graph:x86-windows-static-md-v142-sdk81...
Removing package boost-graph:x86-windows-static-md-v142-sdk81... done
Purging package boost-graph:x86-windows-static-md-v142-sdk81...
Purging package boost-graph:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-graph:x86-windows-static-md-v142-sdk81: 262.4 ms
Starting package 96/628: boost-log:x86-windows-static-md-v142-sdk81
Removing package boost-log:x86-windows-static-md-v142-sdk81...
Removing package boost-log:x86-windows-static-md-v142-sdk81... done
Purging package boost-log:x86-windows-static-md-v142-sdk81...
Purging package boost-log:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-log:x86-windows-static-md-v142-sdk81: 313.9 ms
Starting package 97/628: boost-accumulators:x86-windows-static-md-v142-sdk81
Removing package boost-accumulators:x86-windows-static-md-v142-sdk81...
Removing package boost-accumulators:x86-windows-static-md-v142-sdk81... done
Purging package boost-accumulators:x86-windows-static-md-v142-sdk81...
Purging package boost-accumulators:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-accumulators:x86-windows-static-md-v142-sdk81: 322.3 ms
Starting package 98/628: boost-ublas:x86-windows-static-md-v142-sdk81
Removing package boost-ublas:x86-windows-static-md-v142-sdk81...
Removing package boost-ublas:x86-windows-static-md-v142-sdk81... done
Purging package boost-ublas:x86-windows-static-md-v142-sdk81...
Purging package boost-ublas:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-ublas:x86-windows-static-md-v142-sdk81: 129.9 ms
Starting package 99/628: boost-odeint:x86-windows-static-md-v142-sdk81
Removing package boost-odeint:x86-windows-static-md-v142-sdk81...
Removing package boost-odeint:x86-windows-static-md-v142-sdk81... done
Purging package boost-odeint:x86-windows-static-md-v142-sdk81...
Purging package boost-odeint:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-odeint:x86-windows-static-md-v142-sdk81: 241.4 ms
Starting package 100/628: boost-compute:x86-windows-static-md-v142-sdk81
Removing package boost-compute:x86-windows-static-md-v142-sdk81...
Removing package boost-compute:x86-windows-static-md-v142-sdk81... done
Purging package boost-compute:x86-windows-static-md-v142-sdk81...
Purging package boost-compute:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-compute:x86-windows-static-md-v142-sdk81: 378.1 ms
Starting package 101/628: boost-uuid:x86-windows-static-md-v142-sdk81
Removing package boost-uuid:x86-windows-static-md-v142-sdk81...
Removing package boost-uuid:x86-windows-static-md-v142-sdk81... done
Purging package boost-uuid:x86-windows-static-md-v142-sdk81...
Purging package boost-uuid:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-uuid:x86-windows-static-md-v142-sdk81: 68.09 ms
Starting package 102/628: boost-random:x86-windows-static-md-v142-sdk81
Removing package boost-random:x86-windows-static-md-v142-sdk81...
Removing package boost-random:x86-windows-static-md-v142-sdk81... done
Purging package boost-random:x86-windows-static-md-v142-sdk81...
Purging package boost-random:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-random:x86-windows-static-md-v142-sdk81: 135.1 ms
Starting package 103/628: boost-poly-collection:x64-windows-static-md-v142-sdk10b17134
Removing package boost-poly-collection:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-poly-collection:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-poly-collection:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-poly-collection:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-poly-collection:x64-windows-static-md-v142-sdk10b17134: 76.84 ms
Starting package 104/628: boost-beast:x86-windows-static-md-v142-sdk81
Removing package boost-beast:x86-windows-static-md-v142-sdk81...
Removing package boost-beast:x86-windows-static-md-v142-sdk81... done
Purging package boost-beast:x86-windows-static-md-v142-sdk81...
Purging package boost-beast:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-beast:x86-windows-static-md-v142-sdk81: 273.8 ms
Starting package 105/628: boost-process:x86-windows-static-md-v142-sdk81
Removing package boost-process:x86-windows-static-md-v142-sdk81...
Removing package boost-process:x86-windows-static-md-v142-sdk81... done
Purging package boost-process:x86-windows-static-md-v142-sdk81...
Purging package boost-process:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-process:x86-windows-static-md-v142-sdk81: 154.1 ms
Starting package 106/628: boost-asio:x86-windows-static-md-v142-sdk81
Removing package boost-asio:x86-windows-static-md-v142-sdk81...
Removing package boost-asio:x86-windows-static-md-v142-sdk81... done
Purging package boost-asio:x86-windows-static-md-v142-sdk81...
Purging package boost-asio:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-asio:x86-windows-static-md-v142-sdk81: 549.6 ms
Starting package 107/628: boost-statechart:x86-windows-static-md-v142-sdk81
Removing package boost-statechart:x86-windows-static-md-v142-sdk81...
Removing package boost-statechart:x86-windows-static-md-v142-sdk81... done
Purging package boost-statechart:x86-windows-static-md-v142-sdk81...
Purging package boost-statechart:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-statechart:x86-windows-static-md-v142-sdk81: 71.27 ms
Starting package 108/628: boost-coroutine2:x86-windows-static-md-v142-sdk81
Removing package boost-coroutine2:x86-windows-static-md-v142-sdk81...
Removing package boost-coroutine2:x86-windows-static-md-v142-sdk81... done
Purging package boost-coroutine2:x86-windows-static-md-v142-sdk81...
Purging package boost-coroutine2:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-coroutine2:x86-windows-static-md-v142-sdk81: 61.17 ms
Starting package 109/628: boost-coroutine:x86-windows-static-md-v142-sdk81
Removing package boost-coroutine:x86-windows-static-md-v142-sdk81...
Removing package boost-coroutine:x86-windows-static-md-v142-sdk81... done
Purging package boost-coroutine:x86-windows-static-md-v142-sdk81...
Purging package boost-coroutine:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-coroutine:x86-windows-static-md-v142-sdk81: 84.85 ms
Starting package 110/628: boost-fiber:x86-windows-static-md-v142-sdk81
Removing package boost-fiber:x86-windows-static-md-v142-sdk81...
Removing package boost-fiber:x86-windows-static-md-v142-sdk81... done
Purging package boost-fiber:x86-windows-static-md-v142-sdk81...
Purging package boost-fiber:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-fiber:x86-windows-static-md-v142-sdk81: 114.7 ms
Starting package 111/628: boost-context:x86-windows-static-md-v142-sdk81
Removing package boost-context:x86-windows-static-md-v142-sdk81...
Removing package boost-context:x86-windows-static-md-v142-sdk81... done
Purging package boost-context:x86-windows-static-md-v142-sdk81...
Purging package boost-context:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-context:x86-windows-static-md-v142-sdk81: 79.05 ms
Starting package 112/628: boost-xpressive:x86-windows-static-md-v142-sdk81
Removing package boost-xpressive:x86-windows-static-md-v142-sdk81...
Removing package boost-xpressive:x86-windows-static-md-v142-sdk81... done
Purging package boost-xpressive:x86-windows-static-md-v142-sdk81...
Purging package boost-xpressive:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-xpressive:x86-windows-static-md-v142-sdk81: 171.2 ms
Starting package 113/628: boost-convert:x86-windows-static-md-v142-sdk81
Removing package boost-convert:x86-windows-static-md-v142-sdk81...
Removing package boost-convert:x86-windows-static-md-v142-sdk81... done
Purging package boost-convert:x86-windows-static-md-v142-sdk81...
Purging package boost-convert:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-convert:x86-windows-static-md-v142-sdk81: 54.03 ms
Starting package 114/628: boost-flyweight:x86-windows-static-md-v142-sdk81
Removing package boost-flyweight:x86-windows-static-md-v142-sdk81...
Removing package boost-flyweight:x86-windows-static-md-v142-sdk81... done
Purging package boost-flyweight:x86-windows-static-md-v142-sdk81...
Purging package boost-flyweight:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-flyweight:x86-windows-static-md-v142-sdk81: 87.64 ms
Starting package 115/628: boost-bimap:x86-windows-static-md-v142-sdk81
Removing package boost-bimap:x86-windows-static-md-v142-sdk81...
Removing package boost-bimap:x86-windows-static-md-v142-sdk81... done
Purging package boost-bimap:x86-windows-static-md-v142-sdk81...
Purging package boost-bimap:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-bimap:x86-windows-static-md-v142-sdk81: 164.3 ms
Starting package 116/628: boost-histogram:x86-windows-static-md-v142-sdk81
Removing package boost-histogram:x86-windows-static-md-v142-sdk81...
Removing package boost-histogram:x86-windows-static-md-v142-sdk81... done
Purging package boost-histogram:x86-windows-static-md-v142-sdk81...
Purging package boost-histogram:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-histogram:x86-windows-static-md-v142-sdk81: 115.1 ms
Starting package 117/628: boost-geometry:x86-windows-static-md-v142-sdk81
Removing package boost-geometry:x86-windows-static-md-v142-sdk81...
Removing package boost-geometry:x86-windows-static-md-v142-sdk81... done
Purging package boost-geometry:x86-windows-static-md-v142-sdk81...
Purging package boost-geometry:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-geometry:x86-windows-static-md-v142-sdk81: 1.149 s
Starting package 118/628: boost-property-map:x86-windows-static-md-v142-sdk81
Removing package boost-property-map:x86-windows-static-md-v142-sdk81...
Removing package boost-property-map:x86-windows-static-md-v142-sdk81... done
Purging package boost-property-map:x86-windows-static-md-v142-sdk81...
Purging package boost-property-map:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-property-map:x86-windows-static-md-v142-sdk81: 66.02 ms
Starting package 119/628: boost-msm:x86-windows-static-md-v142-sdk81
Removing package boost-msm:x86-windows-static-md-v142-sdk81...
Removing package boost-msm:x86-windows-static-md-v142-sdk81... done
Purging package boost-msm:x86-windows-static-md-v142-sdk81...
Purging package boost-msm:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-msm:x86-windows-static-md-v142-sdk81: 96.77 ms
Starting package 120/628: boost-property-tree:x86-windows-static-md-v142-sdk81
Removing package boost-property-tree:x86-windows-static-md-v142-sdk81...
Removing package boost-property-tree:x86-windows-static-md-v142-sdk81... done
Purging package boost-property-tree:x86-windows-static-md-v142-sdk81...
Purging package boost-property-tree:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-property-tree:x86-windows-static-md-v142-sdk81: 77 ms
Starting package 121/628: boost-wave:x86-windows-static-md-v142-sdk81
Removing package boost-wave:x86-windows-static-md-v142-sdk81...
Removing package boost-wave:x86-windows-static-md-v142-sdk81... done
Purging package boost-wave:x86-windows-static-md-v142-sdk81...
Purging package boost-wave:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-wave:x86-windows-static-md-v142-sdk81: 109.1 ms
Starting package 122/628: boost-multi-index:x86-windows-static-md-v142-sdk81
Removing package boost-multi-index:x86-windows-static-md-v142-sdk81...
Removing package boost-multi-index:x86-windows-static-md-v142-sdk81... done
Purging package boost-multi-index:x86-windows-static-md-v142-sdk81...
Purging package boost-multi-index:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-multi-index:x86-windows-static-md-v142-sdk81: 134.1 ms
Starting package 123/628: boost-assign:x86-windows-static-md-v142-sdk81
Removing package boost-assign:x86-windows-static-md-v142-sdk81...
Removing package boost-assign:x86-windows-static-md-v142-sdk81... done
Purging package boost-assign:x86-windows-static-md-v142-sdk81...
Purging package boost-assign:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-assign:x86-windows-static-md-v142-sdk81: 55.44 ms
Starting package 124/628: boost-ptr-container:x86-windows-static-md-v142-sdk81
Removing package boost-ptr-container:x86-windows-static-md-v142-sdk81...
Removing package boost-ptr-container:x86-windows-static-md-v142-sdk81... done
Purging package boost-ptr-container:x86-windows-static-md-v142-sdk81...
Purging package boost-ptr-container:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-ptr-container:x86-windows-static-md-v142-sdk81: 79.54 ms
Starting package 125/628: boost-sort:x86-windows-static-md-v142-sdk81
Removing package boost-sort:x86-windows-static-md-v142-sdk81...
Removing package boost-sort:x86-windows-static-md-v142-sdk81... done
Purging package boost-sort:x86-windows-static-md-v142-sdk81...
Purging package boost-sort:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-sort:x86-windows-static-md-v142-sdk81: 111.3 ms
Starting package 126/628: boost-units:x86-windows-static-md-v142-sdk81
Removing package boost-units:x86-windows-static-md-v142-sdk81...
Removing package boost-units:x86-windows-static-md-v142-sdk81... done
Purging package boost-units:x86-windows-static-md-v142-sdk81...
Purging package boost-units:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-units:x86-windows-static-md-v142-sdk81: 378.2 ms
Starting package 127/628: boost-serialization:x86-windows-static-md-v142-sdk81
Removing package boost-serialization:x86-windows-static-md-v142-sdk81...
Removing package boost-serialization:x86-windows-static-md-v142-sdk81... done
Purging package boost-serialization:x86-windows-static-md-v142-sdk81...
Purging package boost-serialization:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-serialization:x86-windows-static-md-v142-sdk81: 267.9 ms
Starting package 128/628: boost-dll:x86-windows-static-md-v142-sdk81
Removing package boost-dll:x86-windows-static-md-v142-sdk81...
Removing package boost-dll:x86-windows-static-md-v142-sdk81... done
Purging package boost-dll:x86-windows-static-md-v142-sdk81...
Purging package boost-dll:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-dll:x86-windows-static-md-v142-sdk81: 74.69 ms
Starting package 129/628: boost-spirit:x86-windows-static-md-v142-sdk81
Removing package boost-spirit:x86-windows-static-md-v142-sdk81...
Removing package boost-spirit:x86-windows-static-md-v142-sdk81... done
Purging package boost-spirit:x86-windows-static-md-v142-sdk81...
Purging package boost-spirit:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-spirit:x86-windows-static-md-v142-sdk81: 1.159 s
Starting package 130/628: boost-locale:x86-windows-static-md-v142-sdk81
Removing package boost-locale:x86-windows-static-md-v142-sdk81...
Removing package boost-locale:x86-windows-static-md-v142-sdk81... done
Purging package boost-locale:x86-windows-static-md-v142-sdk81...
Purging package boost-locale:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-locale:x86-windows-static-md-v142-sdk81: 82.16 ms
Starting package 131/628: boost-contract:x86-windows-static-md-v142-sdk81
Removing package boost-contract:x86-windows-static-md-v142-sdk81...
Removing package boost-contract:x86-windows-static-md-v142-sdk81... done
Purging package boost-contract:x86-windows-static-md-v142-sdk81...
Purging package boost-contract:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-contract:x86-windows-static-md-v142-sdk81: 113.5 ms
Starting package 132/628: boost-poly-collection:x86-windows-static-md-v142-sdk81
Removing package boost-poly-collection:x86-windows-static-md-v142-sdk81...
Removing package boost-poly-collection:x86-windows-static-md-v142-sdk81... done
Purging package boost-poly-collection:x86-windows-static-md-v142-sdk81...
Purging package boost-poly-collection:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-poly-collection:x86-windows-static-md-v142-sdk81: 85.42 ms
Starting package 133/628: boost-type-erasure:x86-windows-static-md-v142-sdk81
Removing package boost-type-erasure:x86-windows-static-md-v142-sdk81...
Removing package boost-type-erasure:x86-windows-static-md-v142-sdk81... done
Purging package boost-type-erasure:x86-windows-static-md-v142-sdk81...
Purging package boost-type-erasure:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-type-erasure:x86-windows-static-md-v142-sdk81: 109.2 ms
Starting package 134/628: boost-thread:x86-windows-static-md-v142-sdk81
Removing package boost-thread:x86-windows-static-md-v142-sdk81...
Removing package boost-thread:x86-windows-static-md-v142-sdk81... done
Purging package boost-thread:x86-windows-static-md-v142-sdk81...
Purging package boost-thread:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-thread:x86-windows-static-md-v142-sdk81: 247 ms
Starting package 135/628: boost-timer:x86-windows-static-md-v142-sdk81
Removing package boost-timer:x86-windows-static-md-v142-sdk81...
Removing package boost-timer:x86-windows-static-md-v142-sdk81... done
Purging package boost-timer:x86-windows-static-md-v142-sdk81...
Purging package boost-timer:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-timer:x86-windows-static-md-v142-sdk81: 45.17 ms
Starting package 136/628: boost-chrono:x86-windows-static-md-v142-sdk81
Removing package boost-chrono:x86-windows-static-md-v142-sdk81...
Removing package boost-chrono:x86-windows-static-md-v142-sdk81... done
Purging package boost-chrono:x86-windows-static-md-v142-sdk81...
Purging package boost-chrono:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-chrono:x86-windows-static-md-v142-sdk81: 95.04 ms
Starting package 137/628: boost-accumulators:x64-windows-static-md-v142-sdk10b17134
Removing package boost-accumulators:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-accumulators:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-accumulators:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-accumulators:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-accumulators:x64-windows-static-md-v142-sdk10b17134: 138.7 ms
Starting package 138/628: boost-ublas:x64-windows-static-md-v142-sdk10b17134
Removing package boost-ublas:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-ublas:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-ublas:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-ublas:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-ublas:x64-windows-static-md-v142-sdk10b17134: 114.3 ms
Starting package 139/628: boost-odeint:x64-windows-static-md-v142-sdk10b17134
Removing package boost-odeint:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-odeint:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-odeint:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-odeint:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-odeint:x64-windows-static-md-v142-sdk10b17134: 228.1 ms
Starting package 140/628: boost-compute:x64-windows-static-md-v142-sdk10b17134
Removing package boost-compute:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-compute:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-compute:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-compute:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-compute:x64-windows-static-md-v142-sdk10b17134: 361 ms
Starting package 141/628: boost-fiber:x64-windows-static-md-v142-sdk10b17134
Removing package boost-fiber:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-fiber:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-fiber:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-fiber:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-fiber:x64-windows-static-md-v142-sdk10b17134: 108.2 ms
Starting package 142/628: boost-graph-parallel:x64-windows-static-md-v142-sdk10b17134
Removing package boost-graph-parallel:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-graph-parallel:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-graph-parallel:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-graph-parallel:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-graph-parallel:x64-windows-static-md-v142-sdk10b17134: 93.51 ms
Starting package 143/628: boost-parameter-python:x64-windows-static-md-v142-sdk10b17134
Removing package boost-parameter-python:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-parameter-python:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-parameter-python:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-parameter-python:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-parameter-python:x64-windows-static-md-v142-sdk10b17134: 37.65 ms
Starting package 144/628: boost-python:x64-windows-static-md-v142-sdk10b17134
Removing package boost-python:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-python:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-python:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-python:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-python:x64-windows-static-md-v142-sdk10b17134: 290.5 ms
Starting package 145/628: boost-graph:x64-windows-static-md-v142-sdk10b17134
Removing package boost-graph:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-graph:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-graph:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-graph:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-graph:x64-windows-static-md-v142-sdk10b17134: 243.4 ms
Starting package 146/628: boost-test:x64-windows-static-md-v142-sdk10b17134
Removing package boost-test:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-test:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-test:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-test:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-test:x64-windows-static-md-v142-sdk10b17134: 196.8 ms
Starting package 147/628: boost-beast:x64-windows-static-md-v142-sdk10b17134
Removing package boost-beast:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-beast:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-beast:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-beast:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-beast:x64-windows-static-md-v142-sdk10b17134: 347.8 ms
Starting package 148/628: boost-log:x64-windows-static-md-v142-sdk10b17134
Removing package boost-log:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-log:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-log:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-log:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-log:x64-windows-static-md-v142-sdk10b17134: 305.7 ms
Starting package 149/628: boost-process:x64-windows-static-md-v142-sdk10b17134
Removing package boost-process:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-process:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-process:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-process:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-process:x64-windows-static-md-v142-sdk10b17134: 205.8 ms
Starting package 150/628: boost-asio:x64-windows-static-md-v142-sdk10b17134
Removing package boost-asio:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-asio:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-asio:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-asio:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-asio:x64-windows-static-md-v142-sdk10b17134: 500.2 ms
Starting package 151/628: boost-icl:x64-windows-static-md-v142-sdk10b17134
Removing package boost-icl:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-icl:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-icl:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-icl:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-icl:x64-windows-static-md-v142-sdk10b17134: 165.3 ms
Starting package 152/628: boost-flyweight:x64-windows-static-md-v142-sdk10b17134
Removing package boost-flyweight:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-flyweight:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-flyweight:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-flyweight:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-flyweight:x64-windows-static-md-v142-sdk10b17134: 76.09 ms
Starting package 153/628: boost-interprocess:x64-windows-static-md-v142-sdk10b17134
Removing package boost-interprocess:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-interprocess:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-interprocess:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-interprocess:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-interprocess:x64-windows-static-md-v142-sdk10b17134: 211.8 ms
Starting package 154/628: boost-statechart:x64-windows-static-md-v142-sdk10b17134
Removing package boost-statechart:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-statechart:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-statechart:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-statechart:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-statechart:x64-windows-static-md-v142-sdk10b17134: 66.78 ms
Starting package 155/628: boost-coroutine2:x64-windows-static-md-v142-sdk10b17134
Removing package boost-coroutine2:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-coroutine2:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-coroutine2:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-coroutine2:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-coroutine2:x64-windows-static-md-v142-sdk10b17134: 60.58 ms
Starting package 156/628: boost-coroutine:x64-windows-static-md-v142-sdk10b17134
Removing package boost-coroutine:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-coroutine:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-coroutine:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-coroutine:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-coroutine:x64-windows-static-md-v142-sdk10b17134: 73.55 ms
Starting package 157/628: boost-context:x64-windows-static-md-v142-sdk10b17134
Removing package boost-context:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-context:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-context:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-context:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-context:x64-windows-static-md-v142-sdk10b17134: 72.65 ms
Starting package 158/628: boost-xpressive:x64-windows-static-md-v142-sdk10b17134
Removing package boost-xpressive:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-xpressive:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-xpressive:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-xpressive:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-xpressive:x64-windows-static-md-v142-sdk10b17134: 156.4 ms
Starting package 159/628: boost-convert:x64-windows-static-md-v142-sdk10b17134
Removing package boost-convert:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-convert:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-convert:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-convert:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-convert:x64-windows-static-md-v142-sdk10b17134: 54.72 ms
Starting package 160/628: boost-uuid:x64-windows-static-md-v142-sdk10b17134
Removing package boost-uuid:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-uuid:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-uuid:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-uuid:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-uuid:x64-windows-static-md-v142-sdk10b17134: 59.47 ms
Starting package 161/628: boost-bimap:x64-windows-static-md-v142-sdk10b17134
Removing package boost-bimap:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-bimap:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-bimap:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-bimap:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-bimap:x64-windows-static-md-v142-sdk10b17134: 135.4 ms
Starting package 162/628: boost-histogram:x64-windows-static-md-v142-sdk10b17134
Removing package boost-histogram:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-histogram:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-histogram:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-histogram:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-histogram:x64-windows-static-md-v142-sdk10b17134: 105.6 ms
Starting package 163/628: boost-geometry:x64-windows-static-md-v142-sdk10b17134
Removing package boost-geometry:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-geometry:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-geometry:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-geometry:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-geometry:x64-windows-static-md-v142-sdk10b17134: 1.028 s
Starting package 164/628: boost-property-map:x64-windows-static-md-v142-sdk10b17134
Removing package boost-property-map:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-property-map:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-property-map:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-property-map:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-property-map:x64-windows-static-md-v142-sdk10b17134: 58.67 ms
Starting package 165/628: boost-msm:x64-windows-static-md-v142-sdk10b17134
Removing package boost-msm:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-msm:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-msm:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-msm:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-msm:x64-windows-static-md-v142-sdk10b17134: 91.48 ms
Starting package 166/628: boost-property-tree:x64-windows-static-md-v142-sdk10b17134
Removing package boost-property-tree:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-property-tree:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-property-tree:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-property-tree:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-property-tree:x64-windows-static-md-v142-sdk10b17134: 69.72 ms
Starting package 167/628: boost-wave:x64-windows-static-md-v142-sdk10b17134
Removing package boost-wave:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-wave:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-wave:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-wave:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-wave:x64-windows-static-md-v142-sdk10b17134: 106.3 ms
Starting package 168/628: boost-multi-index:x64-windows-static-md-v142-sdk10b17134
Removing package boost-multi-index:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-multi-index:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-multi-index:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-multi-index:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-multi-index:x64-windows-static-md-v142-sdk10b17134: 129.6 ms
Starting package 169/628: boost-assign:x64-windows-static-md-v142-sdk10b17134
Removing package boost-assign:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-assign:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-assign:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-assign:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-assign:x64-windows-static-md-v142-sdk10b17134: 53.03 ms
Starting package 170/628: boost-ptr-container:x64-windows-static-md-v142-sdk10b17134
Removing package boost-ptr-container:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-ptr-container:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-ptr-container:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-ptr-container:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-ptr-container:x64-windows-static-md-v142-sdk10b17134: 75.18 ms
Starting package 171/628: boost-sort:x64-windows-static-md-v142-sdk10b17134
Removing package boost-sort:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-sort:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-sort:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-sort:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-sort:x64-windows-static-md-v142-sdk10b17134: 92.02 ms
Starting package 172/628: boost-units:x64-windows-static-md-v142-sdk10b17134
Removing package boost-units:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-units:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-units:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-units:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-units:x64-windows-static-md-v142-sdk10b17134: 409.7 ms
Starting package 173/628: boost-serialization:x64-windows-static-md-v142-sdk10b17134
Removing package boost-serialization:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-serialization:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-serialization:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-serialization:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-serialization:x64-windows-static-md-v142-sdk10b17134: 245.3 ms
Starting package 174/628: boost-dll:x64-windows-static-md-v142-sdk10b17134
Removing package boost-dll:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-dll:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-dll:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-dll:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-dll:x64-windows-static-md-v142-sdk10b17134: 68.46 ms
Starting package 175/628: boost-spirit:x64-windows-static-md-v142-sdk10b17134
Removing package boost-spirit:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-spirit:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-spirit:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-spirit:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-spirit:x64-windows-static-md-v142-sdk10b17134: 1.145 s
Starting package 176/628: boost-locale:x64-windows-static-md-v142-sdk10b17134
Removing package boost-locale:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-locale:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-locale:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-locale:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-locale:x64-windows-static-md-v142-sdk10b17134: 71.12 ms
Starting package 177/628: boost-contract:x64-windows-static-md-v142-sdk10b17134
Removing package boost-contract:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-contract:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-contract:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-contract:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-contract:x64-windows-static-md-v142-sdk10b17134: 100.9 ms
Starting package 178/628: boost-type-erasure:x64-windows-static-md-v142-sdk10b17134
Removing package boost-type-erasure:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-type-erasure:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-type-erasure:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-type-erasure:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-type-erasure:x64-windows-static-md-v142-sdk10b17134: 96.91 ms
Starting package 179/628: boost-thread:x64-windows-static-md-v142-sdk10b17134
Removing package boost-thread:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-thread:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-thread:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-thread:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-thread:x64-windows-static-md-v142-sdk10b17134: 217.2 ms
Starting package 180/628: boost-date-time:x64-windows-static-md-v142-sdk10b17134
Removing package boost-date-time:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-date-time:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-date-time:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-date-time:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-date-time:x64-windows-static-md-v142-sdk10b17134: 148.3 ms
Starting package 181/628: boost-algorithm:x64-windows-static-md-v142-sdk10b17134
Removing package boost-algorithm:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-algorithm:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-algorithm:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-algorithm:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-algorithm:x64-windows-static-md-v142-sdk10b17134: 121.8 ms
Starting package 182/628: boost-nowide:x86-windows-static-md-v142-sdk10b17134
Removing package boost-nowide:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-nowide:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-nowide:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-nowide:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-nowide:x86-windows-static-md-v142-sdk10b17134: 56.79 ms
Starting package 183/628: boost-gil:x86-windows-static-md-v142-sdk10b17134
Removing package boost-gil:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-gil:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-gil:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-gil:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-gil:x86-windows-static-md-v142-sdk10b17134: 262.2 ms
Starting package 184/628: boost-filesystem:x86-windows-static-md-v142-sdk10b17134
Removing package boost-filesystem:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-filesystem:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-filesystem:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-filesystem:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-filesystem:x86-windows-static-md-v142-sdk10b17134: 56.01 ms
Starting package 185/628: boost-interprocess:x86-windows-static-md-v142-sdk81
Removing package boost-interprocess:x86-windows-static-md-v142-sdk81...
Removing package boost-interprocess:x86-windows-static-md-v142-sdk81... done
Purging package boost-interprocess:x86-windows-static-md-v142-sdk81...
Purging package boost-interprocess:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-interprocess:x86-windows-static-md-v142-sdk81: 227.2 ms
Starting package 186/628: boost-timer:x64-windows-static-md-v142-sdk10b17134
Removing package boost-timer:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-timer:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-timer:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-timer:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-timer:x64-windows-static-md-v142-sdk10b17134: 43.51 ms
Starting package 187/628: boost-chrono:x64-windows-static-md-v142-sdk10b17134
Removing package boost-chrono:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-chrono:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-chrono:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-chrono:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-chrono:x64-windows-static-md-v142-sdk10b17134: 93.11 ms
Starting package 188/628: boost-test:x86-windows-static-md-v142-sdk10b17134
Removing package boost-test:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-test:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-test:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-test:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-test:x86-windows-static-md-v142-sdk10b17134: 199.4 ms
Starting package 189/628: boost-icl:x86-windows-static-md-v142-sdk10b17134
Removing package boost-icl:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-icl:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-icl:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-icl:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-icl:x86-windows-static-md-v142-sdk10b17134: 145.5 ms
Starting package 190/628: boost-interprocess:x86-windows-static-md-v142-sdk10b17134
Removing package boost-interprocess:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-interprocess:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-interprocess:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-interprocess:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-interprocess:x86-windows-static-md-v142-sdk10b17134: 210.7 ms
Starting package 191/628: boost-date-time:x86-windows-static-md-v142-sdk10b17134
Removing package boost-date-time:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-date-time:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-date-time:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-date-time:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-date-time:x86-windows-static-md-v142-sdk10b17134: 166 ms
Starting package 192/628: boost-algorithm:x86-windows-static-md-v142-sdk10b17134
Removing package boost-algorithm:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-algorithm:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-algorithm:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-algorithm:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-algorithm:x86-windows-static-md-v142-sdk10b17134: 134.2 ms
Starting package 193/628: boost-test:x64-windows-static-md-v142-sdk81
Removing package boost-test:x64-windows-static-md-v142-sdk81...
Removing package boost-test:x64-windows-static-md-v142-sdk81... done
Purging package boost-test:x64-windows-static-md-v142-sdk81...
Purging package boost-test:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-test:x64-windows-static-md-v142-sdk81: 217.8 ms
Starting package 194/628: boost-icl:x64-windows-static-md-v142-sdk81
Removing package boost-icl:x64-windows-static-md-v142-sdk81...
Removing package boost-icl:x64-windows-static-md-v142-sdk81... done
Purging package boost-icl:x64-windows-static-md-v142-sdk81...
Purging package boost-icl:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-icl:x64-windows-static-md-v142-sdk81: 147.3 ms
Starting package 195/628: boost-interprocess:x64-windows-static-md-v142-sdk81
Removing package boost-interprocess:x64-windows-static-md-v142-sdk81...
Removing package boost-interprocess:x64-windows-static-md-v142-sdk81... done
Purging package boost-interprocess:x64-windows-static-md-v142-sdk81...
Purging package boost-interprocess:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-interprocess:x64-windows-static-md-v142-sdk81: 228.4 ms
Starting package 196/628: boost-date-time:x64-windows-static-md-v142-sdk81
Removing package boost-date-time:x64-windows-static-md-v142-sdk81...
Removing package boost-date-time:x64-windows-static-md-v142-sdk81... done
Purging package boost-date-time:x64-windows-static-md-v142-sdk81...
Purging package boost-date-time:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-date-time:x64-windows-static-md-v142-sdk81: 162.2 ms
Starting package 197/628: boost-algorithm:x64-windows-static-md-v142-sdk81
Removing package boost-algorithm:x64-windows-static-md-v142-sdk81...
Removing package boost-algorithm:x64-windows-static-md-v142-sdk81... done
Purging package boost-algorithm:x64-windows-static-md-v142-sdk81...
Purging package boost-algorithm:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-algorithm:x64-windows-static-md-v142-sdk81: 125 ms
Starting package 198/628: boost-test:x86-windows-static-md-v142-sdk81
Removing package boost-test:x86-windows-static-md-v142-sdk81...
Removing package boost-test:x86-windows-static-md-v142-sdk81... done
Purging package boost-test:x86-windows-static-md-v142-sdk81...
Purging package boost-test:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-test:x86-windows-static-md-v142-sdk81: 222.7 ms
Starting package 199/628: boost-icl:x86-windows-static-md-v142-sdk81
Removing package boost-icl:x86-windows-static-md-v142-sdk81...
Removing package boost-icl:x86-windows-static-md-v142-sdk81... done
Purging package boost-icl:x86-windows-static-md-v142-sdk81...
Purging package boost-icl:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-icl:x86-windows-static-md-v142-sdk81: 158.4 ms
Starting package 200/628: boost-date-time:x86-windows-static-md-v142-sdk81
Removing package boost-date-time:x86-windows-static-md-v142-sdk81...
Removing package boost-date-time:x86-windows-static-md-v142-sdk81... done
Purging package boost-date-time:x86-windows-static-md-v142-sdk81...
Purging package boost-date-time:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-date-time:x86-windows-static-md-v142-sdk81: 156.1 ms
Starting package 201/628: boost-algorithm:x86-windows-static-md-v142-sdk81
Removing package boost-algorithm:x86-windows-static-md-v142-sdk81...
Removing package boost-algorithm:x86-windows-static-md-v142-sdk81... done
Purging package boost-algorithm:x86-windows-static-md-v142-sdk81...
Purging package boost-algorithm:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-algorithm:x86-windows-static-md-v142-sdk81: 132.1 ms
Starting package 202/628: boost-program-options:x64-windows-static-md-v142-sdk10b17134
Removing package boost-program-options:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-program-options:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-program-options:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-program-options:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-program-options:x64-windows-static-md-v142-sdk10b17134: 61.9 ms
Starting package 203/628: boost-random:x64-windows-static-md-v142-sdk10b17134
Removing package boost-random:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-random:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-random:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-random:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-random:x64-windows-static-md-v142-sdk10b17134: 123.3 ms
Starting package 204/628: boost-math:x64-windows-static-md-v142-sdk10b17134
Removing package boost-math:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-math:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-math:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-math:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-math:x64-windows-static-md-v142-sdk10b17134: 465.1 ms
Starting package 205/628: boost-program-options:x86-windows-static-md-v142-sdk10b17134
Removing package boost-program-options:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-program-options:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-program-options:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-program-options:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-program-options:x86-windows-static-md-v142-sdk10b17134: 61.65 ms
Starting package 206/628: boost-random:x86-windows-static-md-v142-sdk10b17134
Removing package boost-random:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-random:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-random:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-random:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-random:x86-windows-static-md-v142-sdk10b17134: 123.7 ms
Starting package 207/628: boost-math:x86-windows-static-md-v142-sdk10b17134
Removing package boost-math:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-math:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-math:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-math:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-math:x86-windows-static-md-v142-sdk10b17134: 719.2 ms
Starting package 208/628: boost-program-options:x64-windows-static-md-v142-sdk81
Removing package boost-program-options:x64-windows-static-md-v142-sdk81...
Removing package boost-program-options:x64-windows-static-md-v142-sdk81... done
Purging package boost-program-options:x64-windows-static-md-v142-sdk81...
Purging package boost-program-options:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-program-options:x64-windows-static-md-v142-sdk81: 65.12 ms
Starting package 209/628: boost-random:x64-windows-static-md-v142-sdk81
Removing package boost-random:x64-windows-static-md-v142-sdk81...
Removing package boost-random:x64-windows-static-md-v142-sdk81... done
Purging package boost-random:x64-windows-static-md-v142-sdk81...
Purging package boost-random:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-random:x64-windows-static-md-v142-sdk81: 124 ms
Starting package 210/628: boost-math:x64-windows-static-md-v142-sdk81
Removing package boost-math:x64-windows-static-md-v142-sdk81...
Removing package boost-math:x64-windows-static-md-v142-sdk81... done
Purging package boost-math:x64-windows-static-md-v142-sdk81...
Purging package boost-math:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-math:x64-windows-static-md-v142-sdk81: 486.6 ms
Starting package 211/628: boost-program-options:x86-windows-static-md-v142-sdk81
Removing package boost-program-options:x86-windows-static-md-v142-sdk81...
Removing package boost-program-options:x86-windows-static-md-v142-sdk81... done
Purging package boost-program-options:x86-windows-static-md-v142-sdk81...
Purging package boost-program-options:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-program-options:x86-windows-static-md-v142-sdk81: 64.03 ms
Starting package 212/628: boost-math:x86-windows-static-md-v142-sdk81
Removing package boost-math:x86-windows-static-md-v142-sdk81...
Removing package boost-math:x86-windows-static-md-v142-sdk81... done
Purging package boost-math:x86-windows-static-md-v142-sdk81...
Purging package boost-math:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-math:x86-windows-static-md-v142-sdk81: 510.7 ms
Starting package 213/628: boost-nowide:x64-windows-static-md-v142-sdk10b17134
Removing package boost-nowide:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-nowide:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-nowide:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-nowide:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-nowide:x64-windows-static-md-v142-sdk10b17134: 55.79 ms
Starting package 214/628: boost-gil:x64-windows-static-md-v142-sdk10b17134
Removing package boost-gil:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-gil:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-gil:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-gil:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-gil:x64-windows-static-md-v142-sdk10b17134: 252.1 ms
Starting package 215/628: boost-filesystem:x64-windows-static-md-v142-sdk10b17134
Removing package boost-filesystem:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-filesystem:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-filesystem:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-filesystem:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-filesystem:x64-windows-static-md-v142-sdk10b17134: 54.07 ms
Starting package 216/628: boost-system:x64-windows-static-md-v142-sdk10b17134
Removing package boost-system:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-system:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-system:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-system:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-system:x64-windows-static-md-v142-sdk10b17134: 57.25 ms
Starting package 217/628: boost-lockfree:x86-windows-static-md-v142-sdk10b17134
Removing package boost-lockfree:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-lockfree:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-lockfree:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-lockfree:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-lockfree:x86-windows-static-md-v142-sdk10b17134: 49.38 ms
Starting package 218/628: boost-multiprecision:x86-windows-static-md-v142-sdk10b17134
Removing package boost-multiprecision:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-multiprecision:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-multiprecision:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-multiprecision:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-multiprecision:x86-windows-static-md-v142-sdk10b17134: 105.7 ms
Starting package 219/628: boost-atomic:x86-windows-static-md-v142-sdk10b17134
Removing package boost-atomic:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-atomic:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-atomic:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-atomic:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-atomic:x86-windows-static-md-v142-sdk10b17134: 145.2 ms
Starting package 220/628: boost-lockfree:x64-windows-static-md-v142-sdk81
Removing package boost-lockfree:x64-windows-static-md-v142-sdk81...
Removing package boost-lockfree:x64-windows-static-md-v142-sdk81... done
Purging package boost-lockfree:x64-windows-static-md-v142-sdk81...
Purging package boost-lockfree:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-lockfree:x64-windows-static-md-v142-sdk81: 51.99 ms
Starting package 221/628: boost-multiprecision:x64-windows-static-md-v142-sdk81
Removing package boost-multiprecision:x64-windows-static-md-v142-sdk81...
Removing package boost-multiprecision:x64-windows-static-md-v142-sdk81... done
Purging package boost-multiprecision:x64-windows-static-md-v142-sdk81...
Purging package boost-multiprecision:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-multiprecision:x64-windows-static-md-v142-sdk81: 100.4 ms
Starting package 222/628: boost-atomic:x64-windows-static-md-v142-sdk81
Removing package boost-atomic:x64-windows-static-md-v142-sdk81...
Removing package boost-atomic:x64-windows-static-md-v142-sdk81... done
Purging package boost-atomic:x64-windows-static-md-v142-sdk81...
Purging package boost-atomic:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-atomic:x64-windows-static-md-v142-sdk81: 144.8 ms
Starting package 223/628: boost-lockfree:x64-windows-static-md-v142-sdk10b17134
Removing package boost-lockfree:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-lockfree:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-lockfree:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-lockfree:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-lockfree:x64-windows-static-md-v142-sdk10b17134: 50.48 ms
Starting package 224/628: boost-multiprecision:x64-windows-static-md-v142-sdk10b17134
Removing package boost-multiprecision:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-multiprecision:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-multiprecision:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-multiprecision:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-multiprecision:x64-windows-static-md-v142-sdk10b17134: 99.03 ms
Starting package 225/628: boost-atomic:x64-windows-static-md-v142-sdk10b17134
Removing package boost-atomic:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-atomic:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-atomic:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-atomic:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-atomic:x64-windows-static-md-v142-sdk10b17134: 138.9 ms
Starting package 226/628: boost-lockfree:x86-windows-static-md-v142-sdk81
Removing package boost-lockfree:x86-windows-static-md-v142-sdk81...
Removing package boost-lockfree:x86-windows-static-md-v142-sdk81... done
Purging package boost-lockfree:x86-windows-static-md-v142-sdk81...
Purging package boost-lockfree:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-lockfree:x86-windows-static-md-v142-sdk81: 52.77 ms
Starting package 227/628: boost-multiprecision:x86-windows-static-md-v142-sdk81
Removing package boost-multiprecision:x86-windows-static-md-v142-sdk81...
Removing package boost-multiprecision:x86-windows-static-md-v142-sdk81... done
Purging package boost-multiprecision:x86-windows-static-md-v142-sdk81...
Purging package boost-multiprecision:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-multiprecision:x86-windows-static-md-v142-sdk81: 105.7 ms
Starting package 228/628: boost-atomic:x86-windows-static-md-v142-sdk81
Removing package boost-atomic:x86-windows-static-md-v142-sdk81...
Removing package boost-atomic:x86-windows-static-md-v142-sdk81... done
Purging package boost-atomic:x86-windows-static-md-v142-sdk81...
Purging package boost-atomic:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-atomic:x86-windows-static-md-v142-sdk81: 163.5 ms
Starting package 229/628: boost-lexical-cast:x64-windows-static-md-v142-sdk10b17134
Removing package boost-lexical-cast:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-lexical-cast:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-lexical-cast:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-lexical-cast:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-lexical-cast:x64-windows-static-md-v142-sdk10b17134: 51.06 ms
Starting package 230/628: boost-unordered:x64-windows-static-md-v142-sdk10b17134
Removing package boost-unordered:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-unordered:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-unordered:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-unordered:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-unordered:x64-windows-static-md-v142-sdk10b17134: 43.34 ms
Starting package 231/628: boost-container:x64-windows-static-md-v142-sdk10b17134
Removing package boost-container:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-container:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-container:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-container:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-container:x64-windows-static-md-v142-sdk10b17134: 146.7 ms
Starting package 232/628: boost-iostreams:x64-windows-static-md-v142-sdk10b17134
Removing package boost-iostreams:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-iostreams:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-iostreams:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-iostreams:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-iostreams:x64-windows-static-md-v142-sdk10b17134: 164.6 ms
Starting package 233/628: boost-qvm:x64-windows-static-md-v142-sdk10b17134
Removing package boost-qvm:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-qvm:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-qvm:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-qvm:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-qvm:x64-windows-static-md-v142-sdk10b17134: 130.4 ms
Starting package 234/628: boost-exception:x64-windows-static-md-v142-sdk10b17134
Removing package boost-exception:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-exception:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-exception:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-exception:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-exception:x64-windows-static-md-v142-sdk10b17134: 74.17 ms
Starting package 235/628: boost-foreach:x64-windows-static-md-v142-sdk10b17134
Removing package boost-foreach:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-foreach:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-foreach:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-foreach:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-foreach:x64-windows-static-md-v142-sdk10b17134: 36.45 ms
Starting package 236/628: boost-phoenix:x64-windows-static-md-v142-sdk10b17134
Removing package boost-phoenix:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-phoenix:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-phoenix:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-phoenix:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-phoenix:x64-windows-static-md-v142-sdk10b17134: 407.6 ms
Starting package 237/628: boost-proto:x64-windows-static-md-v142-sdk10b17134
Removing package boost-proto:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-proto:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-proto:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-proto:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-proto:x64-windows-static-md-v142-sdk10b17134: 187.5 ms
Starting package 238/628: boost-range:x64-windows-static-md-v142-sdk10b17134
Removing package boost-range:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-range:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-range:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-range:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-range:x64-windows-static-md-v142-sdk10b17134: 197.3 ms
Starting package 239/628: boost-regex:x64-windows-static-md-v142-sdk10b17134
Removing package boost-regex:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-regex:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-regex:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-regex:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-regex:x64-windows-static-md-v142-sdk10b17134: 102.5 ms
Starting package 240/628: boost-stacktrace:x64-windows-static-md-v142-sdk10b17134
Removing package boost-stacktrace:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-stacktrace:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-stacktrace:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-stacktrace:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-stacktrace:x64-windows-static-md-v142-sdk10b17134: 73.92 ms
Starting package 241/628: boost-build:x64-windows-static-md-v142-sdk10b17134
Removing package boost-build:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-build:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-build:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-build:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-build:x64-windows-static-md-v142-sdk10b17134: 1.186 s
Starting package 242/628: boost-lexical-cast:x86-windows-static-md-v142-sdk10b17134
Removing package boost-lexical-cast:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-lexical-cast:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-lexical-cast:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-lexical-cast:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-lexical-cast:x86-windows-static-md-v142-sdk10b17134: 52.76 ms
Starting package 243/628: boost-unordered:x86-windows-static-md-v142-sdk10b17134
Removing package boost-unordered:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-unordered:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-unordered:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-unordered:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-unordered:x86-windows-static-md-v142-sdk10b17134: 44.65 ms
Starting package 244/628: boost-container:x86-windows-static-md-v142-sdk10b17134
Removing package boost-container:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-container:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-container:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-container:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-container:x86-windows-static-md-v142-sdk10b17134: 150.4 ms
Starting package 245/628: boost-iostreams:x86-windows-static-md-v142-sdk10b17134
Removing package boost-iostreams:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-iostreams:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-iostreams:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-iostreams:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-iostreams:x86-windows-static-md-v142-sdk10b17134: 165.4 ms
Starting package 246/628: boost-qvm:x86-windows-static-md-v142-sdk10b17134
Removing package boost-qvm:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-qvm:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-qvm:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-qvm:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-qvm:x86-windows-static-md-v142-sdk10b17134: 133.6 ms
Starting package 247/628: boost-exception:x86-windows-static-md-v142-sdk10b17134
Removing package boost-exception:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-exception:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-exception:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-exception:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-exception:x86-windows-static-md-v142-sdk10b17134: 68.74 ms
Starting package 248/628: boost-foreach:x86-windows-static-md-v142-sdk10b17134
Removing package boost-foreach:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-foreach:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-foreach:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-foreach:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-foreach:x86-windows-static-md-v142-sdk10b17134: 40.93 ms
Starting package 249/628: boost-phoenix:x86-windows-static-md-v142-sdk10b17134
Removing package boost-phoenix:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-phoenix:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-phoenix:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-phoenix:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-phoenix:x86-windows-static-md-v142-sdk10b17134: 392.5 ms
Starting package 250/628: boost-proto:x86-windows-static-md-v142-sdk10b17134
Removing package boost-proto:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-proto:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-proto:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-proto:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-proto:x86-windows-static-md-v142-sdk10b17134: 183.1 ms
Starting package 251/628: boost-range:x86-windows-static-md-v142-sdk10b17134
Removing package boost-range:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-range:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-range:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-range:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-range:x86-windows-static-md-v142-sdk10b17134: 186.1 ms
Starting package 252/628: boost-regex:x86-windows-static-md-v142-sdk10b17134
Removing package boost-regex:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-regex:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-regex:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-regex:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-regex:x86-windows-static-md-v142-sdk10b17134: 103.2 ms
Starting package 253/628: boost-stacktrace:x86-windows-static-md-v142-sdk10b17134
Removing package boost-stacktrace:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-stacktrace:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-stacktrace:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-stacktrace:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-stacktrace:x86-windows-static-md-v142-sdk10b17134: 75.86 ms
Starting package 254/628: boost-system:x86-windows-static-md-v142-sdk10b17134
Removing package boost-system:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-system:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-system:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-system:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-system:x86-windows-static-md-v142-sdk10b17134: 57.64 ms
Starting package 255/628: boost-build:x86-windows-static-md-v142-sdk10b17134
Removing package boost-build:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-build:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-build:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-build:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-build:x86-windows-static-md-v142-sdk10b17134: 1.159 s
Starting package 256/628: boost-lexical-cast:x64-windows-static-md-v142-sdk81
Removing package boost-lexical-cast:x64-windows-static-md-v142-sdk81...
Removing package boost-lexical-cast:x64-windows-static-md-v142-sdk81... done
Purging package boost-lexical-cast:x64-windows-static-md-v142-sdk81...
Purging package boost-lexical-cast:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-lexical-cast:x64-windows-static-md-v142-sdk81: 53.23 ms
Starting package 257/628: boost-unordered:x64-windows-static-md-v142-sdk81
Removing package boost-unordered:x64-windows-static-md-v142-sdk81...
Removing package boost-unordered:x64-windows-static-md-v142-sdk81... done
Purging package boost-unordered:x64-windows-static-md-v142-sdk81...
Purging package boost-unordered:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-unordered:x64-windows-static-md-v142-sdk81: 50.09 ms
Starting package 258/628: boost-container:x64-windows-static-md-v142-sdk81
Removing package boost-container:x64-windows-static-md-v142-sdk81...
Removing package boost-container:x64-windows-static-md-v142-sdk81... done
Purging package boost-container:x64-windows-static-md-v142-sdk81...
Purging package boost-container:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-container:x64-windows-static-md-v142-sdk81: 150.7 ms
Starting package 259/628: boost-qvm:x64-windows-static-md-v142-sdk81
Removing package boost-qvm:x64-windows-static-md-v142-sdk81...
Removing package boost-qvm:x64-windows-static-md-v142-sdk81... done
Purging package boost-qvm:x64-windows-static-md-v142-sdk81...
Purging package boost-qvm:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-qvm:x64-windows-static-md-v142-sdk81: 131.4 ms
Starting package 260/628: boost-exception:x64-windows-static-md-v142-sdk81
Removing package boost-exception:x64-windows-static-md-v142-sdk81...
Removing package boost-exception:x64-windows-static-md-v142-sdk81... done
Purging package boost-exception:x64-windows-static-md-v142-sdk81...
Purging package boost-exception:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-exception:x64-windows-static-md-v142-sdk81: 73.6 ms
Starting package 261/628: boost-nowide:x64-windows-static-md-v142-sdk81
Removing package boost-nowide:x64-windows-static-md-v142-sdk81...
Removing package boost-nowide:x64-windows-static-md-v142-sdk81... done
Purging package boost-nowide:x64-windows-static-md-v142-sdk81...
Purging package boost-nowide:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-nowide:x64-windows-static-md-v142-sdk81: 57.88 ms
Starting package 262/628: boost-gil:x64-windows-static-md-v142-sdk81
Removing package boost-gil:x64-windows-static-md-v142-sdk81...
Removing package boost-gil:x64-windows-static-md-v142-sdk81... done
Purging package boost-gil:x64-windows-static-md-v142-sdk81...
Purging package boost-gil:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-gil:x64-windows-static-md-v142-sdk81: 259.6 ms
Starting package 263/628: boost-filesystem:x64-windows-static-md-v142-sdk81
Removing package boost-filesystem:x64-windows-static-md-v142-sdk81...
Removing package boost-filesystem:x64-windows-static-md-v142-sdk81... done
Purging package boost-filesystem:x64-windows-static-md-v142-sdk81...
Purging package boost-filesystem:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-filesystem:x64-windows-static-md-v142-sdk81: 57.73 ms
Starting package 264/628: boost-foreach:x64-windows-static-md-v142-sdk81
Removing package boost-foreach:x64-windows-static-md-v142-sdk81...
Removing package boost-foreach:x64-windows-static-md-v142-sdk81... done
Purging package boost-foreach:x64-windows-static-md-v142-sdk81...
Purging package boost-foreach:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-foreach:x64-windows-static-md-v142-sdk81: 36.69 ms
Starting package 265/628: boost-phoenix:x64-windows-static-md-v142-sdk81
Removing package boost-phoenix:x64-windows-static-md-v142-sdk81...
Removing package boost-phoenix:x64-windows-static-md-v142-sdk81... done
Purging package boost-phoenix:x64-windows-static-md-v142-sdk81...
Purging package boost-phoenix:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-phoenix:x64-windows-static-md-v142-sdk81: 396.5 ms
Starting package 266/628: boost-proto:x64-windows-static-md-v142-sdk81
Removing package boost-proto:x64-windows-static-md-v142-sdk81...
Removing package boost-proto:x64-windows-static-md-v142-sdk81... done
Purging package boost-proto:x64-windows-static-md-v142-sdk81...
Purging package boost-proto:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-proto:x64-windows-static-md-v142-sdk81: 207.5 ms
Starting package 267/628: boost-range:x64-windows-static-md-v142-sdk81
Removing package boost-range:x64-windows-static-md-v142-sdk81...
Removing package boost-range:x64-windows-static-md-v142-sdk81... done
Purging package boost-range:x64-windows-static-md-v142-sdk81...
Purging package boost-range:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-range:x64-windows-static-md-v142-sdk81: 191.2 ms
Starting package 268/628: boost-regex:x64-windows-static-md-v142-sdk81
Removing package boost-regex:x64-windows-static-md-v142-sdk81...
Removing package boost-regex:x64-windows-static-md-v142-sdk81... done
Purging package boost-regex:x64-windows-static-md-v142-sdk81...
Purging package boost-regex:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-regex:x64-windows-static-md-v142-sdk81: 283.6 ms
Starting package 269/628: boost-stacktrace:x64-windows-static-md-v142-sdk81
Removing package boost-stacktrace:x64-windows-static-md-v142-sdk81...
Removing package boost-stacktrace:x64-windows-static-md-v142-sdk81... done
Purging package boost-stacktrace:x64-windows-static-md-v142-sdk81...
Purging package boost-stacktrace:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-stacktrace:x64-windows-static-md-v142-sdk81: 72.55 ms
Starting package 270/628: boost-system:x64-windows-static-md-v142-sdk81
Removing package boost-system:x64-windows-static-md-v142-sdk81...
Removing package boost-system:x64-windows-static-md-v142-sdk81... done
Purging package boost-system:x64-windows-static-md-v142-sdk81...
Purging package boost-system:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-system:x64-windows-static-md-v142-sdk81: 55.86 ms
Starting package 271/628: boost-build:x64-windows-static-md-v142-sdk81
Removing package boost-build:x64-windows-static-md-v142-sdk81...
Removing package boost-build:x64-windows-static-md-v142-sdk81... done
Purging package boost-build:x64-windows-static-md-v142-sdk81...
Purging package boost-build:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-build:x64-windows-static-md-v142-sdk81: 1.061 s
Starting package 272/628: boost-lexical-cast:x86-windows-static-md-v142-sdk81
Removing package boost-lexical-cast:x86-windows-static-md-v142-sdk81...
Removing package boost-lexical-cast:x86-windows-static-md-v142-sdk81... done
Purging package boost-lexical-cast:x86-windows-static-md-v142-sdk81...
Purging package boost-lexical-cast:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-lexical-cast:x86-windows-static-md-v142-sdk81: 53.87 ms
Starting package 273/628: boost-unordered:x86-windows-static-md-v142-sdk81
Removing package boost-unordered:x86-windows-static-md-v142-sdk81...
Removing package boost-unordered:x86-windows-static-md-v142-sdk81... done
Purging package boost-unordered:x86-windows-static-md-v142-sdk81...
Purging package boost-unordered:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-unordered:x86-windows-static-md-v142-sdk81: 44.63 ms
Starting package 274/628: boost-container:x86-windows-static-md-v142-sdk81
Removing package boost-container:x86-windows-static-md-v142-sdk81...
Removing package boost-container:x86-windows-static-md-v142-sdk81... done
Purging package boost-container:x86-windows-static-md-v142-sdk81...
Purging package boost-container:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-container:x86-windows-static-md-v142-sdk81: 163.9 ms
Starting package 275/628: boost-iostreams:x86-windows-static-md-v142-sdk81
Removing package boost-iostreams:x86-windows-static-md-v142-sdk81...
Removing package boost-iostreams:x86-windows-static-md-v142-sdk81... done
Purging package boost-iostreams:x86-windows-static-md-v142-sdk81...
Purging package boost-iostreams:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-iostreams:x86-windows-static-md-v142-sdk81: 166.7 ms
Starting package 276/628: boost-qvm:x86-windows-static-md-v142-sdk81
Removing package boost-qvm:x86-windows-static-md-v142-sdk81...
Removing package boost-qvm:x86-windows-static-md-v142-sdk81... done
Purging package boost-qvm:x86-windows-static-md-v142-sdk81...
Purging package boost-qvm:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-qvm:x86-windows-static-md-v142-sdk81: 130.6 ms
Starting package 277/628: boost-exception:x86-windows-static-md-v142-sdk81
Removing package boost-exception:x86-windows-static-md-v142-sdk81...
Removing package boost-exception:x86-windows-static-md-v142-sdk81... done
Purging package boost-exception:x86-windows-static-md-v142-sdk81...
Purging package boost-exception:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-exception:x86-windows-static-md-v142-sdk81: 68.55 ms
Starting package 278/628: boost-nowide:x86-windows-static-md-v142-sdk81
Removing package boost-nowide:x86-windows-static-md-v142-sdk81...
Removing package boost-nowide:x86-windows-static-md-v142-sdk81... done
Purging package boost-nowide:x86-windows-static-md-v142-sdk81...
Purging package boost-nowide:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-nowide:x86-windows-static-md-v142-sdk81: 57.49 ms
Starting package 279/628: boost-gil:x86-windows-static-md-v142-sdk81
Removing package boost-gil:x86-windows-static-md-v142-sdk81...
Removing package boost-gil:x86-windows-static-md-v142-sdk81... done
Purging package boost-gil:x86-windows-static-md-v142-sdk81...
Purging package boost-gil:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-gil:x86-windows-static-md-v142-sdk81: 258.2 ms
Starting package 280/628: boost-filesystem:x86-windows-static-md-v142-sdk81
Removing package boost-filesystem:x86-windows-static-md-v142-sdk81...
Removing package boost-filesystem:x86-windows-static-md-v142-sdk81... done
Purging package boost-filesystem:x86-windows-static-md-v142-sdk81...
Purging package boost-filesystem:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-filesystem:x86-windows-static-md-v142-sdk81: 57.01 ms
Starting package 281/628: boost-foreach:x86-windows-static-md-v142-sdk81
Removing package boost-foreach:x86-windows-static-md-v142-sdk81...
Removing package boost-foreach:x86-windows-static-md-v142-sdk81... done
Purging package boost-foreach:x86-windows-static-md-v142-sdk81...
Purging package boost-foreach:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-foreach:x86-windows-static-md-v142-sdk81: 37.44 ms
Starting package 282/628: boost-phoenix:x86-windows-static-md-v142-sdk81
Removing package boost-phoenix:x86-windows-static-md-v142-sdk81...
Removing package boost-phoenix:x86-windows-static-md-v142-sdk81... done
Purging package boost-phoenix:x86-windows-static-md-v142-sdk81...
Purging package boost-phoenix:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-phoenix:x86-windows-static-md-v142-sdk81: 401.8 ms
Starting package 283/628: boost-proto:x86-windows-static-md-v142-sdk81
Removing package boost-proto:x86-windows-static-md-v142-sdk81...
Removing package boost-proto:x86-windows-static-md-v142-sdk81... done
Purging package boost-proto:x86-windows-static-md-v142-sdk81...
Purging package boost-proto:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-proto:x86-windows-static-md-v142-sdk81: 199.1 ms
Starting package 284/628: boost-range:x86-windows-static-md-v142-sdk81
Removing package boost-range:x86-windows-static-md-v142-sdk81...
Removing package boost-range:x86-windows-static-md-v142-sdk81... done
Purging package boost-range:x86-windows-static-md-v142-sdk81...
Purging package boost-range:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-range:x86-windows-static-md-v142-sdk81: 200 ms
Starting package 285/628: boost-regex:x86-windows-static-md-v142-sdk81
Removing package boost-regex:x86-windows-static-md-v142-sdk81...
Removing package boost-regex:x86-windows-static-md-v142-sdk81... done
Purging package boost-regex:x86-windows-static-md-v142-sdk81...
Purging package boost-regex:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-regex:x86-windows-static-md-v142-sdk81: 103.8 ms
Starting package 286/628: boost-stacktrace:x86-windows-static-md-v142-sdk81
Removing package boost-stacktrace:x86-windows-static-md-v142-sdk81...
Removing package boost-stacktrace:x86-windows-static-md-v142-sdk81... done
Purging package boost-stacktrace:x86-windows-static-md-v142-sdk81...
Purging package boost-stacktrace:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-stacktrace:x86-windows-static-md-v142-sdk81: 74.14 ms
Starting package 287/628: boost-system:x86-windows-static-md-v142-sdk81
Removing package boost-system:x86-windows-static-md-v142-sdk81...
Removing package boost-system:x86-windows-static-md-v142-sdk81... done
Purging package boost-system:x86-windows-static-md-v142-sdk81...
Purging package boost-system:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-system:x86-windows-static-md-v142-sdk81: 54.85 ms
Starting package 288/628: boost-build:x86-windows-static-md-v142-sdk81
Removing package boost-build:x86-windows-static-md-v142-sdk81...
Removing package boost-build:x86-windows-static-md-v142-sdk81... done
Purging package boost-build:x86-windows-static-md-v142-sdk81...
Purging package boost-build:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-build:x86-windows-static-md-v142-sdk81: 1.148 s
Starting package 289/628: boost-modular-build-helper:x64-windows-static-md-v142-sdk81
Removing package boost-modular-build-helper:x64-windows-static-md-v142-sdk81...
Removing package boost-modular-build-helper:x64-windows-static-md-v142-sdk81... done
Purging package boost-modular-build-helper:x64-windows-static-md-v142-sdk81...
Purging package boost-modular-build-helper:x64-windows-static-md-v142-sdk81... done
Elapsed time for package boost-modular-build-helper:x64-windows-static-md-v142-sdk81: 40.51 ms
Starting package 290/628: python3:x64-windows-static-md-v142-sdk81
Removing package python3:x64-windows-static-md-v142-sdk81...
Removing package python3:x64-windows-static-md-v142-sdk81... done
Purging package python3:x64-windows-static-md-v142-sdk81...
Purging package python3:x64-windows-static-md-v142-sdk81... done
Elapsed time for package python3:x64-windows-static-md-v142-sdk81: 2.439 s
Starting package 291/628: openssl:x64-windows-static-md-v142-sdk81
Removing package openssl:x64-windows-static-md-v142-sdk81...
Removing package openssl:x64-windows-static-md-v142-sdk81... done
Purging package openssl:x64-windows-static-md-v142-sdk81...
Purging package openssl:x64-windows-static-md-v142-sdk81... done
Elapsed time for package openssl:x64-windows-static-md-v142-sdk81: 35.95 ms
Starting package 292/628: openssl-windows:x64-windows-static-md-v142-sdk81
Removing package openssl-windows:x64-windows-static-md-v142-sdk81...
Removing package openssl-windows:x64-windows-static-md-v142-sdk81... done
Purging package openssl-windows:x64-windows-static-md-v142-sdk81...
Purging package openssl-windows:x64-windows-static-md-v142-sdk81... done
Elapsed time for package openssl-windows:x64-windows-static-md-v142-sdk81: 161.7 ms
Starting package 293/628: cpprestsdk:x64-windows-static-md-v142-sdk10b17134
Removing package cpprestsdk:x64-windows-static-md-v142-sdk10b17134...
Removing package cpprestsdk:x64-windows-static-md-v142-sdk10b17134... done
Purging package cpprestsdk:x64-windows-static-md-v142-sdk10b17134...
Purging package cpprestsdk:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package cpprestsdk:x64-windows-static-md-v142-sdk10b17134: 138.5 ms
Starting package 294/628: boost-modular-build-helper:x86-windows-static-md-v142-sdk10b17134
Removing package boost-modular-build-helper:x86-windows-static-md-v142-sdk10b17134...
Removing package boost-modular-build-helper:x86-windows-static-md-v142-sdk10b17134... done
Purging package boost-modular-build-helper:x86-windows-static-md-v142-sdk10b17134...
Purging package boost-modular-build-helper:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-modular-build-helper:x86-windows-static-md-v142-sdk10b17134: 38.37 ms
Starting package 295/628: boost-modular-build-helper:x64-windows-static-md-v142-sdk10b17134
Removing package boost-modular-build-helper:x64-windows-static-md-v142-sdk10b17134...
Removing package boost-modular-build-helper:x64-windows-static-md-v142-sdk10b17134... done
Purging package boost-modular-build-helper:x64-windows-static-md-v142-sdk10b17134...
Purging package boost-modular-build-helper:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package boost-modular-build-helper:x64-windows-static-md-v142-sdk10b17134: 40.59 ms
Starting package 296/628: boost-modular-build-helper:x86-windows-static-md-v142-sdk81
Removing package boost-modular-build-helper:x86-windows-static-md-v142-sdk81...
Removing package boost-modular-build-helper:x86-windows-static-md-v142-sdk81... done
Purging package boost-modular-build-helper:x86-windows-static-md-v142-sdk81...
Purging package boost-modular-build-helper:x86-windows-static-md-v142-sdk81... done
Elapsed time for package boost-modular-build-helper:x86-windows-static-md-v142-sdk81: 34.1 ms
Starting package 297/628: cpprestsdk:x64-windows-static-md-v142-sdk81
Removing package cpprestsdk:x64-windows-static-md-v142-sdk81...
Removing package cpprestsdk:x64-windows-static-md-v142-sdk81... done
Purging package cpprestsdk:x64-windows-static-md-v142-sdk81...
Purging package cpprestsdk:x64-windows-static-md-v142-sdk81... done
Elapsed time for package cpprestsdk:x64-windows-static-md-v142-sdk81: 137.3 ms
Starting package 298/628: cpprestsdk:x86-windows-static-md-v142-sdk10b17134
Removing package cpprestsdk:x86-windows-static-md-v142-sdk10b17134...
Removing package cpprestsdk:x86-windows-static-md-v142-sdk10b17134... done
Purging package cpprestsdk:x86-windows-static-md-v142-sdk10b17134...
Purging package cpprestsdk:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package cpprestsdk:x86-windows-static-md-v142-sdk10b17134: 128.8 ms
Starting package 299/628: opencv4:x86-windows-static-md-v142-sdk10b17134
Removing package opencv4:x86-windows-static-md-v142-sdk10b17134...
Removing package opencv4:x86-windows-static-md-v142-sdk10b17134... done
Purging package opencv4:x86-windows-static-md-v142-sdk10b17134...
Purging package opencv4:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package opencv4:x86-windows-static-md-v142-sdk10b17134: 742.1 ms
Starting package 300/628: protobuf:x86-windows-static-md-v142-sdk10b17134
Removing package protobuf:x86-windows-static-md-v142-sdk10b17134...
Removing package protobuf:x86-windows-static-md-v142-sdk10b17134... done
Purging package protobuf:x86-windows-static-md-v142-sdk10b17134...
Purging package protobuf:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package protobuf:x86-windows-static-md-v142-sdk10b17134: 202.5 ms
Starting package 301/628: cpprestsdk:x86-windows-static-md-v142-sdk81
Removing package cpprestsdk:x86-windows-static-md-v142-sdk81...
Removing package cpprestsdk:x86-windows-static-md-v142-sdk81... done
Purging package cpprestsdk:x86-windows-static-md-v142-sdk81...
Purging package cpprestsdk:x86-windows-static-md-v142-sdk81... done
Elapsed time for package cpprestsdk:x86-windows-static-md-v142-sdk81: 130.8 ms
Starting package 302/628: opencv4:x64-windows-static-md-v142-sdk10b17134
Removing package opencv4:x64-windows-static-md-v142-sdk10b17134...
Removing package opencv4:x64-windows-static-md-v142-sdk10b17134... done
Purging package opencv4:x64-windows-static-md-v142-sdk10b17134...
Purging package opencv4:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package opencv4:x64-windows-static-md-v142-sdk10b17134: 879.3 ms
Starting package 303/628: hdf5:x64-windows-static-md-v142-sdk10b17134
Removing package hdf5:x64-windows-static-md-v142-sdk10b17134...
Removing package hdf5:x64-windows-static-md-v142-sdk10b17134... done
Purging package hdf5:x64-windows-static-md-v142-sdk10b17134...
Purging package hdf5:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package hdf5:x64-windows-static-md-v142-sdk10b17134: 125.2 ms
Starting package 304/628: hdf5:x86-windows-static-md-v142-sdk10b17134
Removing package hdf5:x86-windows-static-md-v142-sdk10b17134...
Removing package hdf5:x86-windows-static-md-v142-sdk10b17134... done
Purging package hdf5:x86-windows-static-md-v142-sdk10b17134...
Purging package hdf5:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package hdf5:x86-windows-static-md-v142-sdk10b17134: 131.7 ms
Starting package 305/628: python3:x64-windows-static-md-v142-sdk10b17134
Removing package python3:x64-windows-static-md-v142-sdk10b17134...
Removing package python3:x64-windows-static-md-v142-sdk10b17134... done
Purging package python3:x64-windows-static-md-v142-sdk10b17134...
Purging package python3:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package python3:x64-windows-static-md-v142-sdk10b17134: 2.765 s
Starting package 306/628: openssl:x64-windows-static-md-v142-sdk10b17134
Removing package openssl:x64-windows-static-md-v142-sdk10b17134...
Removing package openssl:x64-windows-static-md-v142-sdk10b17134... done
Purging package openssl:x64-windows-static-md-v142-sdk10b17134...
Purging package openssl:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package openssl:x64-windows-static-md-v142-sdk10b17134: 31.77 ms
Starting package 307/628: python3:x86-windows-static-md-v142-sdk10b17134
Removing package python3:x86-windows-static-md-v142-sdk10b17134...
Removing package python3:x86-windows-static-md-v142-sdk10b17134... done
Purging package python3:x86-windows-static-md-v142-sdk10b17134...
Purging package python3:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package python3:x86-windows-static-md-v142-sdk10b17134: 2.5 s
Starting package 308/628: openssl:x86-windows-static-md-v142-sdk10b17134
Removing package openssl:x86-windows-static-md-v142-sdk10b17134...
Removing package openssl:x86-windows-static-md-v142-sdk10b17134... done
Purging package openssl:x86-windows-static-md-v142-sdk10b17134...
Purging package openssl:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package openssl:x86-windows-static-md-v142-sdk10b17134: 38.97 ms
Starting package 309/628: python3:x86-windows-static-md-v142-sdk81
Removing package python3:x86-windows-static-md-v142-sdk81...
Removing package python3:x86-windows-static-md-v142-sdk81... done
Purging package python3:x86-windows-static-md-v142-sdk81...
Purging package python3:x86-windows-static-md-v142-sdk81... done
Elapsed time for package python3:x86-windows-static-md-v142-sdk81: 2.878 s
Starting package 310/628: openssl:x86-windows-static-md-v142-sdk81
Removing package openssl:x86-windows-static-md-v142-sdk81...
Removing package openssl:x86-windows-static-md-v142-sdk81... done
Purging package openssl:x86-windows-static-md-v142-sdk81...
Purging package openssl:x86-windows-static-md-v142-sdk81... done
Elapsed time for package openssl:x86-windows-static-md-v142-sdk81: 34.97 ms
Starting package 311/628: openssl-windows:x64-windows-static-md-v142-sdk10b17134
Removing package openssl-windows:x64-windows-static-md-v142-sdk10b17134...
Removing package openssl-windows:x64-windows-static-md-v142-sdk10b17134... done
Purging package openssl-windows:x64-windows-static-md-v142-sdk10b17134...
Purging package openssl-windows:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package openssl-windows:x64-windows-static-md-v142-sdk10b17134: 171.7 ms
Starting package 312/628: openssl-windows:x86-windows-static-md-v142-sdk10b17134
Removing package openssl-windows:x86-windows-static-md-v142-sdk10b17134...
Removing package openssl-windows:x86-windows-static-md-v142-sdk10b17134... done
Purging package openssl-windows:x86-windows-static-md-v142-sdk10b17134...
Purging package openssl-windows:x86-windows-static-md-v142-sdk10b17134... done
Elapsed time for package openssl-windows:x86-windows-static-md-v142-sdk10b17134: 186.2 ms
Starting package 313/628: openssl-windows:x86-windows-static-md-v142-sdk81
Removing package openssl-windows:x86-windows-static-md-v142-sdk81...
Removing package openssl-windows:x86-windows-static-md-v142-sdk81... done
Purging package openssl-windows:x86-windows-static-md-v142-sdk81...
Purging package openssl-windows:x86-windows-static-md-v142-sdk81... done
Elapsed time for package openssl-windows:x86-windows-static-md-v142-sdk81: 170 ms
Starting package 314/628: protobuf:x64-windows-static-md-v142-sdk10b17134
Removing package protobuf:x64-windows-static-md-v142-sdk10b17134...
Removing package protobuf:x64-windows-static-md-v142-sdk10b17134... done
Purging package protobuf:x64-windows-static-md-v142-sdk10b17134...
Purging package protobuf:x64-windows-static-md-v142-sdk10b17134... done
Elapsed time for package protobuf:x64-windows-static-md-v142-sdk10b17134: 196.9 ms
Starting package 315/628: boost-build:x86-windows-static-md-v142-sdk10b17134
Building package boost-build[core]:x86-windows-static-md-v142-sdk10b17134...
-- Using community triplet x86-windows-static-md-v142-sdk10b17134. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: C:\njs\vcpkg\triplets\community\x86-windows-static-md-v142-sdk10b17134.cmake
CMake Error at scripts/ports.cmake:14 (message):
          Your vcpkg executable is outdated and is not compatible with the current CMake scripts.
          Please re-build vcpkg by running bootstrap-vcpkg.



Error: Building package boost-build:x86-windows-static-md-v142-sdk10b17134 failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: boost-build:x86-windows-static-md-v142-sdk10b17134
  Vcpkg version: 2020.02.04-nohash-external

Additionally, attach any relevant sections from the log files above.

</details>

Expected

Rebuild of the ~300 packages. No errors.

Failure logs

As you can see, no specific failure log was indicated in the build failure. In buildtrees/boost-build there are two files with a date similar to now. They are attached.
stdout-x86-windows-static-md-v142-sdk10b17134.log x86-windows-static-md-v142-sdk10b17134.vcpkg_abi_info.txt

Comments

I am unsure if the problem is exactly Your vcpkg executable is outdated and is not compatible with the current CMake scripts. Please re-build vcpkg by running bootstrap-vcpkg. After writing this issue, I will try that.

However, if that is the superficial problem, then the issue underlying that is that vcpkg upgrade did not check all its dependencies before destructively altering the system. Meaning, vcpkg failed to check its own version dependency before making ~300 purges of packages. Waiting to check its own version until after hundreds of purges results in demolished libraries and no easy way to re-populate it. Like a building contractor that is hired to rebuild a home, demolishes the home, and only after that tells the owner..."oh, I'm not qualified to rebuild your home". Owner says, "But you knew that at the beginning...why did you demolish my home?!"

But maybe that's not the underlying issue. Or is it? 🎲

created time in 2 days

push eventdiablodale/dp.kinect2

Dale Phurrough

commit sha 27e6a36c00fb84c97f2607a1ee30e6c3fbcb7427

add download link

view details

push time in 4 days

issue commentdiablodale/dp.kinect2

Registration stopped working; @verbose=1 output shows RG: 167772160

The just released v1.2 of dp.kinect2 includes client-side changes to better handle the specific catastrophic AWS failure that occurred on this date. (Server-side changes have been in place for a few years.) You can download it from https://hidale.com/shop/dp-kinect2/

emm-ess

comment created time in 4 days

GollumEvent
GollumEvent

issue openedMicrosoftDocs/feedback

Kinect 2.0 content broken/missing with "Error Sorry, this page is unavailable. Please try again later."

Kinect content is broken/missing on many links. Below I list several. I recommend a tester use a web crawler to automate the testing of live content to find all the problems. This is related to issue #1214

Setup

  • Windows 10 x64 build 19041.329
  • Chrome 83.0.4103.116

Repro

  1. Visit https://docs.microsoft.com/en-us/previous-versions/windows/kinect/dn772957(v=ieb.10)
  2. scroll down to the method GetActivityDetectionResults
  3. Click on GetActivityDetectionResults

Result

"Error Sorry, this page is unavailable. Please try again later." Using developer tools, I can see your server is throwing http error 500 on this page.

Expected

Content with no error.

More errors, and workaround

More links and the content on that page have the same errors. This following is a short list manually found: GetAppearanceDetectionResults GetExpressionDetectionResults GetJointOrientations GetJoints

As a workaround, I can click on the Download PDF link in the left nav, and within the PDF I can read the missing content.

created time in 4 days

push eventdiablodale/dp.kinect2

Dale Phurrough

commit sha 861aab8fd13a10de585399adb3dbdcada7d730b3

Update README.md

view details

push time in 5 days

GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent
GollumEvent

issue closeddiablodale/dp.kinect2

expose the license serial number via a message or attribute

Perhaps expose the license serial number for a current registration of dp.kinect2. This would allow a customer to know "what license did I use to register on this machine?" Unsure if there is a large benefit for this. Need more use cases. As comparison, Windows doesn't provide this type of feature.

closed time in 5 days

diablodale

issue commentdiablodale/dp.kinect2

expose the license serial number via a message or attribute

I've released the v1.2 feature update to include this idea. Available to download at the usual locations like https://hidale.com/shop/dp-kinect2/

diablodale

comment created time in 5 days

issue closeddiablodale/dp.kinect2

unregister/moving license dp.kinect2 problems

Setup computer i7 6700 cpu , 250 gb ssd 32 gb ram ddr4 2400 Windows 10 pro Installed Kinect 2.0 Public Preview SDK Installed Max 7.3.5 x64 and it is registered Using dp.kinect2 version 1.1

I want to remove the registry of this computer to use it in a new computer, but although it confirms to me that the registry has been removed it does not arrive it to realize and I can not authorize the new computer. The features of the new computer are:

zotac model in 1060k, cpu i5 7500, ram 16 gb ddr4 2400, ssd 250 gb. Gpu zotac nvidia 1060.

version of max msp 7.3.5 x64 authorized.

using dp.kinect2 version 1.1

captura captura2 captura3

closed time in 5 days

circasu

issue commentdiablodale/dp.kinect2

unregister/moving license dp.kinect2 problems

I've released the v1.2 feature update to resolve this issue directly in the code. Available to download at the usual locations like https://hidale.com/shop/dp-kinect2/

circasu

comment created time in 5 days

issue closeddiablodale/dp.kinect2

get skeleton joints to color coordinates (x,y)

Hi,

I've some problems to properly project datas (Skeleton joints) on top of the color and depth streams One solution i guess could be to convert the skeleton joints to color coordinates (x,y) Is there any technic to do this?

i've seen Microsoft sdk provide CoordinateMapper for that : CoordinateMapper’s job is to identify whether a point from the 3D space corresponds to a point in the color or depth 2D space

Sadly i'm only a maxer and can't use this CoordinateMapper ... Maybe you've a solution? Thank you very much Mathieu

closed time in 5 days

silicatproject

issue commentdiablodale/dp.kinect2

get skeleton joints to color coordinates (x,y)

I've released the v1.2 feature update to include these ideas. Available to download at the usual locations like https://hidale.com/shop/dp-kinect2/

silicatproject

comment created time in 5 days

GollumEvent
GollumEvent
GollumEvent
GollumEvent

issue openedCycling74/max-sdk

max_jit_class_wrap_addmethods() -or- exposing jitter methods to max wrapper (late stage)

What is the behavior of max_jit_class_wrap_addmethods()? Can I call it multiple times with no harm?

My need is to add methods to a jitter object that is exposed to Max via a max wrapper object. And these methods are to be added after the call to max_jit_class_wrap_standard()

Trial/error/reading header files I found max_jit_class_wrap_addmethods() and it seems to do what I want. Though I am unclear as to its full behavior and if there are negative sideaffects if called multiple times; once after each time I add a method to the jitter class.

Is there a API to cause the max wrapper to see this single new jitter method without (re)parsing all methods in bulk as I'm guessing max_jit_class_wrap_addmethods() does?

After this example is clarified, would be good to add documentation for this function and the others in related doc issues #20

created time in 13 days

startedcoreruleset/coreruleset

started time in 23 days

issue openedmicrosoft/Azure-Kinect-Sensor-SDK

Kinect data on GPU with `gpu::GpuMat`, `ogl::Buffer`, `ogl::Texture2D`, or OpenGL handles

Add access to Kinect data via cv::gpu::GpuMat, ogl::Buffer, cv::ogl::Texture2D, and/or OpenGL handles to keep data on GPU and greatly reduce GPU<->CPU memory churn for image processing, computation, etc. As I read the code today, almost all work by this SDK codebase is done on the CPU. (depthengine is not part of this SDK codebase)

For the same reasons that depthengine is written for GPU usage...our apps need to use the GPU. Developers on tiny industrial platforms up to workstations need the Kinect data to stay on the GPU to scale across the variety of computing platforms. Forcing download of all frames to CPU is outdated 👴 and wastes resources of gpu, cpu, power, and thermal budget.

Examples

OpenCV provides cv::gpu::GpuMat as one container for data kept in GPU memory. Two others are ogl::Buffer and cv::ogl::Texture2D. If depthengine via this SDK exposed Kinect data in such containers, it would allow easy usage in OpenCV and libraries using OpenCV interfaces. In addition, data can be downloaded GPU->CPU at any time with single lines of code cv::gpu::GpuMat::download().

auto image = k4a_capture_get_color_image(capture);
cv::gpu::GpuMat sourceOnGpu = k4a_image_get_gpumat(image);
cv::gpu::GpuMat resultOnGpu;
cv::gpu::threshold(sourceOnGpu, resultOnGpu, 128.0, 255.0, CV_THRESH_BINARY);

cv::Mat resultSlowCpuMem;
resultOnGpu.download(resultSlowCpuMem);  // <-- only here do we request data move from GPU->CPU

Or imagine depthengine exposes the data in a capture collection of OpenGL handles to shared textures, pbo, etc. And enabling dirextx/opengl texture sharing as needed for depthengine. This would allow the following pseudocode. Note: in this pseudocode zero image data was copied from GPU->CPU memory.

auto capture = k4a_get_capture();
auto image = k4a_capture_get_color_image(capture);
auto glTexture = k4a_image_get_buffer(image);
myShader.use();
myShader.setInt("texture1", glTexture);
myShader.run();

Savings

The memory savings, cpu savings, and cache churn is gigantic. For example, every NV12 4k frame is approximately 12MB of data. At 30fps that is approximately 365 MB every second and invalidating large chunks of the L1-3 CPU cache. And worse...in today's apps that must process data with GPUs this number is doubled. Why? Because depthengine forces download to CPU and the very next line of code is an upload of that same data back to the GPU...

cv::gpu::GpuMat churnMemory(const k4a_image_t& image) {
  cv::gpu::GpuMat gpuMem;
  uint8_t * cpuMem = k4a_image_get_buffer(image); // download gpu->cpu
  gpuMem.upload(cpuMem); // duplicate resource waste cpu->gpu
  return gpuMem;
}

By keeping data on the GPU, 730MB every second is reduced to zero. Plus, it allows for efficient GPU processing of data when often the destination is the GPU.

Alternative

Currently none possible. All image data is forced to be copied to CPU memory. This SDK only exposes Kinect capture data via CPU memory using k4a_capture_get_depth_image(), k4a_capture_get_color_image(), or k4a_capture_get_ir_image(). Even the SDK examples do expensive GPU->CPU copies on every frame

https://github.com/microsoft/Azure-Kinect-Sensor-SDK/blob/aaddc09296731905ee775a1da30b95e06f7f6b97/examples/viewer/opengl/texture.cpp#L69-L77

created time in a month

issue openedwoocommerce/action-scheduler

wpcli `migrate` subcommand disappears after one use, help disappears, and not like `wp wc update`

migrate subcommand disappears after one use, its help disappears, and it behaves differently than commands like wp wc update.

https://github.com/woocommerce/action-scheduler/blob/f3a13eb9b5c9b1f06db1144caa219202c27deef6/classes/abstracts/ActionScheduler.php#L169-L172

Setup

  • Woo 4.2.0 which includes Ac 3.1.6
  • Also reproduces on current Ac master as linked above

Repo

  1. Install a complete Woo setup by command-line (not UI or webpages)
  2. wpcli action-scheduler migrate
  3. wpcli action-scheduler migrate

Result

Error and a non-zero exit code

Error: 'migrate' is not a registered subcommand of 'action-scheduler'. See 'wp help action-scheduler' for available subcommands.`

Further...when you follow those instructions to get help with wp help action-scheduler all help on it has vanished.

...
SUBCOMMANDS

  run      Run the Action Scheduler

GLOBAL PARAMETERS
...

Expected

No error and action scheduler should provide a friendly notice that no migrate/update is needed and note the current version. For example, this is the friendly notice (with exit code=0) that Woo provides when wp wc update is run:

Success: No updates required. Database version is 4.2.0

Also, complete help should always be available. When wp help action-scheduler is run, it should provide a list of all subcommands (including migrate) and help for them all.

created time in a month

issue commentmicrosoft/winget-cli

The *.appxbundle installer does not automatically add the installation directory for winget.exe to the PATH environment variable in Windows 10

Naturally, anything with write access (has nothing to do with an installer) to HKEY_CURRENT_USER\Environment key and value Path can change it from REG_EXPAND_SZ to REG_SZ.

I think it is reasonable for the infrastructure (Microsoft Store + Windows) to correctly check/set/install all needed dependencies when an app is installed via that store. Therefore...

  1. Since app aliases are part of the app's install
  2. App alias functionality depends on PATH being correctly configured to %USERPROFILE%\AppData\Local\Microsoft\WindowsApps

That would require the dependency of app aliases to do at a minimum

  1. make the alias in %USERPROFILE%\AppData\Local\Microsoft\WindowsApps
  2. ensure the PATH includes %USERPROFILE%\AppData\Local\Microsoft\WindowsApps
  3. ensure the PATH is REG_EXPAND_SZ. When it is only REG_SZ, then do the needed re/write of path back to REG_EXPAND_SZ

Seems to me the dependency handing of (Microsoft Store + Windows) is not doing steps 2 and 3. If the dependency handling is updated then it allows much...

  1. Bugs like this issue go away
  2. When something else changes REG_EXPAND_SZ to REG_SZ at any time, then one or more aliases will fail. However, then the user can use the standard Windows App->Repair/Reset. Since the improved dependency handling will include steps 2 and 3 above...and therefore fix the registry key back to REG_EXPAND_SZ
jwheeler88

comment created time in a month

issue commentmicrosoft/terminal

store installer sets wrong path, as literal ';%USERPROFILE%\AppData\Local\Microsoft\WindowsApps`

Naturally, anything with write access (has nothing to do with an installer) to HKEY_CURRENT_USER\Environment key and value Path can change it from REG_EXPAND_SZ to REG_SZ.

I think it is reasonable for the infrastructure (Microsoft Store + Windows) to correctly check/set/install all needed dependencies when an app is installed via that store. Therefore...

  1. Since app aliases are part of the app's install
  2. App alias functionality depends on PATH being correctly configured to %USERPROFILE%\AppData\Local\Microsoft\WindowsApps

That would require the dependency of app aliases to do at a minimum

  1. make the alias in %USERPROFILE%\AppData\Local\Microsoft\WindowsApps
  2. ensure the PATH includes %USERPROFILE%\AppData\Local\Microsoft\WindowsApps
  3. ensure the PATH is REG_EXPAND_SZ. When it is only REG_SZ, then do the needed re/write of path back to REG_EXPAND_SZ

Seems to me the dependency handing of (Microsoft Store + Windows) is not doing steps 2 and 3. If the dependency handling is updated then it allows much...

  1. Bugs like this issue go away
  2. When something else changes REG_EXPAND_SZ to REG_SZ at any time, then one or more aliases will fail. However, then the user can use the standard Windows App->Repair/Reset. Since the improved dependency handling will include steps 2 and 3 above...and therefore fix the registry key back to REG_EXPAND_SZ
diablodale

comment created time in a month

issue commentmicrosoft/vscode-cpptools

intellisense uses newest SDK instead of specified Win8.1

Win10 x64. Slightly changed since OP

Version: 1.45.1 (system setup)
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:27:35.169Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041

vscode is installed at C:\Program Files\Microsoft VS Code\Code.exe

As diagnostics, I used sysinternals process monitor and some querying and found cpptools.exe made 6 RegQueryValue to HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots\KitsRoot81 and all six times got the return Type: REG_SZ, Length: 82, Data: C:\Program Files (x86)\Windows Kits\8.1\. No other process accessed a key with the substring KitsRoot81. If some other process should have...it didn't.

I see two similar sequences, each querying for 81 and 10 yet different repeats. procmon1

diablodale

comment created time in a month

issue commentmicrosoft/winget-cli

The *.appxbundle installer does not automatically add the installation directory for winget.exe to the PATH environment variable in Windows 10

windows terminal is experiencing the same problem. They identified it as the store/centennial/appx install process for appexecutionalias is not fully specifying the path to the aliases and instead using a path with embedded %USERPROFILE%. However that fails because the PATH environment variable in the registry is REG_SZ and not REG_EXPAND_SZ. Therefore that variable reference is not expanded.

Can someone at Microsoft escalate this shared issue to the Microsoft team(s) responsible for that area?

jwheeler88

comment created time in a month

issue commentmicrosoft/terminal

store installer sets wrong path, as literal ';%USERPROFILE%\AppData\Local\Microsoft\WindowsApps`

Hi, it is true my HKEY_CURRENT_USER\Environment key has a value Path with a type of REG_SZ.

This installation bug with store/centennial/appx is I think related to the appExecutionAlias and how it is managed with the installer, store, and Win10.

winget is experiencing the same problem. https://github.com/microsoft/winget-cli/issues/210

diablodale

comment created time in a month

issue commentmicrosoft/terminal

store installer sets wrong path, as literal ';%USERPROFILE%\AppData\Local\Microsoft\WindowsApps`

  • the Windows Terminal execution alias is present and turned on. This was its state after install, I made no changes.
  • C:\Users\dale\AppData\Local\Microsoft\WindowsApps\wt.exe is present and I can run it successfully if I use the full path at a prompt or windowskey-R.
diablodale

comment created time in a month

issue openedmicrosoft/terminal

store installer sets wrong path, as literal ';%USERPROFILE%\AppData\Local\Microsoft\WindowsApps`

Windows store installer for v1.0.1401.0 appends wrong value to path. Therefore, it is not possible to run wt.exe from windowskey-R, cmd prompt, or anything else that needs to find it on the path.

Environment

  • Microsoft Windows [Version 10.0.19041.264]
  • Absolutely never before had Windows Terminal installed
  • Windows Terminal v1.0.1401.0 from Windows Store

Steps to reproduce

  1. Install Windows
  2. Windows Terminal v1.0.1401.0 from Windows Store
  3. Press windowskey-R to get quick run prompt
  4. Type wt.exe

Expected behavior

Windows Terminal to run

Actual behavior

Error. Windows cannot find wt.exe image

I checked my path at cmd prompt. The following is a cut/paste. Notice the last entry, two semicolons and then a env variable not expanded. And with that unexpanded directory not evaluated in the path, naturally wt.exe will not be found by windowskey-R or typing wt.exe at a legacy command prompt.

C:\Users\dale>path
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Strawberry\c\bin;C:\Strawberry\perl\site\bin;C:\Strawberry\perl\bin;C:\ProgramData\chocolatey\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\bin;C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\libnvvp;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files\NVIDIA Corporation\Nsight Compute 2019.4.0\;C:\Program Files\Microsoft VS Code\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\Microsoft VS Code\bin;C:\Users\dale\.flutter\bin;C:\Users\dale\.cargo\bin;C:\Program Files\Android\android-studio-preview\jre\bin;C:\njs\wslgit;C:\njs;C:\Program Files\CMake\bin;;%USERPROFILE%\AppData\Local\Microsoft\WindowsApps

created time in a month

fork diablodale/min-api

High-level C++-language application programming interface for Max

fork in a month

issue commentCycling74/min-api

dozens of bugs exposed by warnings; min-api needs overhaul to address

Hahaha, to continue the joke, please send me a email so I can give you my invoicing information. The week or two of work needed to fix the readily found min-api problems are more than I can do without a formal agreement setup. ;-) The economics don't work without compensation. You're welcome to email anytime. I can fit in the work while I'm working on another project.

I'll use the legacy 6.x SDK until min-api is brought up to production quality. We all have priorities. Cheers :-)

diablodale

comment created time in a month

issue openedCycling74/min-api

dozens of bugs exposed by warnings; min-api needs overhaul to address

Hi. I'm finding so many bugs through compiler warnings that it doesn't make sense to continue listing them one-by-one. Cycling74 can see and fix them in bulk by turning on level 4x warnings. I've filed multiple other issues and additional example of the many dozens is below.

Setup

  • VS Community 2019 v16.6.0
  • max api commit 1c06b88fc30da0931b6dfa4a874bc081afe00926
  • min api commit 210d5da
  • min.jit.stencil.cpp from the min-devkit

Repro

  1. Remove any 'ignore warning' flags from your cmake harness
  2. Add /W4 to your cmake add_compile_options()
  3. Compile min.jit.stencil.cpp

Result

Dozens of bugs and warnings. You'll have to go one by one to see which is a legitimate bug. I've logged some of them in separate issues. And I'll give one additional example here

C:\repos-nobackup\min-api\include\c74_min_string.h(47): warning C4100: 'glue': unreferenced formal parameter

That is a legitimate bug. The function's code is errant to always put a space between joined strings rather than using the glue parameter.

inline string join(const vector<string>& input, char glue = ' ') {
        string output;

        for (const auto& str : input) {
            output += str;
            output += " ";    // <------------- BUG
        }
        trim(output);
        return output;
    }

created time in a month

issue openedCycling74/min-api

logical operation on address of string constant warnings (is risk)

Multiple warnings in min-api of "logical operation on address of string constant". This is due to comparing the addresses of two pointers; each of those pointers pointing to a block of char.

Setup

  • VS Community 2019 v16.6.0
  • max api commit 1c06b88fc30da0931b6dfa4a874bc081afe00926
  • min api commit 210d5da
  • min.jit.stencil.cpp from the min-devkit

Repo

  1. Remove any 'ignore warning' flags from your cmake harness
  2. Compile min.jit.stencil.cpp

Result

Build fails with:

[build] C:\repos-nobackup\min-api\include\c74_min_object_wrapper.h(242): error C2220: the following warning is treated as an error
[build] C:\repos-nobackup\min-api\include\c74_min_object_wrapper.h(785): note: see reference to function template instantiation 'void c74::min::wrapper_method_multitouch<min_class_type,c74::min::wrapper_message_name_mt_mouseenter>(c74::max::t_object *,c74::max::t_object *,c74::max::t_mouseevent *)' being compiled
[build]         with
[build]         [
[build]             min_class_type=jit_stencil
[build]         ]
[build] ..\min.jit.stencil.cpp(70): note: see reference to function template instantiation 'void c74::min::wrap_as_max_external<jit_stencil,0>(const char *,const char *,void *,min_class_type *)' being compiled
[build]         with
[build]         [
[build]             min_class_type=jit_stencil
[build]         ]
[build] C:\repos-nobackup\min-api\include\c74_min_object_wrapper.h(242): warning C4130: '==': logical operation on address of string constant
[build] C:\repos-nobackup\min-api\include\c74_min_object_wrapper.h(244): warning C4130: '==': logical operation on address of string constant
[build] C:\repos-nobackup\min-api\include\c74_min_object_wrapper.h(246): warning C4130: '==': logical operation on address of string constant
[build] C:\repos-nobackup\min-api\include\c74_min_object_wrapper.h(248): warning C4130: '==': logical operation on address of string constant
[build] C:\repos-nobackup\min-api\include\c74_min_object_wrapper.h(250): warning C4130: '==': logical operation on address of string constant
[build] C:\repos-nobackup\min-api\include\c74_min_object_wrapper.h(252): warning C4130: '==': logical operation on address of string constant
[build] ninja: build stopped: subcommand failed.

Expected

No warnings or errors, a clean build, and an mxe output.

Notes

This is a valid problem and should not be ignored. The lines of code are errant.

if (name == "mt_mouseenter")
  1. name is an auto variable (char *) that was derived from a struct containing a static const char created with MIN_WRAPPER_CREATE_TYPE_FROM_STRING()
  2. "mt_mouseenter" is also a static const char created inplace
  3. Comparing two pointers is bad.

It might by luck work. Why? Because some compilers with some options (like string pooling, COMDAT folder, etc.) will recognize: 1) the string bytes created with MIN_WRAPPER_CREATE_TYPE_FROM_STRING() and 2) the inplace bytes with "mt_mouseenter" are the same... and therefore have each refer to the same bytes in the executables data segment and therefore have the same pointer address. However, this is too risky. It depends on your specific compiler with specific compile options and that the compiler does the pooling and recognizes the two are the same.

The correct way to compare two C-style POD strings is to use strcmp(), convert them to std::string, etc.

created time in a month

issue openedCycling74/min-api

jitter matrix processing not inlined, inefficient, millions of jumps/calls per frame

The most important part of a jitter external is the matrix calculation loop. Full stop. The min-api is not designed to be efficient in this most important area. Critical matrix calculation functions are not inlined and instead have multiple millions (for an HD frame) of expensive calls to/from for every frame's matrix calculation.

Writing C/C++ code for jitter objects is a technical endeavor. Otherwise, a person should use (gen). I request the Cycling74 team do a thorough design review of min-api to surface these performance flaws.

Context

The matrix calc function in a jitter external is called once per frame. That function loops over all dimensions of input and output matrices to transform (or generate) the output matrices. It is common for such looping to be sliced into chunks (aka "ndim") and to spawn threads for each ndim chunk. And then each thread loops over its chunk.

Naturally, there is great need for the loops to be optimized, access to memory kept thread local in all cases possible, and for code to be local to the thread and not jump to/from other places in memory.

Modern compilers statically analyze code and functions to optimize the output executable. One optimization is to reduce code duplication by putting functions as independent units, and then each calling site calls/jumps to that shared function. Another optimization is to "inline" a function at the calling site. Inlining improves speed at the cost of larger code/memory size. Why consider to inline or not a function? Because jumps/calls are very expensive. This is just two of many optimizations compilers do and the approaches compilers take are based on the compiler's static analysis. And this analysis is specific to the function and the calling site. Meaning, it is possible for the compiler to inline a function in one calling location and not inline that same function in another calling location.

C/C++ coders can give a "hint" to the compiler to suggest the compiler inline or not inline a function. This is only a hint. Nothing guaranteed and it can't be forced. This is by design. https://docs.microsoft.com/en-us/cpp/cpp/inline-functions-cpp?redirectedfrom=MSDN&view=vs-2019 and https://en.cppreference.com/w/cpp/language/inline

There is a rumor that compilers tend to not inline functions longer than a few lines. That their analyzer's cost/benefit analysis determines that the size of all the functionality overwhelms the benefit of an unknown speed improvement. Since the analysis is static, the compiler can not verify this...its just an algorithmic guess. I can find nothing in the cpp specs to support this, however, there is a general "feeling" in the c++ community that for functions to be successfully inlined, they need to be very short and focused.

Setup

  • VS Community 2019 v16.6.0
  • max api commit 1c06b88fc30da0931b6dfa4a874bc081afe00926
  • min api commit 210d5da4b9a3ebc201b4be5c1f0733e3110b1993
  • min.jit.stencil.cpp from the min-devkit

For the reader that doesn't have experience with MAP files, read https://www.codeproject.com/Articles/3472/Finding-Crash-Information-Using-the-MAP-File
https://docs.microsoft.com/en-us/cpp/build/reference/decorated-names?view=vs-2019
https://flylib.com/books/en/4.441.1.87/1/
https://stackoverflow.com/questions/1902976/msvc-any-way-to-check-if-function-is-actually-inlined

Repo

  1. Edit your harness's CMakeLists.txt to add the /MAP parameter to target_link_options().
  2. Build stencil with cmake build variant Release
  3. Examine the generated min.jit.stencil.map

Result

Core functions of the matrix calculation are not inlined. Instead, they are independent functions with multiple call sites jumping/calling into them. This is terribly inefficient and detrimental to a performant jitter external. Here is proof of two functions jit_calculate_vector, calc_cell

 0001:00013d90       ??$jit_calculate_vector@Vjit_stencil@@E$0A@@min@c74@@YAXPEAU?$minwrap@Vjit_stencil@@X@01@AEBVmatrix_info@01@JJPEAUt_jit_op_info@max@1@2@Z 0000000180014d90 f i min.jit.stencil.cpp.obj
 0001:00014bf0       ??$jit_calculate_vector@Vjit_stencil@@H$0A@@min@c74@@YAXPEAU?$minwrap@Vjit_stencil@@X@01@AEBVmatrix_info@01@JJPEAUt_jit_op_info@max@1@2@Z 0000000180015bf0 f i min.jit.stencil.cpp.obj
 0001:000160c0       ??$jit_calculate_vector@Vjit_stencil@@M$0A@@min@c74@@YAXPEAU?$minwrap@Vjit_stencil@@X@01@AEBVmatrix_info@01@JJPEAUt_jit_op_info@max@1@2@Z 00000001800170c0 f i min.jit.stencil.cpp.obj
 0001:000177f0       ??$jit_calculate_vector@Vjit_stencil@@N$0A@@min@c74@@YAXPEAU?$minwrap@Vjit_stencil@@X@01@AEBVmatrix_info@01@JJPEAUt_jit_op_info@max@1@2@Z 00000001800187f0 f i min.jit.stencil.cpp.obj
 0001:00018da0       ??$calc_cell@E$00@jit_stencil@@QEAA?AV?$array@E$00@std@@V12@AEBVmatrix_info@min@c74@@AEAVmatrix_coord@45@@Z 0000000180019da0 f i min.jit.stencil.cpp.obj
 0001:00018ec0       ??$calc_cell@E$03@jit_stencil@@QEAA?AV?$array@E$03@std@@V12@AEBVmatrix_info@min@c74@@AEAVmatrix_coord@45@@Z 0000000180019ec0 f i min.jit.stencil.cpp.obj
 0001:00018fe0       ??$calc_cell@H$00@jit_stencil@@QEAA?AV?$array@H$00@std@@V12@AEBVmatrix_info@min@c74@@AEAVmatrix_coord@45@@Z 0000000180019fe0 f i min.jit.stencil.cpp.obj
 0001:000190e0       ??$calc_cell@M$00@jit_stencil@@QEAA?AV?$array@M$00@std@@V12@AEBVmatrix_info@min@c74@@AEAVmatrix_coord@45@@Z 000000018001a0e0 f i min.jit.stencil.cpp.obj
 0001:00019200       ??$calc_cell@N$00@jit_stencil@@QEAA?AV?$array@N$00@std@@V12@AEBVmatrix_info@min@c74@@AEAVmatrix_coord@45@@Z 000000018001a200 f i min.jit.stencil.cpp.obj

Here are two of those function names undecorated by undname.exe

void __cdecl c74::min::jit_calculate_vector<class jit_stencil,unsigned char,0>(struct c74::min::minwrap<class jit_stencil,void> * __ptr64,class c74::min::matrix_info const & __ptr64,long,long,struct c74::max::t_jit_op_info * __ptr64,struct c74::max::t_jit_op_info * __ptr64)

public: class std::array<unsigned char,1> __cdecl jit_stencil::calc_cell<unsigned char,1>(class std::array<unsigned char,1>,class c74::min::matrix_info const & __ptr64,class c74::min::matrix_coord & __ptr64) __ptr64

Expected

The entire ndim section of code for a matrix calculation to be contiguous, no jumps/calls to functions, and thread local storage whenever technically possible.

Workarounds

As min-api is currently designed, there is no quick fix. The segmentation of jitter functionality has lead to a cascade of functions calling to/from and results in significant overhead.

It may be possible (no guarantee) to request the compiler inline functions. For example:

  • min-api headers could declare inline on jitter member function prototypes like calc_cell so that when consumers of min-api write their own calc_cell they are forced to also inline. But remember...the compiler doesn't guarantee to actually inline it.
  • min-api headers could definitely declare inline on their own internal functions like jit_calculate_ndim, jit_calculate_ndim_loop, jit_calculate_vector, etc. in a similar hope that the compiler will inline them.
  • probably use additional compiler specific specifiers like __forceinline and __attribute__((always_inline)) as more hope and stronger hints to the compiler. But remember...it is still not guaranteed.

Do these work? Not really. The compiler failed to inline when I tried inline in the headers for jit_calculate_vector and stencil's calc_cell and get_cell.

Using __forceinline failed as it couldn't inline all the matrix calc related functions. For example:

[build] C:\repos-nobackup\min-api\include\c74_min_operator_matrix.h(474) : warning C4714: function 'void __cdecl c74::min::jit_calculate_ndim<class jit_stencil,0>(struct c74::min::minwrap<class jit_stencil,void> * __ptr64,long,long * __ptr64,long,struct c74::max::t_jit_matrix_info * __ptr64,unsigned char * __ptr64,struct c74::max::t_jit_matrix_info * __ptr64,unsigned char * __ptr64)' marked as __forceinline not inlined
[build] C:\repos-nobackup\min-api\include\c74_min_operator_matrix.h(513) : warning C4714: function 'void __cdecl c74::min::jit_calculate_ndim_single<class jit_stencil,0>(struct c74::min::minwrap<class jit_stencil,void> * __ptr64,long,long * __ptr64,long,struct c74::max::t_jit_matrix_info * __ptr64,unsigned char * __ptr64)' marked as __forceinline not inlined

The Microsoft doc https://docs.microsoft.com/en-us/cpp/cpp/inline-functions-cpp?redirectedfrom=MSDN&view=vs-2019 warns that recursive functions have limitations. Perhaps those two functions are ok to not be inlined since in the parallel ndim scenario that is the level of chunk work.

Removing __forceinline on those two but keeping the force on the others, resulted in compile that did not have entries in the MAP file for jit_calculate_vector, jit_calculate_ndim_loop, calc_cell, get_cell, jit_matrix_docalc, perhaps others.

Keep in mind that I see many class member functions that have no specifier on them and they are defined in the class definitions. This means they are implicitly inlined as if the inline specifier was on them. But still no guarantee. Therefore, compiler specific specifiers like __forceline can be used on them to increase the chances they will be inlined.

matrix_coord is such a critical class that it should be inlined. Yet, the compiler didn't do it...

 0001:00001df0       ??0matrix_coord@min@c74@@QEAA@JJ@Z 0000000180002df0 f i min.jit.stencil.cpp.obj
 0001:00001e20       ?x@matrix_coord@min@c74@@QEBAJXZ 0000000180002e20 f i min.jit.stencil.cpp.obj
 0001:00001e30       ?y@matrix_coord@min@c74@@QEBAJXZ 0000000180002e30 f i min.jit.stencil.cpp.obj

I was able to have matrix_coord inlined if I used __forceinline on the constructor, x(), and y(). Perhaps in_cell() and in_pixel() should be done the same.

Also keep in mind that a static function name will not appear in a MAP file. To see if such a function has been inlined, you must examine the assembly at the calling location.

To my knowledge, the only guarantee for code to be contiguous and no jumps is when code is fully defined all within one function. That is...a single all inclusive ...calculate_ndim()

created time in a month

issue commentmicrosoft/vscode-cpptools

intellisense uses newest SDK instead of specified Win8.1

Discovered a few opportunities...

Using VS2017/2019, I should have only two winkits installed: 8.1 and 10.0.17134. I found what I expected...

I have on my drive C:\Program Files (x86)\Windows Kits
and inside it are two folders: C:\Program Files (x86)\Windows Kits\8.1 C:\Program Files (x86)\Windows Kits\10 they contained: C:\Program Files (x86)\Windows Kits\8.1\Include\shared C:\Program Files (x86)\Windows Kits\10\Include\10.0.17134.0\shared

I then used regedit to do a whole string search for KitsRoot10 in keys and values...

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Kits\Installed Roots
with the value:
KitsRoot10 = REG_SZ C:\Program Files (x86)\Windows Kits\10\

I also found... 🧐 HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows Kits\Installed Roots with the values: KitsRoot81 = REG_SZ C:\Program Files (x86)\Windows Kits\8.1\
KitsRoot10 = REG_SZ C:\Program Files (x86)\Windows Kits\10\

That latter finding is slightly different than your inquiry above where you asked for a key named KitsRoot81 instead of a value with that name. I wasn't able to gap the mistype as I didn't visibly see that value because there are 50+ values in the Installed Roots key and the KitsRoot81 value is offscreen.

diablodale

comment created time in a month

issue commentmicrosoft/vscode-cpptools

intellisense uses newest SDK instead of specified Win8.1

Seems I'm not the only one. Others are reporting that regkey missing... https://gitlab.kitware.com/cmake/cmake/issues/16811

diablodale

comment created time in a month

issue commentmicrosoft/vscode-cpptools

intellisense uses newest SDK instead of specified Win8.1

That regkey doesn't exist.

image

Here it is installed by... image

diablodale

comment created time in a month

issue commentCycling74/min-api

missing `const` throughout headers; causes difficult usage, integration, and slowdown

Want to add clarification on that const-correctness subtlety...

The rightmost const in this prototype foobar(int * const a); is pedantic. For the consumer of the function, it doesn't matter so much. For the coder of the function itself, it is valuable as it restricts the code in that function from accidental mistakes. For example:

void foobar(int * a) {
++a;
}

The above incremented the pointer. But the coder meant to increment the int to which the pointer pointed. Now contrast this to the following:

void foobar(int * const a) {
++a;
}

In that above version, the compiler will protect the coder from themselves. It won't compile. And so they can change their code to be the correctish ++(*a). The exception in my link writes to the frequency and reasoning. I lean towards protecting myself when I write the inside of that function. In my experience, all humans make mistakes.

Separate from the right-most const, the following is definitely desired if the dereferenced value of the pointer should be const and the function should not be able to change it

void jimjam(const int * a) {
  // can't change *a
}
diablodale

comment created time in a month

issue commentCycling74/min-api

missing `const` throughout headers; causes difficult usage, integration, and slowdown

@j3kz haha, yes max::t_symbol const * const s or const max::t_symbol * const s are both fine with me. Something in my past, has me put const as left as possible. In practice, I have no preference and can follow the style of the team.

@tap great reference. Yet, I think you misread F.16. Cheap things (int, float, POD-stuff) pass by copy Complex things (large structs, STL containers, etc.) pass by const reference. This is focused on performance...the cpu/mem overhead of sending data to a function via parameters. But F.16 does not provide guidance for the issue at hand. The issue of const-correctness.

I'm saying to const the pass by copy in every situation you don't mutate it in the function https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#con-constants-and-immutability. It better documents code, helps coders from making mistakes, provides opportunities for compiler optimizations, etc. This approach is so important in 21st century coding...that new languages like Rust go so far that variables are by default const and you have to go through hoops to mutate them.

If function code is only reading a parameter...make it const. This protects the coder of that function from inadvertent mistakes. And allows more flexible usage of the function itself. Remember the legacy SDK and its header ext_proto.h with the following ugh 😝 prototype

void *outlet_anything(void *o, t_symbol *s, short ac, t_atom *av);

I can't write the solid code I want to. That legacy prototype forces me to send mutable non-const values for everything. But as we all know, t_symbols are always logically const (as editing inside that "blackbox" is a no-no), and my av should be const (because outlet_anything shouldn't be altering it), and pointers to them all may/may not be const. But no...that prototype forces all params to be non-const pointers to non-const values.

That prototype, atom_setsym() and others are so troublesome to use in well-structured code, that I in my custom max headers alter them to I can write better code. My prototypes are

void *outlet_anything(void *o, const t_symbol * const s, const short ac, const t_atom * const av);
t_max_err atom_setsym(t_atom * const a, const t_symbol * const s);

With those prototypes, I can send const or non-const parameters. I can now in my code (before it ever gets to that max function) use const variables to hold const things. Yay! And the prototype tells a naive max programmer that this function is not going to change anything.

diablodale

comment created time in a month

issue openedCycling74/min-api

jitter matrix processing direction has large cpu/memory cache contention and overhead

the min matrix operator reads the calculate direction variable 2,075,759 times too many on each matrix calculation. It can read it once per matrix calculation.

When the matrix is processed a call is made to the subclass calc_cell() method for each cell. The order in which the cells are iterated will be one of the options provided here [by m_direction]

For example at: https://github.com/Cycling74/min-api/blob/32449860b7929bd822cf543c551a9f5fb9fad6e5/include/c74_min_operator_matrix.h#L283-L291

  1. This variable and its access is not thread-safe
  2. If changed during the middle of an ndim parallelized action, the effects are indeterminate.
  3. To get this direction value, the CPU must deference a pointer and read the variable (2 + up to framewidth) times on every section (up to every row) of every ndim parallelized block for every matrix frame.

As an example, its possible for a single frame, for the current min-api codebase to access m_direction the following number of times for an HD color rgba image.

(2+framewidth=1922 potential accesses each jit_calculate_vector section) x (1080 for every HD row) = 2,075,760 times

That's very poor. 😞 Because its a single value that only needs to be read 1 time from the class variable on each frame.

And worse, this class member variable access is spread across multiple cpu caches. And since it is a read/write dereferenced variable and could be changed by any thread running on any cpu on any core, then the cache is constantly thrashing making access slow.

There are multiple possible improvements, and combinations of them can be used.

  1. make direction compile time. It is a subset of externals that need to process cells in a matrix in dynamically runtime changing calculation order.
  2. make direction set on the class. For that subset of externals that need a dynamically runtime changing calculation order and further that subset of customers using that subset of externals that choose a non-standard direction, let them set it as an argument on the max object, or a read-only attribute. Then it is a const set at class construction.
  3. copy direction from that class's member variable to an ndim/thread const local parameter/struct. This means that the direction can not change during the scope of a single matrix_calc. And when the value is copied into a param/struct for each ndim section, this allows for cache locality on the cpu that is running that ndim thread.

created time in a month

issue openedCycling74/min-api

missing `const` throughout headers; causes difficult usage, integration, and slowdown

Headers throughout min-api are missing const. The const that is totally absent in legacy SDKs, mostly absent in max-api, is also mostly absent in min-api. To use min, I need it to be better than the legacy SDKs. This is major SDK work to resolve a systemic problem; needs to be done by Cycling74, not customers.

c74_min_operator_matrix.h has so many missing const that I can't list them all here. Here are two of dozens in that file:

https://github.com/Cycling74/min-api/blob/32449860b7929bd822cf543c551a9f5fb9fad6e5/include/c74_min_operator_matrix.h#L27-L29

https://github.com/Cycling74/min-api/blob/32449860b7929bd822cf543c551a9f5fb9fad6e5/include/c74_min_operator_matrix.h#L217-L218

Not isolated to that one file. Second example c74_min_buffer.h

https://github.com/Cycling74/min-api/blob/32449860b7929bd822cf543c551a9f5fb9fad6e5/include/c74_min_buffer.h#L49-L54

I request that min-api use const in all situations possible. As a rule, the default for all function parameters should be const. Only if a reference parameter is to be mutated should it be non-const. This leads then to declaring max_jit_mop_new(const max::t_symbol* const s, const long argc, const max::t_atom* const argv).

I do see some examples of member functions being declared const when they do not change state of their class. This const usage should be verified across all min-api member functions to ensure this is consistently on all member functions that don't mutate their class.

created time in a month

issue commentmicrosoft/vcpkg

How to remove dependencies of package being removed?

@cbezault , please consider what your typed in your 2nd sentence and my analysis post above. The Win32 binary vcpkg does that + leaves an orphanage. That's the issue. This issue is not about a coding bug. This issue is about a design/Ux flaw. Someone spec'd a design model which doesn't match the mental model of users with the install/remove pair. While also creating situations that leave dependency holes and/or orphanages.

IIFE

comment created time in a month

issue openedmicrosoft/vcpkg

docs: triplet VCPKG_C_FLAGS and VCPKG_CXX_FLAGS is unclear

Docs for triplets and the flag families VCPKG_C_FLAGS*, VCPKG_CXX_FLAGS* are unclear. By trial and error I discovered that you must use set(), not a cache variable, and the value must be a single string (not a list). I recommend updating official docs to clarify correct usage. Here is the ambiguous doc...

https://github.com/microsoft/vcpkg/blob/55be137d5ba6230f62aa7fb0994fda1728ce7fef/docs/users/triplets.md#L67-L77

Setup

  • vcpkg b37f5d651d0f55a3f0ed709ed1682a4385294519
  • tested with port opencv4

Single Success

set(VCPKG_CXX_FLAGS "-DWINVER=0x0A00 -D_WIN32_WINNT=0x0A00 -DNTDDI_VERSION=0x0A000005") works.

The family of settings like VCPKG_C*_FLAGS* must...

  1. be set()
  2. its single value must be a string
  3. if multiple compiler settings are desired, then put them all in a single string and separate them with a space

Failures

Various combinations were tested and all failed. For example the following all failed in each their own way:

  • set(VCPKG_CXX_FLAGS
    -DWINVER=0x0A00
    -D_WIN32_WINNT=0x0A00
    -DNTDDI_VERSION=0x0A000005
    )
  • set(VCPKG_CXX_FLAGS -DWINVER=0x0A00 -D_WIN32_WINNT=0x0A00 -DNTDDI_VERSION=0x0A000005)
  • set(VCPKG_CXX_FLAGS -DWINVER=0x0A00 -D_WIN32_WINNT=0x0A00 -DNTDDI_VERSION=0x0A000005 CACHE internal)
  • etc.

Example of clearer doc

Sets additional compiler flags to be used when not using VCPKG_CHAINLOAD_TOOLCHAIN_FILE. Use set() and declare the single value of that variable as a string. When multiple compiler flags are needed, separate them with a space. For example, a triplet file would include:

set(VCPKG_C_FLAGS "-DWINVER=0x0A00 -D_WIN32_WINNT=0x0A00 -DNTDDI_VERSION=0x0A000005")

This option also has forms for configuration-specific and C flags:

  • VCPKG_CXX_FLAGS
  • VCPKG_CXX_FLAGS_DEBUG
  • VCPKG_CXX_FLAGS_RELEASE
  • VCPKG_C_FLAGS
  • VCPKG_C_FLAGS_DEBUG
  • VCPKG_C_FLAGS_RELEASE

created time in a month

issue commentmicrosoft/vcpkg

How to remove dependencies of package being removed?

Yes, this is strange behavior and due to a broken mental model for vcpkg. And that errant model leads to a orphanage and/or dependency tree with holes. @PhoebeHui writes...

@IIFE, this is intended behavior, if you remove boost, then adding --recurse option will remove all ports(eg: cpprestsdk)that dependent to boost.

In that scenario, the vcpkg remove boost will result in a broken vcpkg library tree. Why?

  1. cpprestsdk depends on boost being installed
  2. vcpkg remove boost removes boost from the folders
  3. Now any use of cpprestsdk has a high chance of failure depending on how cpprestsdk and boost were built (static, dynamic, etc.)

As I see it, vcpkg remove boost should immediately fail. vcpkg should forbid any removal of packages who have other packages that depend on them.

As I have read and somewhat seen myself, the vcpkg remove --recurse doesn't recurse down into children. It recurses up into parents. It recurses to parent dependers, not child dependencies.

This conflicts with the mental model of vcpkg install. Why? First, install and remove are a matched pair. vcpkg install installs a package and its dependencies. Therefore, the mental model is that vcpkg remove would remove a package and its dependencies. But it doesn't.

vcpkg action who is affected
install dependencies ✔
remove dependers ❌

Since the mental model is not consistent in vcpkg, this causes the confusion of the OP (and me). vcpkg remove results in a broken dependency tree since the dependers are still on the hard drive. And leads to manual work to cleanup orphan dependencies that were not removed.

This then puts into question the option --recurse. It is a curious option. If you don't use it, then the vcpkg tree will have dependency holes since the parent depender's dependency was removed. If you do use it, then there won't be holes for the immediate port, but if it has any dependers (to which --recurse recurses ?infinitely?), then when the chain of dependers (and their dependers...) are removed it will leave all the dependencies of those dependers as orphans. Creating not holes...instead an broad orphanage. 😵

At my current level of thinking through this problem, it is unsafe to use vcpkg remove. It is additionally unsafe to use vcpkg remove --recurse on any package that has a dependency. Not following those two rules will result in a vcpkg folder with either a shotgun of dependency holes or an orphanage.

On the plus side, nobody dies here. No production-stage app crashes. Dependencies can be rebuilt when errors occur. And wasted hard drive space is cheap.

I reproduced this broken model with the opencv4 port. When I vcpkg remove opencv4:triplet, it left many orphaned packages including (hdf5, opengl, szip, gflags, glog, etc.). In https://github.com/microsoft/vcpkg/blob/master/ports/opencv4/CONTROL you can see all the dependencies. vcpkg remove --recurse only removed opencv4 and its features. It removed no dependencies.

Dependencies, dependers, and a ref count for each are challenges that tools like apt and yum have been managing for years. For example, apt tracks when dependencies are not longer needed and prompts the admin; who can then purge them with apt autoremove. There can be learning from these seasoned tools to address the broken vcpkg mental model and look forward to possible resolutions.

IIFE

comment created time in a month

issue commentmicrosoft/vscode

`git.path` fails in workspace settings

Unclear why this issue is closed if we are having a discussion. I request it be reopened until we complete our investigation...or open a new issue.

diablodale

comment created time in a month

issue commentmicrosoft/vscode

`git.path` fails in workspace settings

@kieferrm , I don't understand your comment. Did you mistype or missing a word? As a guess, did you intend to write "git.path is not a user setting..."?

If that was your intention, then a restriction like that doesn't protect anyone with any actual beneficial effect. That's like putting a red velvet rope around something. Or security through obscurity. Its meaningless and only hinders normal users. It is no barrier to actual evil hackers/virus. 🙈

As an example, I took 5 minutes (really...only 5 minutes) and I found 11 dangerous workspace settings that can point to dangerous unauthorized code. As I see the ecosystem, the issue of "protecting against evil hackers" is not solvable by workspace settings.

  • everything task.json
  • everything launch.json
  • python.pythonPath
  • python.linting.mypyPath
  • docker.certPath
  • eslint.nodePath
  • C_Cpp.default.compilerPath
  • terminal.integrated.shell.*
  • cmake.cmakePath
  • cmake.ctestpath,
  • and a bonus phpcs.executablePath
diablodale

comment created time in a month

issue openedmicrosoft/vscode

`git.path` fails in workspace settings

Issue Type: <b>Bug</b>

  1. Have working VSCode and working git functionality in VSCode
  2. menu file/preferences/settings
  3. In json or UI, go to workspace settings
  4. attempt to set "git.path"

Result

The UI and json do not recognize git.path at the workspace settings.
Entering a git.path in the workspace settings, reload the window, can see it has no effect and is ignored. This setting is only settable from the master top-level settings file.

Expected

git.path to be settable at the workspace settings level as the majority of other settings. Having this functionality is important so that a developer can set a specific git to be used for a specific project/workspace. Windows and VSCode are no longer a single OS, single environment. Now projects and the editors (e.g. vscode) for them span multiple OS, environments, etc.

In my specific scenario, I use the Win32 git.exe only on one project. For all other projects, I use the WSL git.exe due to its extensive integration into auth, gpg signing, and portable settings. ✔

Workaround

Editing the master settings.json every time vscode is launched to match the project's needs for git.path

Additional info

VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z) OS version: Windows_NT x64 10.0.19041

<details> <summary>System Info</summary>

Item Value
CPUs Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz (8 x 2594)
GPU Status 2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off_ok<br>webgl: enabled<br>webgl2: enabled
Load (avg) undefined
Memory (System) 15.89GB (7.46GB free)
Process Argv
Screen Reader no
VM 0%

</details><details><summary>Extensions (17)</summary>

Extension Author (truncated) Version
better-toml bun 0.3.2
vscode-markdownlint Dav 0.35.2
gitlens eam 10.2.1
EditorConfig Edi 0.15.1
todo-tree Gru 0.0.176
vscode-random jre 1.6.1
rainbow-csv mec 1.7.0
remote-containers ms- 0.117.1
remote-ssh ms- 0.51.0
remote-ssh-edit ms- 0.51.0
remote-wsl ms- 0.44.2
vscode-remote-extensionpack ms- 0.20.0
cmake-tools ms- 1.4.0
cpptools ms- 0.28.1
vscode-sort-json ric 1.18.0
cmake twx 0.0.17
markdown-all-in-one yzh 3.0.0

</details> <!-- generated by issue reporter -->

created time in a month

issue commentmicrosoft/vscode-cpptools

intellisense uses newest SDK instead of specified Win8.1

Hi, I see label is still 'more info needed'. Did my post above clarify? If not, please tell me what more info is needed so I can collect it.

diablodale

comment created time in a month

issue openedmicrosoft/vcpkg

[boost] remove --recurse fails and needs 4 additional removes

vcpkg remove boost-vcpkg-helpers --recurse fails to remove all of boost. It requires an additional 3 remove to finally remove all of boost. 🤛🤛🤛

This errant behavior was exposed due to failure of upgrade https://github.com/microsoft/vcpkg/issues/11482 and the boost port requiring special and unique removal procedure https://github.com/microsoft/vcpkg/issues/8486#issuecomment-580928157

Setup

  • Windows 10
  • vcpkg
  • boost 1.72.0 installed

Repro

  1. vcpkg remove boost-vcpkg-helpers --recurse. Notice is spelled plural
  2. vcpkg list
  3. Boost is still there. Was boost-vcpkg-helper always there? Notice it is spelled singular
  4. vcpkg remove boost-vcpkg-helper --recurse
  5. vcpkg list
  6. Still more boost. And now I can see there is boost-build
  7. vcpkg remove boost-build --recurse
  8. vcpkg list
  9. Yet more boost. Now there is boost-modular-build-helper
  10. vcpkg remove boost-modular-build-helper --recurse
  11. vcpkg list

Result

Boost is gone after four separate removals, each one a unique boost-only command in a unique boost only removal process.

Expected

vcpkg remove boost should work. Full stop. No special procedure. No wack-a-mole with 4 seperate remove commands.

Cute animal pic

mole-cat

created time in a month

pull request commentGnucash/gnucash

Bug 797218 - Support QIF import with any encoding

I continue to believe the workflow should include additional UI and steps. As I wrote in https://bugs.gnucash.org/show_bug.cgi?id=797218#c9 so I don't duplicate the conversation.

christopherlam

comment created time in a month

issue commentCycling74/min-api

constructors called twice and have different behaviors/argument values

@sncheca , thanks for looping in that issue. I'm on another project now, will revisit this in June 2020 and I can test if that's the double I see and also explore that dummy. It seems odd to create a dummy at runtime when all is known at compiletime. We have constexpr and cmake. 🤔

diablodale

comment created time in a month

issue openedmicrosoft/vcpkg

[boost] build failure on upgrade "Error... port definition not found"

vcpkg upgrade to move boost from 1.72.0 to 1.73.0 fails. Results in manual removal of all Boost triplets and manual install of all triplets. upgrade fails in its reason to exist 😆

Setup

  • Windows 2004 Version 10.0.19041.264
  • Visual Studio 2019 Community 16.6.0

Repro

  1. Have previously installed Boost 1.72.0 with all its components/features
  2. git pull
  3. vcpkg update and notice there is a new Boost 1.73.0
  4. vcpkg upgrade

Result

Failure.

Error: while loading boost-disjoint-sets:x64-windows-static-md-v142-sdk10b17134: Port definition not found.
Please run "vcpkg remove boost-disjoint-sets:x64-windows-static-md-v142-sdk10b17134" and re-attempt.

Continued Repro

  1. vcpkg remove boost-disjoint-sets:x64-windows-static-md-v142-sdk10b17134

Result 2

Failure. The vcpkg state is such that a manual removal of the entire boost package (see 1st line with *) must occur. I have four triplets. Therefore, I will need to manually remove all four and then manually install all four. Such tedium is the job of upgrade, but it fails as seen above.

The following packages will be removed:
  * boost:x64-windows-static-md-v142-sdk10b17134
    boost-disjoint-sets:x64-windows-static-md-v142-sdk10b17134
Additional packages (*) need to be removed to complete this operation.
If you are sure you want to remove them, run the command with the --recurse option

Expected

No errors or failures. vcpkg upgrade should nicely upgrade all parts of Boost on all installed triplets. If any features no longer exist, then it should warn and/or easily remove them. At no time should a manual remove and manual install of all triplets be needed.

created time in a month

issue commentMicrosoftDocs/feedback

Microsoft Product Lifecycle catch-all phrase not helpful

Unfortunately, this spam banner does not go away. Instead, it returns on every page. Naturally, once a customer has read it once, and clicked to close it, it should never appear again. SOP Ux behavior.

Repro

  1. Visit https://docs.microsoft.com/en-us/previous-versions/windows/kinect/dn782038(v=ieb.10)
  2. Click X on right of spam banner.
  3. Click C+ Reference in main content pane
  4. Click X on right of spam banner. 😟
  5. Click Interfaces in main content pane
  6. Click X on right of spam banner. 😟
  7. Click IAudioBeamFrame in main content
  8. Click X on right of spam banner. 😟
  9. etc.

Result

The spam banner appears on every page, every time. Reduced productivity by 2x mouse clicks, 10+% lose of reading space, distraction in customer's task.

Expected

Don't spam. Notify the customer once. If the customer clicks X, then disappear and don't appear again.

clairestreb

comment created time in 2 months

issue commentCycling74/max-api

missing define guard around NOMINMAX

Hi. You slightly misread. The header is missing a define guard. Not a header guard. Instead, missing a define guard.

Meaning...it is missing

#ifndef NOMINMAX
#define NOMINMAX
#endif

Naturally, its your headers. However, from a customer's perspective, these headers are new and drastically different. A lot of behaviors/settings/values/defines have changed. Any use of these new headers will require work by a customer. How do I know? Because I tried and already created this issue. ;-) And I chose to not use these new headers because I've got other things more important to do. I'll use new headers on a new project (not existing code).

Given that there is rework...then removing old legacy (like already done elsewhere in these headers) is appropriate. And in fact, it is odd for this old NOMINMAX define to still be there. Its legacy. It shouldn't be there historically (but was) and given these are new headers it shouldn't be there now. Otherwise, why use these new headers? Just use the crusty time-tested ones.

I strongly suggest you consider that if full backwards compat is desired by a customer...then use the 6.1.9 download or 7.x SDK on github. It 100% works. Otherwise, a customer can choose to use these new headers and by choosing (nothing forced) they also chose some rework.

Then...consider that Max isn't the focus of most customers. Instead, they are building a solution and Max is one of many components. However, think about keeping that NOMINMAX in there. Due to the way the headers/define is setup, this is Max intruding into other areas. Depending on how a project's compilation units are setup, this define could affect widely across the project. But what if other libraries or customer code needs MINMAX (the need that define to not be there). Well...that's not possible. Max headers (which don't need the define) are for a bizarre reason defining that macro. But this forces all the other customer code to comply.

Max (doesn't need/use it) but Max forces it. That make no logical sense. Max has no business or stake in NOMINMAX. So why define it? It seems a mistake. And if it is for legacy reasons, then that's a mistake also. These are new headers which require rework if used on existing code.

Following my thinking here?

diablodale

comment created time in 2 months

issue commentCycling74/max-api

missing define guard around NOMINMAX

Though before the trivial PR, why is c74_max_platform.h defining NOMINMAX? I see no value, instead potential harm due to already found macro redefinition compiler errors and user/3rd party potentially needing those legacy macros yet this header intrudes in defining such exclusion.

Throughout this repo, there are no occurrences of min( or max( which would trigger a conflict with those legacy minmax macros. Instead, I find explicit occurrences of std::max(, std::min(.

It could be possible that closed-source Cycling74 internal code uses those legacy macros. And in that case an internal closed-source header or compiler switch should define NOMINMAX.

I recommend removing line 104. Removing the define NOMINMAX as it is not needed for this Cycling74 max-api header/library. And removing it will remove problems with conflicts and forced workarounds (for the NOMINMAX workaround).

diablodale

comment created time in 2 months

fork diablodale/max-api

Low-level C-language application programming interface for Max

fork in 2 months

issue openedCycling74/max-api

missing define guard around NOMINMAX

The header is missing a define guard. Causing cascading macro redefinition problems that can span max, microsoft, and an infinite number of other-party headers.

https://github.com/Cycling74/max-api/blob/c5e4ac0e1917c99b874b3a53552a8cda43687cfd/include/c74_max_platform.h#L104

Easy fix. Put a guard around it. PR forthcoming.

created time in 2 months

issue closeddiablodale/dp.kinect2

Not able to register purchase

Description

When I go through the steps to register dp.kinect2 it fails. I get console errors that say "dp.kinect2 is not registered or has expired" , "general access denied"

Setup

  • Computer i7-7700HQ, 256GB SD, 16GB Ram
  • Windows 10 Home - version 1903
  • Installed Kinect for Windows SDK 2.0
  • Installed MAx 8.1.3, registered
  • Using dp.kinect2 version - dp.kinect2-v1.1.20170110
  • ...

Steps to reproduce

  1. Open Max
  2. create new patch
  3. create new object dp.kinect2
  4. right click to open dp.kinect2 help
  5. go to registration tab
  6. enter registration name from email, make sure it is spelled correctly and press button
  7. file browser opens, locate dp.kinect2 .dpreg file, press open
  8. go to first tab in help
  9. click to start

Result

get console error "dp.kinect2 is not registered or has expired" , "general access denied"

Expected Result

I expect the kinect to light up and work with the help patch like it did with the trial registration

Workarounds

no workarounds. Have tried many things, such as re-installing dp.kinect2, updating Max, rebooting... just really stubbornly won't register. Please note, my machine and kinect set up are working with TouchDesigner, Ableton, Unity 3D and Brekel softwares so it's probably not my system, hardware or kinect SDK. Also, I have not used an older kinect v1 with this machine so there should be no registration conflicts.

Max console output

Kinecterrors

When you set `@verbose 1`, additional debug messages were sent to the Max console.
Please copy and paste here...
1. The first group of messages from dp.kinect2 which provide version information and settings.
2. Include any diagnostic messages you find related to your issue. They will be in yellow/red color.

closed time in 2 months

krisforce

issue commentdiablodale/dp.kinect2

Not able to register purchase

Good to hear. That was the problem. Max was searching its path and found that old v0.x copy and loaded it before the v1.x version.

If you want, you should be able to run that machine learning demo also. Remove the old mxe/mxe64 within it. Then Max will find your newer mxe/mxe64 when it loads that ML patch.

Your license is good for any v1.x version. However, it doesn't work retroactive for old v0.x you might find floating around the Internet. I do grandfather old licenses forward. But I don't time-travel backwards. ;-)

Happy patching! :-)

krisforce

comment created time in 2 months

issue commentmicrosoft/vcpkg

[cpprestsdk] port missing package version file (can't use cmake package versioning)

I consider this specific issue closed. The cpprestsdk port fixed the version issue on 25 April 2020.

For those that find this issue, I've written a cmake helper function to require a specific semver or newer of any vcpkg installed package https://gist.github.com/diablodale/471341d2e139b0b42f4270c78f031378

diablodale

comment created time in 2 months

issue closedmicrosoft/vcpkg

[cpprestsdk] port missing package version file (can't use cmake package versioning)

The cpprestsdk port is missing the package version file. Therefore it is not possible in cmake to use package version checking as in find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

This is duplicate of the incorrectly dup-closed https://github.com/microsoft/vcpkg/issues/5231. The user @LilyWangL mistakenly collapsed two distinct issues as one. It is not a duplicate of https://github.com/microsoft/vcpkg/issues/5040

Repro

  1. Setup a working vspkg with VS2019
  2. vcpkg install cpprestsdk
  3. Create your app's CMakeLists.txt with the needed toolchain file
  4. Add to that CMakeLists.txt the following: find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

Result

[cmake] CMake Error at C:/njs/vcpkg/scripts/buildsystems/vcpkg.cmake:329 (_find_package):
[cmake]   Could not find a configuration file for package "cpprestsdk" that is
[cmake]   compatible with requested version "2.8.0".
[cmake] 
[cmake]   The following configuration files were considered but not accepted:
[cmake] 
[cmake]     C:/njs/vcpkg/installed/x86-windows-static-md-v142-sdk81/share/cpprestsdk/cpprestsdk-config.cmake, version: unknown
[cmake] 
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:127 (find_package)

Expected

No errors and a later successful compile using the cpprestsdk library.

Solution

Add package versioning information to the port as described in official cmake docs https://cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html#package-version-file

Notes

A repeat reminder...this is not an issue with vcpkg installing/compiling a specific version. Those are other open issues.

Instead, this is an issue with the port cpprestsdk does not contain the package version file. Therefore an app's CMakeLists.txt can not express or require a specific version of the port using find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

Describe alternatives you've considered

No reasonable alternative other than to remove package version in find_package(). Otherwise, the alternative is to implement what is already built into cmake.

closed time in 2 months

diablodale

issue closedmicrosoft/cpprestsdk

missing cmake package version file (can't use cmake package versioning)

The cpprestsdk port is missing the package version file. Therefore it is not possible in cmake to use package version checking as in find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

Repro

  1. Setup a working vcpkg with VS2019 for simplicity
  2. vcpkg install cpprestsdk
  3. Create your app's CMakeLists.txt with the needed toolchain file
  4. Add to that CMakeLists.txt the following: find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

Result

[cmake] CMake Error at C:/njs/vcpkg/scripts/buildsystems/vcpkg.cmake:329 (_find_package):
[cmake]   Could not find a configuration file for package "cpprestsdk" that is
[cmake]   compatible with requested version "2.8.0".
[cmake] 
[cmake]   The following configuration files were considered but not accepted:
[cmake] 
[cmake]     C:/njs/vcpkg/installed/x86-windows-static-md-v142-sdk81/share/cpprestsdk/cpprestsdk-config.cmake, version: unknown
[cmake] 
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:127 (find_package)

Expected

No errors and a later successful compile using the cpprestsdk library.

Solution

Add package versioning information to the port as described in official cmake docs https://cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html#package-version-file

Usually you just set the version as project's property, and then you use CMake's helpers to create a simple Config + Version file like

project(xxxx VERSION 2.8.0 LANGUAGES CXX)
...
include(CMakePackageConfigHelpers)
write_basic_package_version_file(
    ${CMAKE_CURRENT_BINARY_DIR}/xxxxxxxxxxxx.cmake
    COMPATIBILITY SameMajorVersion
)
install(FILES ${CMAKE_CURRENT_BINARY_DIR}/xxxxxxxxxxxxxx.cmake DESTINATION ${CMAKE_INSTALL_DATADIR}/cmake/xxxxxxxxxxxxxxxx)

Notes and related issues

No reasonable alternative other than to remove package version in find_package(). Otherwise, the alternative is to implement what is already built into cmake.

https://github.com/microsoft/cpprestsdk/issues/1382 https://github.com/microsoft/cpprestsdk/issues/686 https://github.com/microsoft/vcpkg/issues/10938

closed time in 2 months

diablodale

issue commentmicrosoft/cpprestsdk

missing cmake package version file (can't use cmake package versioning)

Ah-ha! This issue was fixed here 5 days after my original report on 20 April in the vcpkg repo. I just now tested with the current v2.10.16 and it happily works. Sorry for noise. Thanks for very helpful library -- I've used cpprest since 2016.

diablodale

comment created time in 2 months

issue openedmicrosoft/cpprestsdk

missing cmake package version file (can't use cmake package versioning)

The cpprestsdk port is missing the package version file. Therefore it is not possible in cmake to use package version checking as in find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

Repro

  1. Setup a working vcpkg with VS2019 for simplicity
  2. vcpkg install cpprestsdk
  3. Create your app's CMakeLists.txt with the needed toolchain file
  4. Add to that CMakeLists.txt the following: find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

Result

[cmake] CMake Error at C:/njs/vcpkg/scripts/buildsystems/vcpkg.cmake:329 (_find_package):
[cmake]   Could not find a configuration file for package "cpprestsdk" that is
[cmake]   compatible with requested version "2.8.0".
[cmake] 
[cmake]   The following configuration files were considered but not accepted:
[cmake] 
[cmake]     C:/njs/vcpkg/installed/x86-windows-static-md-v142-sdk81/share/cpprestsdk/cpprestsdk-config.cmake, version: unknown
[cmake] 
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:127 (find_package)

Expected

No errors and a later successful compile using the cpprestsdk library.

Solution

Add package versioning information to the port as described in official cmake docs https://cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html#package-version-file

Usually you just set the version as project's property, and then you use CMake's helpers to create a simple Config + Version file like

project(xxxx VERSION 2.8.0 LANGUAGES CXX)
...
include(CMakePackageConfigHelpers)
write_basic_package_version_file(
    ${CMAKE_CURRENT_BINARY_DIR}/xxxxxxxxxxxx.cmake
    COMPATIBILITY SameMajorVersion
)
install(FILES ${CMAKE_CURRENT_BINARY_DIR}/xxxxxxxxxxxxxx.cmake DESTINATION ${CMAKE_INSTALL_DATADIR}/cmake/xxxxxxxxxxxxxxxx)

Notes and related issues

No reasonable alternative other than to remove package version in find_package(). Otherwise, the alternative is to implement what is already built into cmake.

https://github.com/microsoft/cpprestsdk/issues/1382 https://github.com/microsoft/cpprestsdk/issues/686 https://github.com/microsoft/vcpkg/issues/10938

created time in 2 months

issue commentdiablodale/dp.kinect2

Not able to register purchase

Hi. Unfortunately, that 2nd screenshot doesn't match my needs.

Would you please follow your repro steps 1-7 again and capture the Max console output? The screenshot you attached shows a lot of activity that is hiding diagnostic information. Please only do steps 1-7. Don't click on any part of tab 1. And please ensure that the full Max console window is in the picture. Therefore, it should show the dp.kinect2 startup information like its version, 32/64-bit, copyright, etc.

krisforce

comment created time in 2 months

issue commentdiablodale/dp.kinect2

Not able to register purchase

While you gather the above three things, please look specifically at the dp.kinect2 version that appears in the Max console when it first starts up. One possibility that would match your error code, is if you are trying to use your newly bought license with an early (v0.xxx) release of dp.kinect2. You might have such a pre-release version of dp.kinect2 on your Max path. Max has a very specific order of directories it checks when you use the method in step 3 of your repro steps.

krisforce

comment created time in 2 months

issue commentdiablodale/dp.kinect2

Not able to register purchase

Hi. The diagnostic codes that I can see are consistent with what I previously wrote. So I want to get more diagnostics to resolve this.

Would you please follow your repro steps 1-7 again and capture the Max console output? The screenshot you attached shows a lot of activity that is hiding diagnostic information. Please only do steps 1-7. Don't click on any part of tab 1. And please ensure that the full Max console window is in the picture. Therefore, it should show the dp.kinect2 startup information like its version, 32/64-bit, copyright, etc.

At step 7, what happens on that registration tab. Do you see a green "registered" or yellow "not registered"?

And is this machine connected to the internet? And is Max itself allowed to connect to the internet (perhaps your have a firewall or virus blocking it? This shouldn't cause this failure. However, if it is connected to the Internet, I might be able to see something in my license server logs.

krisforce

comment created time in 2 months

issue commentdiablodale/dp.kinect2

get skeleton joints to color coordinates (x,y)

Hi. I have two questions.

  1. I have a early build you can try. Would you contact me by email @diablodale and ask for it? It has the depthtoskel, depthtocolor, skeltocolor, skeltodepth methods that you can give one or more coordinates and it will return answers for them like pixeltoskel does today.
  2. I am unsure how skelcolor and skeldepth messages on the 5th outlet output relate to @distmeter, @position, @quat, @rotate, @rotatexyz, and @scale. I do understand how to use @flipx and @align.

Here is the scenario.

  1. A patch tells dp.kinect2 to transform joint data using one or more of the attributes @distmeter, @position, @quat, @rotate, @rotatexyz, and @scale.
  2. A patch turns on output of the skelcolor messages for outlet 5.

Does the message skelcolor 1 l_hand give color coordinates of the un-transformed joint? Or does it apply the joint transform(s) and then calculate/output the color coordinate?

I can code either approach. But I don't yet see the benefit of the 2nd (transform+color). Because the joint's color coordinate that would be output would not align with the colormap matrix being output on outlet 2. So while I could do it...is that useful? I guess you could use @position or @quat to make the skeleton joints "beside" you...like a twin. And then use the output of skelcolor to draw the skeleton "twin" on the colormap matrix.

I'm unsure. What is your thinking on this?

silicatproject

comment created time in 2 months

issue openedmicrosoft/GSL

missing cmake package version file (can't use cmake package versioning)

GSL is missing the cmake package version file. Therefore it is not possible in cmake to use package version checking as in find_package(Microsoft.GSL 3.0.1 CONFIG REQUIRED)

Repro (using vcpkg for ease)

  1. Setup a working vcpkg with VS2019, e.g. using your instructions at https://github.com/microsoft/gsl#building-gsl---using-vcpkg
  2. vcpkg install ms-gsl
  3. Create your app's CMakeLists.txt with the needed toolchain file
  4. Add to that CMakeLists.txt the following: find_package(Microsoft.GSL 3.0.1 CONFIG REQUIRED)

Result

[cmake] CMake Error at C:/njs/vcpkg/scripts/buildsystems/vcpkg.cmake:329 (_find_package):
[cmake]   Could not find a configuration file for package "Microsoft.GSL" that is
[cmake]   compatible with requested version "3.0.1".
[cmake] 
[cmake]   The following configuration files were considered but not accepted:
[cmake] 
[cmake]     C:/njs/vcpkg/installed/x64-windows-static-md-v142-sdk81/share/Microsoft.GSL/Microsoft.GSLConfig.cmake, version: unknown
[cmake] 
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:164 (find_package)
[cmake] -- Configuring incomplete, errors occurred!```

Expected

No errors and a later successful compile using the GSL library.

Solution

Add package versioning information to the port as described in official cmake docs https://cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html#package-version-file

Notes

No reasonable alternative other than to remove package version in find_package(). Otherwise, the alternative is to implement what is already built into cmake.

created time in 2 months

issue commentdiablodale/dp.kinect2

get skeleton joints to color coordinates (x,y)

I'm unsure of the guaranteed order of the three skeleton coordinate messages. These messages (0, 1, 2, or all 3) would be output before any of the matrices (pointcloud, player, ir, color, depth) since outlet order is right->left.

Approach 1 would use skel as the änchor"and consistently final message. The other two could be either order. Perhaps skelcolor, skeldepth, skel

Approach 2 would be somewhat the same as outlet output (right->left). Meaning skel, skelcolor, skeldepth.

My instinct tells me approach 1, but I don't have any facts to support it. Do you have an opinion on this topic?

silicatproject

comment created time in 2 months

issue commentdiablodale/dp.kinect2

get skeleton joints to color coordinates (x,y)

Hi. I think it is possible to include some of these enhancements to dp.kinect2. Would you be willing to try and test some early builds? And could you help exercise/test it so we can be sure it meets your needs and performs well?

silicatproject

comment created time in 2 months

issue openedmicrosoft/WSL

WSL2 with wsl.conf "uid=1000,gid=1000" duplicates uid and gid in actual mount

WSL2 with a wsl.conf file having automount options for uid and gid duplicates them in actual mount

Setup

  • Windows 10 2004 build 19041.207
  • fresh install of distro Debian from Windows Store
  • fresh change of that Debian distro to WSL2
  • updated WSL2 kernel as needed to switch distro to WSL2

Repro

  1. Run Debian
  2. create a /etc/wsl.conf with the following content
    [automount]
    options = "metadata,uid=1000,gid=1000,fmask=0027,dmask=0027"
    
  3. Terminate the Debian distro
  4. Run Debian
  5. at the prompt run mount

Result

The mount info for the C drive will have duplicated uid and gid in it 👯‍♀️

C:\ on /mnt/c type 9p (rw,noatime,dirsync,aname=drvfs;path=C:\;uid=1000;gid=1000;metadata;uid=1000;gid=1000;fmask=0027;dmask=0027;symlinkroot=/mnt/,mmap,access=client,msize=65536,trans=fd,rfd=8,wfd=8)

Expected

The uid and gid to be listed only once, and it to be the uid and gid specified in wsl.conf

Notes

I have not yet noticed harm if the gid and uid are the same as the duplicates. I do not know when they are different that harm occurs. Or other combinations.

In general, the official doc for WSL2 points to the official doc for WSL Distro management https://docs.microsoft.com/en-us/windows/wsl/wsl-config which writes

By default, WSL sets the uid and gid to the value of the default user (in Ubuntu distro, the default user is created with uid=1000,gid=1000). If the user specifies a gid or uid option explicitly via this key, the associated value will be overwritten. Otherwise, the default value will always be appended.

Therefore, I believe whatever code is putting the duplicate, should be overwritten by the gid,uid specified in wsl.conf

created time in 2 months

issue commentmicrosoft/vscode-cpptools

intellisense uses newest SDK instead of specified Win8.1

That is the original scenario. It does set "C_Cpp.default.windowsSdkVersion": "8.1" Install the scenario to your computer and watch the fun. Intellisense ignores all my attempts to force 8.1.

diablodale

comment created time in 2 months

issue commentmicrosoft/vscode-cpptools

intellisense uses newest SDK instead of specified Win8.1

Got it. Doesn't work. 🙃 Unfortunately the workaround idea has a worse outcome.

Clarification

  1. Is the cpp extension intellisense in all configuration possibilities only use the most current SDK? If not, what combination allows selection of the WinKit?
  2. Does the setting C_Cpp.default.windowsSdkVersion": "8.1" work in some other combination of config? If not, what is the use of that setting? Is it time to disable/warn of its usage?

Fail of workaround idea

Unfortunately, removing all Win10 kits was a worse outcome. 🤦‍♀️😁 When I do this, the cpp intellisense then puts a red squiggle on #include <Windows.h> and aborts further intellisense checks; meaning that there are no red squiggles anywhere else. Which since these are core Windows includes and in many files, this makes intellisense pervasively unworkable. Its actually "better" to leave a Win10 kit installed so at least I have intellisense and only the occasionally wrong red squiggle.

I also noticed that if I click #include <Windows.h> and F12, it correctly goes to the WinKit 8.1 header. This is different-esque behavior than with a WinKit 10.x installed when I would click the SYSTEM_POWER_STATUS and F12, it would go to the WinKit 10.x header.

The logs below are my computer which now has no Windows Kit 10.x installed, only the Windows 8.1 Kit (from the VS2017 installer).

<details><summary>C/C++ diag log</summary>

-------- Diagnostics - 4/21/2020, 4:47:45 PM
Version: 0.27.0
Current Configuration:
{
    "name": "Win32",
    "includePath": [
        "${workspaceFolder}/**",
        "${vcpkgRoot}/x64-windows-static-md/include",
        "${vcpkgRoot}/x64-windows-static-md-v142-sdk10b17134/include",
        "${vcpkgRoot}/x64-windows-static-md-v142-sdk81/include",
        "${vcpkgRoot}/x86-windows-static-md-v142-sdk10b17134/include",
        "${vcpkgRoot}/x86-windows-static-md-v142-sdk81/include"
    ],
    "defines": [
        "_DEBUG",
        "UNICODE",
        "_UNICODE"
    ],
    "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe",
    "cStandard": "c11",
    "cppStandard": "c++17",
    "windowsSdkVersion": "8.1",
    "compilerArgs": [],
    "intelliSenseMode": "msvc-x64",
    "configurationProvider": "vector-of-bool.cmake-tools",
    "browse": {
        "path": [
            "${workspaceFolder}/**",
            "${vcpkgRoot}/x64-windows-static-md/include",
            "${vcpkgRoot}/x64-windows-static-md-v142-sdk10b17134/include",
            "${vcpkgRoot}/x64-windows-static-md-v142-sdk81/include",
            "${vcpkgRoot}/x86-windows-static-md-v142-sdk10b17134/include",
            "${vcpkgRoot}/x86-windows-static-md-v142-sdk81/include"
        ],
        "limitSymbolsToIncludedHeaders": true
    }
}
Translation Unit Mappings:
[ C:\njs\cpp-bug-winsdk81\cppsdkbug.cpp ]:
    C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Translation Unit Configurations:
[ C:\njs\cpp-bug-winsdk81\cppsdkbug.cpp ]:
    Process ID: 11924
    Memory Usage: 87 MB
    Compiler Path: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe
    Includes:
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
        C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
        C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
        C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
    Defines:
        cppsdkbug_EXPORTS
        WIN32
        _WINDOWS
    Standard Version: ms_c++17
    IntelliSense Mode: msvc-x64
Total Memory Usage: 87 MB

</details>

<details><summary>Language Server</summary>

initialized
cpptools/queryCompilerDefaults (id: 1)
Attempting to get defaults from compiler found on the machine: 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe'
Attempting to get defaults from compiler found on the machine: 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe'
Custom browse configuration received: {
  "browsePath": [
    "c:/njs/cpp-bug-winsdk81"
  ],
  "standard": "c++17",
  "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe",
  "compilerArgs": [
    "/DWIN32",
    "/D_WINDOWS",
    "/GR",
    "/EHsc",
    "/Zi",
    "/Ob0",
    "/Od",
    "/RTC1",
    "-MDd"
  ]
}
cpptools/didChangeCppProperties
Attempting to get defaults from compiler found on the machine: 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe'
Code browsing service initialized
Attempting to get defaults from compiler found on the machine: 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe'
  Folder: C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/INCLUDE/* will be indexed
  Folder: C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/ATLMFC/INCLUDE/* will be indexed
  Folder: C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/UM/ will be indexed
  Folder: C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/SHARED/ will be indexed
  Folder: C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/WINRT/ will be indexed
  Folder: C:/NJS/CPP-BUG-WINSDK81/ will be indexed
  Folder: C:/NJS/VCPKG/INSTALLED/X64-WINDOWS-STATIC-MD/INCLUDE/ will be indexed
  Folder: C:/NJS/VCPKG/INSTALLED/X64-WINDOWS-STATIC-MD-V142-SDK10B17134/INCLUDE/ will be indexed
  Folder: C:/NJS/VCPKG/INSTALLED/X64-WINDOWS-STATIC-MD-V142-SDK81/INCLUDE/ will be indexed
  Folder: C:/NJS/VCPKG/INSTALLED/X86-WINDOWS-STATIC-MD-V142-SDK10B17134/INCLUDE/ will be indexed
  Folder: C:/NJS/VCPKG/INSTALLED/X86-WINDOWS-STATIC-MD-V142-SDK81/INCLUDE/ will be indexed
cpptools/didChangeCustomBrowseConfiguration
Attempting to get defaults from compiler found on the machine: 'C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe'
  Folder: C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/INCLUDE/* will be indexed
  Folder: C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/ATLMFC/INCLUDE/* will be indexed
  Folder: C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/UM/ will be indexed
  Folder: C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/SHARED/ will be indexed
  Folder: C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/WINRT/ will be indexed
  Folder: C:/NJS/CPP-BUG-WINSDK81/ will be indexed
textDocument/didOpen: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Populate include completion cache.
Discovering files...
cpptools/activeDocumentChange: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/textEditorSelectionChange
cpptools/getDocumentSymbols: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp (id: 2)
cpptools/getDocumentSymbols
cpptools/clearCustomConfigurations
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
  Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/INCLUDE
  Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/ATLMFC/INCLUDE
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/UM/
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
  tag parsing file: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE\CODEANALYSIS\SOURCEANNOTATIONS.H
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\NJS\VCPKG\INSTALLED\X64-WINDOWS-STATIC-MD\INCLUDE
  include: C:\NJS\VCPKG\INSTALLED\X64-WINDOWS-STATIC-MD-V142-SDK10B17134\INCLUDE
  include: C:\NJS\VCPKG\INSTALLED\X64-WINDOWS-STATIC-MD-V142-SDK81\INCLUDE
  include: C:\NJS\VCPKG\INSTALLED\X86-WINDOWS-STATIC-MD-V142-SDK10B17134\INCLUDE
  include: C:\NJS\VCPKG\INSTALLED\X86-WINDOWS-STATIC-MD-V142-SDK81\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
  define: _DEBUG
  define: UNICODE
  define: _UNICODE
  stdver: ms_c++17
  intelliSenseMode: msvc-x64
Shutting down IntelliSense server: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/SHARED/
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/WINRT/
  Processing folder (recursive): C:/NJS/CPP-BUG-WINSDK81/
  Discovering files: 2807 file(s) processed
  0 file(s) removed from database
Done discovering files.
Parsing remaining files...
  Parsing: 0 files(s) processed
Done parsing remaining files.
Closing the communication channel.
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\NJS\VCPKG\INSTALLED\X64-WINDOWS-STATIC-MD\INCLUDE
  include: C:\NJS\VCPKG\INSTALLED\X64-WINDOWS-STATIC-MD-V142-SDK10B17134\INCLUDE
  include: C:\NJS\VCPKG\INSTALLED\X64-WINDOWS-STATIC-MD-V142-SDK81\INCLUDE
  include: C:\NJS\VCPKG\INSTALLED\X86-WINDOWS-STATIC-MD-V142-SDK10B17134\INCLUDE
  include: C:\NJS\VCPKG\INSTALLED\X86-WINDOWS-STATIC-MD-V142-SDK81\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
  define: _DEBUG
  define: UNICODE
  define: _UNICODE
  stdver: ms_c++17
  intelliSenseMode: msvc-x64
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Error squiggles will be disabled in: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Update IntelliSense time (sec): 3.621
Database safe to open
cpptools/didChangeSettings
IntelliSense Engine = Default.
Enhanced Colorization is enabled.
Error squiggles are enabled if all header dependencies are resolved.
Autocomplete is enabled.
File exclude: **/.git
File exclude: **/.svn
File exclude: **/.hg
File exclude: **/CVS
File exclude: **/.DS_Store
File exclude: **/.vscode
Search exclude: **/node_modules
Search exclude: **/bower_components
Search exclude: **/*.code-search
Search exclude: **/.vscode
$/setTraceNotification
Populate include completion cache.
Discovering files...
  Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/INCLUDE
cpptools/getDocumentSymbols: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp (id: 3)
cpptools/getDocumentSymbols
  Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/ATLMFC/INCLUDE
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/UM/
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/SHARED/
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/8.1/INCLUDE/WINRT/
  Processing folder (recursive): C:/NJS/CPP-BUG-WINSDK81/
  Discovering files: 2807 file(s) processed
  1 file(s) removed from database
Done discovering files.
Parsing remaining files...
  Parsing: 0 files(s) processed
Done parsing remaining files.
cpptools/getDocumentSymbols: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp (id: 4)
cpptools/getDocumentSymbols
cpptools/fileCreated: file:///c%3A/njs/cpp-bug-winsdk81/build/.cmake/api/v1/reply/index-2020-04-21T14-44-43-0682.json
cpptools/fileDeleted: file:///c%3A/njs/cpp-bug-winsdk81/build/.cmake/api/v1/reply/index-2020-04-21T14-43-19-0003.json
Custom configuration provider 'CMake Tools' registered
Custom browse configuration received: {
  "browsePath": [
    "c:/njs/cpp-bug-winsdk81"
  ],
  "standard": "c++17",
  "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe",
  "compilerArgs": [
    "/DWIN32",
    "/D_WINDOWS",
    "/GR",
    "/EHsc",
    "/Zi",
    "/Ob0",
    "/Od",
    "/RTC1",
    "-MDd"
  ]
}
cpptools/pauseParsing
cpptools/clearCustomConfigurations
Closing the communication channel.
Shutting down IntelliSense server: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/queryTranslationUnitSource: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp (id: 5)
Custom configurations received:
  uri: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
  config: {
  "defines": [
    "cppsdkbug_EXPORTS",
    "WIN32",
    "_WINDOWS"
  ],
  "standard": "c++17",
  "includePath": [],
  "intelliSenseMode": "msvc-x64",
  "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe",
  "compilerArgs": [
    "/DWIN32",
    "/D_WINDOWS",
    "/GR",
    "/EHsc",
    "/Zi",
    "/Ob0",
    "/Od",
    "/RTC1",
    "-MDd"
  ]
}
Custom browse configuration received: {
  "browsePath": [
    "c:/njs/cpp-bug-winsdk81"
  ],
  "standard": "c++17",
  "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe",
  "compilerArgs": [
    "/DWIN32",
    "/D_WINDOWS",
    "/GR",
    "/EHsc",
    "/Zi",
    "/Ob0",
    "/Od",
    "/RTC1",
    "-MDd"
  ]
}
cpptools/didChangeCustomBrowseConfiguration
cpptools/didChangeCustomConfiguration
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/resumeParsing
cpptools/clearCustomConfigurations
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/queryTranslationUnitSource: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp (id: 6)
Custom configurations received:
  uri: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
  config: {
  "defines": [
    "cppsdkbug_EXPORTS",
    "WIN32",
    "_WINDOWS"
  ],
  "standard": "c++17",
  "includePath": [],
  "intelliSenseMode": "msvc-x64",
  "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe",
  "compilerArgs": [
    "/DWIN32",
    "/D_WINDOWS",
    "/GR",
    "/EHsc",
    "/Zi",
    "/Ob0",
    "/Od",
    "/RTC1",
    "-MDd"
  ]
}
cpptools/didChangeCustomBrowseConfiguration
cpptools/didChangeCustomConfiguration
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/resumeParsing
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
  define: cppsdkbug_EXPORTS
  define: WIN32
  define: _WINDOWS
  stdver: ms_c++17
  intelliSenseMode: msvc-x64
Shutting down IntelliSense server: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Closing the communication channel.
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
  define: cppsdkbug_EXPORTS
  define: WIN32
  define: _WINDOWS
  stdver: ms_c++17
  intelliSenseMode: msvc-x64
Shutting down IntelliSense server: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Closing the communication channel.
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
  define: cppsdkbug_EXPORTS
  define: WIN32
  define: _WINDOWS
  stdver: ms_c++17
  intelliSenseMode: msvc-x64
Shutting down IntelliSense server: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Closing the communication channel.
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
  define: cppsdkbug_EXPORTS
  define: WIN32
  define: _WINDOWS
  stdver: ms_c++17
  intelliSenseMode: msvc-x64
Shutting down IntelliSense server: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Closing the communication channel.
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
  define: cppsdkbug_EXPORTS
  define: WIN32
  define: _WINDOWS
  stdver: ms_c++17
  intelliSenseMode: msvc-x64
Shutting down IntelliSense server: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Closing the communication channel.
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\8.1\INCLUDE\WINRT
  define: cppsdkbug_EXPORTS
  define: WIN32
  define: _WINDOWS
  stdver: ms_c++17
  intelliSenseMode: msvc-x64
Database safe to open
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Error squiggles will be disabled in: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Update IntelliSense time (sec): 4.686
textDocument/hover: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp (id: 7)
cpptools/getCodeActions: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp (id: 8)
cpptools/activeDocumentChange: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/textEditorSelectionChange
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Update IntelliSense time (sec): 0.255
cpptools/activeDocumentChange: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/textEditorSelectionChange
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Update IntelliSense time (sec): 0.289
cpptools/getCodeActions: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp (id: 9)
cpptools/activeDocumentChange: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/textEditorSelectionChange
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Update IntelliSense time (sec): 0.271
cpptools/getDiagnostics (id: 10)
cpptools/activeDocumentChange: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/textEditorSelectionChange
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Update IntelliSense time (sec): 0.263
cpptools/activeDocumentChange: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
cpptools/textEditorSelectionChange
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
cpptools/cpptools_finishUpdateSquiggles
Error squiggle count: 6
Update IntelliSense time (sec): 0.261

</details>

diablodale

comment created time in 2 months

issue commentmicrosoft/vcpkg

[cpprestsdk] port missing package version file (can't use cmake package versioning)

❔😵 Maaybe. Happy to move the convo over there if so.

I see a correct version in structured fields in both this repo's portfile.cmake and CONTROL for cpprestsdk. At my current level of understanding, I don't know if vcpkg.exe uses/exposes/mutates those versions so they are exposed to vcpkg's CMAKE_TOOLCHAIN_FILE, etc. Or perhaps "helps" ports by autogen such cmake version if if that port doesn't do it themselves.

diablodale

comment created time in 2 months

issue openedmicrosoft/vscode-cpptools

intellisense uses newest SDK instead of specified Win8.1

Type: LanguageService

vscode cpp extension Intellisense for a cmake c++ project uses the newest "Windows Kit" 10.0.17763.0 instead of the Windows Kit 8.1 specified in multiple places in settings.json, c_cpp_properties.json and/or cmake-kits.json.

Similar but doesn't seem same as #1305, #4164 🤔

Setup

  • Host is Windows 10 version 1909 build 18363.778
  • VS Code Version
    Version: 1.44.2 (system setup)
    Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
    Date: 2020-04-16T16:36:23.138Z
    Electron: 7.1.11
    Chrome: 78.0.3904.130
    Node.js: 12.8.1
    V8: 7.8.279.23-electron.0
    OS: Windows_NT x64 10.0.18363
    
  • C/C++ Extension Version: 0.27.0
  • Other Extensions: only the necessary ms-vscode.cmake-tools v1.3.1
  • Cmake 3.15
  • VS Community 2019: C++ Desktop workload, WinSDK 10.0.17134, Windows Universal C Runtime
  • VS Community 2017 (same shared installer): C++ Desktop workload, Windows 8.1 SDK, VC++ 2015.3 v14.00 toolset
  • No SSH remote anything

Repro steps

  1. Configure computer, apps, and vscode as in setup above
  2. Unzip this attached ZIP to an empty folder --> cppkit81.zip
  3. Open VSCode into that folder
  4. Click cmake in left nav
  5. Click 3-dot menu above tree pane, choose Clean Configure All Projects
  6. Click 3-dot menu above tree pane, choose Clean Rebuild All Projects
  7. Open the file cppsdkbug.cpp and view the code
  8. Open the build output tab and view the build results

Result

You will have two red squiggle errors, on line 7 and line 9. This is incorrect.

Line 7 references a field in a struct named Reserved1. This is valid in Windows Kit 8.1. Line 9 references a field in a struct named SystemStatusFlag. This is valid in Windows Kit 10+

Expected

Only a red squiggle error on line 9.

Why?

The project given in the ZIP file declares to use the Windows Kit 8.1.

Line 7 red squiggle is incorrectly generated by cpp extension intellisense. It is using the wrong path to the winbase.h header file. It is using the WinKit 10+ ☹ Line 9 red squiggle is correctly generated by the compiler's build output. The compiler is correctly using the WinKit 8.1.

Notice in the logs below, the language server is processing C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.17763.0/UM/. It should not. Instead should be processing the equivalent WinKit8.1 folder C:\Program Files (x86)\Windows Kits\8.1\Include\um\

Notice no kits are populated as written about at https://github.com/Microsoft/vscode-cpptools/issues/1305#issuecomment-349017948

Logs

<details><summary>C/C++ Log Diagnostics</summary>

-------- Diagnostics - 4/21/2020, 3:59:56 AM
Version: 0.27.0
Current Configuration:
{
    "name": "Win32",
    "includePath": [
        "${workspaceFolder}/**",
        "${vcpkgRoot}/x64-windows-static-md/include",
        "${vcpkgRoot}/x64-windows-static-md-v142-sdk10b17134/include",
        "${vcpkgRoot}/x64-windows-static-md-v142-sdk81/include",
        "${vcpkgRoot}/x86-windows-static-md-v142-sdk10b17134/include",
        "${vcpkgRoot}/x86-windows-static-md-v142-sdk81/include"
    ],
    "defines": [
        "_DEBUG",
        "UNICODE",
        "_UNICODE"
    ],
    "compilerPath": "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe",
    "cStandard": "c11",
    "cppStandard": "c++17",
    "windowsSdkVersion": "8.1",
    "compilerArgs": [],
    "intelliSenseMode": "msvc-x64",
    "configurationProvider": "vector-of-bool.cmake-tools",
    "browse": {
        "path": [
            "${workspaceFolder}/**",
            "${vcpkgRoot}/x64-windows-static-md/include",
            "${vcpkgRoot}/x64-windows-static-md-v142-sdk10b17134/include",
            "${vcpkgRoot}/x64-windows-static-md-v142-sdk81/include",
            "${vcpkgRoot}/x86-windows-static-md-v142-sdk10b17134/include",
            "${vcpkgRoot}/x86-windows-static-md-v142-sdk81/include"
        ],
        "limitSymbolsToIncludedHeaders": true
    }
}
Translation Unit Mappings:
[ C:\njs\cpp-bug-winsdk81\cppsdkbug.cpp ]:
    C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Translation Unit Configurations:
[ C:\njs\cpp-bug-winsdk81\cppsdkbug.cpp ]:
    Process ID: 12188
    Memory Usage: 19 MB
    Compiler Path: C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/VC/Tools/MSVC/14.25.28610/bin/Hostx64/x64/cl.exe
    Includes:
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\UM
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\UCRT
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\SHARED
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\WINRT
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\CPPWINRT
    Defines:
        cppsdkbug_EXPORTS
        WIN32
        _WINDOWS
    Standard Version: ms_c++17
    IntelliSense Mode: msvc-x64
Total Memory Usage: 19 MB

</details>

<details><summary>Language Server</summary>

File exclude: **/.git
File exclude: **/.svn
File exclude: **/.hg
File exclude: **/CVS
File exclude: **/.DS_Store
File exclude: **/.vscode
Search exclude: **/node_modules
Search exclude: **/bower_components
Search exclude: **/*.code-search
Search exclude: **/.vscode
Populate include completion cache.
Discovering files...
  Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/INCLUDE
  Processing folder (non-recursive): C:/PROGRAM FILES (X86)/MICROSOFT VISUAL STUDIO/2019/COMMUNITY/VC/TOOLS/MSVC/14.25.28610/ATLMFC/INCLUDE
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.17763.0/UM/
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.17763.0/UCRT/
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.17763.0/SHARED/
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.17763.0/WINRT/
  Processing folder (recursive): C:/PROGRAM FILES (X86)/WINDOWS KITS/10/INCLUDE/10.0.17763.0/CPPWINRT/
  Processing folder (recursive): C:/NJS/CPP-BUG-WINSDK81/
  Discovering files: 4773 file(s) processed
  142 file(s) removed from database
Done discovering files.
Parsing remaining files...
  Parsing: 0 files(s) processed
Done parsing remaining files.
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\UCRT
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\WINRT
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\CPPWINRT
  define: cppsdkbug_EXPORTS
  define: WIN32
  define: _WINDOWS
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Error squiggle count: 1
Update IntelliSense time (sec): 0.504
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Error squiggle count: 1
Update IntelliSense time (sec): 0.261
Shutting down IntelliSense server: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Closing the communication channel.
sending compilation args for C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
  include: C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\UM
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\UCRT
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\SHARED
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\WINRT
  include: C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\CPPWINRT
  define: cppsdkbug_EXPORTS
  define: WIN32
  define: _WINDOWS
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Error squiggle count: 1
Update IntelliSense time (sec): 0.698
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Error squiggle count: 1
Update IntelliSense time (sec): 0.258
idle loop: reparsing the active document
Checking for syntax errors: file:///c%3A/njs/cpp-bug-winsdk81/cppsdkbug.cpp
Queueing IntelliSense update for files in translation unit of: C:\NJS\CPP-BUG-WINSDK81\CPPSDKBUG.CPP
Error squiggle count: 1
Update IntelliSense time (sec): 0.255

</details>

created time in 2 months

issue openedmicrosoft/vcpkg

[cpprestsdk] port missing package version file (can't use cmake package versioning)

The cpprestsdk port is missing the package version file. Therefore it is not possible in cmake to use package version checking as in find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

This is duplicate of the incorrectly dup-closed https://github.com/microsoft/vcpkg/issues/5231. The user @LilyWangL mistakenly collapsed two distinct issues as one. It is not a duplicate of https://github.com/microsoft/vcpkg/issues/5040

Repro

  1. Setup a working vspkg with VS2019
  2. vcpkg install cpprestsdk
  3. Create your app's CMakeLists.txt with the needed toolchain file
  4. Add to that CMakeLists.txt the following: find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

Result

[cmake] CMake Error at C:/njs/vcpkg/scripts/buildsystems/vcpkg.cmake:329 (_find_package):
[cmake]   Could not find a configuration file for package "cpprestsdk" that is
[cmake]   compatible with requested version "2.8.0".
[cmake] 
[cmake]   The following configuration files were considered but not accepted:
[cmake] 
[cmake]     C:/njs/vcpkg/installed/x86-windows-static-md-v142-sdk81/share/cpprestsdk/cpprestsdk-config.cmake, version: unknown
[cmake] 
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:127 (find_package)

Expected

No errors and a later successful compile using the cpprestsdk library.

Solution

Add package versioning information to the port as described in official cmake docs https://cmake.org/cmake/help/v3.0/manual/cmake-packages.7.html#package-version-file

Notes

A repeat reminder...this is not an issue with vcpkg installing/compiling a specific version. Those are other open issues.

Instead, this is an issue with the port cpprestsdk does not contain the package version file. Therefore an app's CMakeLists.txt can not express or require a specific version of the port using find_package(cpprestsdk 2.8.0 CONFIG REQUIRED)

Describe alternatives you've considered

No reasonable alternative other than to remove package version in find_package(). Otherwise, the alternative is to implement what is already built into cmake.

created time in 2 months

push eventdiablodale/maxcpp

push time in 3 months

push eventdiablodale/maxcpp

Dale Phurrough

commit sha a7857134b084c60839db7d78312d7d30374326d4

init common syms only once

view details

Dale Phurrough

commit sha 318bef2f2a18acf0fc7a2d637ff9e44c76579510

safer outlet_anything() prototype from Max 7 SDK

view details

push time in 3 months

issue commentmicrosoft/WSL

rsync fails with non-writable targets on mounted ntfs filesystems

I have a guess to the cause of the errant behavior.

I've pushed TBs of data using rsync on WSL1. Yet, I can repo the OP on... Win10 18363.778 WSL1 Ubuntu 18.04.4 LTS with 4.4.0-18362-Microsoft

However, those same steps don't have error (a and b have same content) on... Native host... Ubuntu 18.04.4 LTS with 5.3.0-46-generic

Interestingly, I've never encountered this error in the 2+ years pushing GBs of data nightly using rsync from that same WSL1 system. It pushes to that native Ubuntu on a LAN. And to a Linux server on the Internet. Both using the rsync remote over ssh method.

Contrast the same OP steps but use cp a b instead. This will fail with a similar permission denied. Why? Because b is read-only...and cp protects us...it doesn't do invisible extra work like rsync. Rsync does extra work...it will manipulate files/metadata to force its work...so it will manipulate the destination file/folders metadata to match the goal (since goals are both file content and metadata).

It is expected behavior when all write bits are removed in WSL that Windows native file bit is marked read-only. https://devblogs.microsoft.com/commandline/chmod-chown-wsl-improvements/ see caveat 2.

Since this chmod -w behavior triggers caveat 2 and leads to the Windows native file bit read-only...and since the Windows native file bits supersede and can't be overridden by WSL...that means that when rsync does its "extra work" that it can't. The linux api calls that rsync makes in WSL can't override the Windows native read-only file bit.

That's my guess.

As a workaround...if your setup allows, can you use rsync remote? Even if the rsync is remote to the same machine? Or don't do a chmod -w and instead a subset like `chmod go-w' 🤔

kristjanvalur

comment created time in 3 months

push eventdiablodale/dp.kinect2

Dale Phurrough

commit sha 5f4adde1943667fa67410985b14919b1dd739f4c

Update bug_report.md

view details

push time in 3 months

issue commentmicrosoft/vscode-docker

attach shell (right-click) fails; it doesn't use docker host (aka docker.host setting)

Matthew, please delete via PRV0020176

diablodale

comment created time in 3 months

issue commentmicrosoft/vscode-docker

Container names to attach are incorrect; names combined from adjacent containers

Matthew, please delete via PRV0020176

diablodale

comment created time in 3 months

issue commentmicrosoft/vscode-cpptools

Need a setting to force case-sensitive folder support

Blindly uppercasing all alphabetic ASCII characters corrupts the paths of/when using cross-platform projects and libraries. The paths/files of these libraries and git repos are correct and fully expressed with cases. For example, this C++ extension fails to work correctly with the CMake extension. The CMake extension leads to generation of compile_commands.json for example:

[
{
  "directory": "C:/njs/dp.kinect3/build",
  "command": "C:\\PROGRA~2\\MICROS~1\\2019\\COMMUN~1\\VC\\Tools\\MSVC\\1425~1.286\\bin\\Hostx64\\x64\\cl.exe   /TP -DEXT_WIN_VERSION -DINTERNAL_JIT_ANIM -DMAXAPI_USE_MSCRT -DWIN64 -DWIN_VERSION -D_DEBUG -D_NO_ASYNCRTIMP -D_NO_PPLXIMP -D_USRDLL -D_WINDLL -Ddp_kinect3_EXPORTS -I. -IC:\\njs\\max-sdk\\source\\c74support\\max-includes -IC:\\njs\\max-sdk\\source\\c74support\\jit-includes -IC:\\njs\\max-sdk\\source\\c74support\\msp-includes -IC:\\njs\\maxcpp\\maxcpp -I\"C:\\Program Files\\Azure Kinect SDK v1.4.0\\sdk\\include\"  /DWIN32 /D_WINDOWS /GR /EHsc /Zi /Ob0 /Od /RTC1 -MDd /GL   /W4 /wd4200 /WX /ZH:SHA_256 /arch:AVX -std:c++17 /FoCMakeFiles\\dp.kinect3.dir\\dp.kinect3.cpp.obj /FdTARGET_COMPILE_PDB /FS -c C:\\njs\\dp.kinect3\\dp.kinect3.cpp",
  "file": "C:/njs/dp.kinect3/dp.kinect3.cpp"
}
]

The path -IC:\\njs\\maxcpp\\maxcpp is correctly expressed. And the project correctly compiles and links. The failures are isolated to this C++ extension and its intellisense functionality.

C:\njs>fsutil.exe file queryCaseSensitiveInfo maxcpp
Case sensitive attribute on directory C:\njs\maxcpp is enabled.

Unfortunately, this C++ extension corrupts the path and its debug log output surfaces this as:

Includes:
        C:\NJS\DP.KINECT3\BUILD
        C:\NJS\MAX-SDK\SOURCE\C74SUPPORT\MAX-INCLUDES
        C:\NJS\MAX-SDK\SOURCE\C74SUPPORT\JIT-INCLUDES
        C:\NJS\MAX-SDK\SOURCE\C74SUPPORT\MSP-INCLUDES
        C:\NJS\MAXCPP\MAXCPP
        C:\PROGRAM FILES\AZURE KINECT SDK V1.4.0\SDK\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\INCLUDE
        C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO\2019\COMMUNITY\VC\TOOLS\MSVC\14.25.28610\ATLMFC\INCLUDE
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\UM
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\UCRT
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\SHARED
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\WINRT
        C:\PROGRAM FILES (X86)\WINDOWS KITS\10\INCLUDE\10.0.17763.0\CPPWINRT

The 5th include path has been corrupted and is incorrect. Various NTFS directories on this computer's SSD are case sensitive and need to be case sensitive as the dependent projects are cross-platform where case-sensitivity is needed. Projects are compiled and linked in multiple simultaneous platforms and file systems. It is not this or that. It is both at the same time. Last century when Windows didn't live in cross-platform scenarios it was possible to blindly alter case. This is no longer possible and leads to havok as this issue documents.

File system case-sensitivity is orthogonal to "running on windows, WSL, etc. The following is errant logic:

We support case sensitivity if "WSL" mode is enabled, i.e. if you install WSL and reference a WSL path, such as "/usr/bin/gcc" in the compilerPath...or via opening your workspace with the remote WSL extension (which will run our Linux binaries on Windows in WSL).

Paths, configuration values, etc. should not be corrupted by changing their byte (aka ASCII) values. It is probably impossible for an app like this C++ extension to construct some logic to derive if it should alter the individual byte characters in a configuration or path. This was further cemented in 2018 when NTFS and WSL again updated shared filesystem features and ended the old ways of Win32-only-case-doesn't-matter.

Workarounds like fsutil.exe file SetCaseSensitiveInfo maxcpp disable are the equivalent of playing a game of Wack-a-mole 🔨 due to non-inheritance of that attribute + the side-affect of all effected folders afterwards having different behaviors in other environments like WSL, git itself, etc.

I can't easily imagine the value of blindly uppercasing paths. Why? Because if you are assuming case doesn't matter...then upper-casing doesn't matter because the case doesn't matter. Perhaps you want to uppercase them for some internal intelllisense database de-duping. Fine. Then restrict the uppercasing to your internal database and not to the broader usage of paths/configuration values. And if this extension really really won't change this "I'm Win32 so I must uppercase", then do the additional API call to query the directory to see if it is case-sensitive and for those directories do not uppercase corrupt the path.

adpa

comment created time in 3 months

push eventdiablodale/maxcpp

ISHII 2bit

commit sha eed1d73b59c2c4e9329b12b4e5d6479578976408

implement REGISTER_METHOD_LOADBANG

view details

Graham Wakefield

commit sha 373387f88af4e62bfe52d413729d3884eaf768ac

Merge pull request #16 from 2bbb/PR/implement_loadbang implement REGISTER_METHOD_LOADBANG

view details

Dale Phurrough

commit sha c656f8f6568c75cf52330de90485dc6b89c804e4

typesafety w/ const; support defer, schedule - add support for Method_Task to be used with defer_*, schedule_*, etc. - first pass for more typesafety and implicit compiler hints by using const

view details

Dale Phurrough

commit sha 3df93fd1efd9c043ddf2ae6caac7f6e8e6f1f5cc

enabling set accessors in base classes

view details

Dale Phurrough

commit sha 058b6bff623a0e4c7d9b37bee19cba087995f15e

more changes of gensym() to USESYM() - enables use of commonsyms

view details

Dale Phurrough

commit sha 07c0d6c123447061f521773ea88ceea17eb1c839

non-signal in/outlets for MSP; more const - added non-signal in/outlets for MSP objects - removed unused maxcpp_perform64() - aligned _destroy for all 3 max classes - const for more params and vars - inc/dec to prefix from suffix

view details

Dale Phurrough

commit sha 856b3f25e51877db1bf9470963a602e241f0fc5d

add REGISTER_METHOD_DSPSTATE - add support for the notify callback when the MSP DSP engine turns on or off

view details

Dale Phurrough

commit sha 1026f9937f9eea89162115f8470cc0058c3de7ea

ignore local .vs directories

view details

push time in 3 months

push eventdiablodale/maxcpp

ISHII 2bit

commit sha eed1d73b59c2c4e9329b12b4e5d6479578976408

implement REGISTER_METHOD_LOADBANG

view details

Graham Wakefield

commit sha 373387f88af4e62bfe52d413729d3884eaf768ac

Merge pull request #16 from 2bbb/PR/implement_loadbang implement REGISTER_METHOD_LOADBANG

view details

push time in 3 months

issue openedCycling74/min-api

constructors called twice and have different behaviors/argument values

Min external constructors have different behaviors and called twice. I would never want my constructor called twice and I want consistent behavior across scenarios.

Setup

  • Min-api 55c65a0
  • Max 7 x64
  • MSVC++ 2019

Code

#pragma warning(push)
    #pragma warning(disable: 4100 4701 4706 4127 4244 4456 4267)
    #include <c74_min.h>
#pragma warning(pop)
#pragma warning(disable: 4100) // hack for c74_min MIN_FUNCTION

using namespace c74::min;

class foobar : public object<foobar> { //public matrix_operator<>
public:
    inlet<>  input	{ this, "input" };
    outlet<> output	{ this, "output" };

    // constructor for specific instance of this max object
    foobar(const atoms& args = {}) {
        cout << "constructor... " << args.size() << " arguments are: ";
        for (auto&& it : from_atoms<std::vector<string>>(args)) {
            cout << it;
        }
        cout << endl;
    }
    message<> setup { this, "setup",
        MIN_FUNCTION {
            cout << "setup()" << endl;
            return {};
        }
    };
    message<> maxclass_setup { this, "maxclass_setup",
        MIN_FUNCTION {
            cout << "maxclass_setup()" << endl;
            return {};
        }
    };
    message<> jitclass_setup { this, "jitclass_setup",
        MIN_FUNCTION {
            cout << "jitclass_setup()" << endl;
            return {};
        }
    };

};
MIN_EXTERNAL(foobar);

Repo 1

  1. Compile
  2. Create patch with single object with single argument -> (foobar myarg)
  3. Run that patch

Result 1

Max console reports the following

constructor... 0 arguments are: 
maxclass_setup()
foobar: constructor... 1 arguments are: myarg

Expected 1

A constructor to only be called once. Since the constructor is in the scope of the "top" max class, then this constructor would have no arguments. Please note, that checking the size() of arguments can not self-distinguish if it is the max class or the instance of that class, because arguments are not required and therefore it is valid to have zero arguments which would make both times the constructor is called appears extremely similar unless some state outside the constructor is used. But that's weird because now we are implementing a language feature (constructor only called once) with a state variable.

Repo 2

  1. Change line 9 class foobar... to be instead the following
    class foobar : public object<foobar>, public matrix_operator<> {
  2. Add a noop calc_cell method to the class
    template<class matrix_type, size_t plane_count>
    cell<matrix_type, plane_count> calc_cell(cell<matrix_type, plane_count> input, const matrix_info& info, matrix_coord& position) {
        cell<matrix_type, plane_count> result = {};
        return result;
    }
    
  3. Compile
  4. Run the same patch above

Result 2

constructor... 0 arguments are: jitclass_setup() maxclass_setup() foobar: constructor... 0 arguments are: foobar: setup()

Expected 2

In addition to the problem of the constructor running twice, now the second time it runs it no longer receives the "myarg" argument. This is drastically different behavior. The full list of non attribute arguments (non @... arguments) should be available to the constructor.

Notes

The number of times a constructor is called, in what context that constructor is called, and the arguments available to that constructor are all involved in this issue. Without guidance and examples from Cycling74, it is unclear the goal and context of constructors are in Min. Until that is clearer, I don't have any suggestions or fixes.

created time in 3 months

issue openedCycling74/min-api

multiple potentially uninitialized local variable 'tmp' used in matrix operations

In matrix processing, multiple locations of potentially uninitialized local variable 'tmp' used.

https://github.com/Cycling74/min-api/blob/63bd9859c8434632f796ee6a521b824458d1dda7/include/c74_min_operator_matrix.h#L299

and lines 383 and 408. Fixes can be to refactor code to be cleaner logic, set pragma's before these troublesome lines, etc.

Min appears to still be in flux, so correcting warnings are useful to continue a move towards stable clean code.

created time in 3 months

pull request commentdiablodale/pinentry-wsl-ps1

allow options to be passed to the script

I do not think env will work either. Same problem as above, the gpg agent tries to run a program named env NOTIFY=""... with spaces in it which would naturally fail.

https://github.com/gpg/gnupg/blob/fd79cadf7ba5ce45dfb5e266975f58bf5c7ce145/agent/call-pinentry.c#L352

From what I can understand (unless you see otherwise in your testing), it is not possible to set environment variables on the "same line" as this pinentry program in the real-world. This is due to the gpg agent interface between that agent and a pinentry program. It might be possible to set NOTIFY in a global scope in which gpg-agent is launched and hope it is inherited by the pinentry program. Though a global env var named NOTIFY is somewhat concerning.

Testing is needed for your proposed code change. Trying your idea in a real-world WSL, Windows, GPG setup to see if it is successful.

I like your idea. But I predict problems that testing can surface or prove me wrong 😅

To move forward, you'll need to do the testing I've written about above to explore what works and not. Maybe its your envvar technique, maybe its PINENTRY_USER_DATA, or maybe something else. When you find a method that does work, then I'm happy to consider it 🙂

Konfekt

comment created time in 3 months

pull request commentdiablodale/pinentry-wsl-ps1

allow options to be passed to the script

Nice idea. Thanks for the contribution. For the implementation, perhaps using ${-} instead of ${:-}. The behavior changes when the incoming value is "" or null.

with ${-}

NOTIFY="" pinentry-wsl-ps1.sh
inside script NOTIFY=""

with ${:-}

NOTIFY="" pinentry-wsl-ps1.sh
inside script NOTIFY=1

And have you tested step 2 of setup using the VAR=VALUE pinentry-wsl-ps1.sh approach? A quick read of the gpg code makes me suspect this will fail. The pinentry-program expects a program path, not a script command. What did you see when testing?

An alternative might be to use the env var PINENTRY_USER_DATA described https://gnupg.org/documentation/manuals/gnupg.pdf and code https://github.com/gpg/gnupg/blob/fd79cadf7ba5ce45dfb5e266975f58bf5c7ce145/agent/call-pinentry.c#L425 The PINENTRY_USER_DATA isn't automatically parsed by gpg code, so pinentry-wsl-ps1.sh would need to manually parse it when it is received via the Assaun option OPTION pinentry-user-data for any settings contained within. For example https://kevinlocke.name/bits/2019/07/31/prefer-terminal-for-gpg-pinentry/

Konfekt

comment created time in 3 months

more