Handle layers in PnP registry locations

Previously, we added a change that allows ICDs to be specified through the PnP system. This PR extends that to also allow layers to be specified through the same means. This is needed so that ICDs can continue to install layers in future versions of Windows, where they will not be able to access the old paths. The old paths are retained, and are expected to be used by anything that's not a driver.
This change also extends the PnP registries to allow a REG_MULTI_SZ, in the case that multiple layers or ICDs need to be specified from a single device.

I did a careful review of the code before you force-pushed a change that rewrote history of your three commits. Did the force push modify the source code files, or only the markdown file?

About the grammatical voice used in the markdown file (I don't know the english grammar vocabulary to describe this), I'm commenting on it here because it's hard to see the old "show outdated" comment after a subsequent commit.
There are many 10's of places in the spec file that use a voice such as "the loader will do XYZ" instead of "the loader does XYZ".  I see now that modifying that one creates inconsistency in the voice used by the document. Although I'd be happy to see this changed throughout the document, that belongs in a separate MR, and therefore I don't really care which voice is used by the text modified in this MR.

I'm building the loader now (after updating to the latest commits) so that I can test with a driver package I'm modifying to rely on the loader key being located in the device key instead of in HKLM/Software. I probably won't have a test result until tomorrow.

The change seems to work as intended.
I conducted an experiment of two trials configured as follows:

I modified my driver package to put both ICD and implicit layer regkey values in the KHR device key, and to remove the old regkey values from HKLM/Software/Khronos/Vulkan.
Both regkey values are modified to be created as REG_MULTI_SZ instead of as REG_SZ.
I enabled loader logging by setting the environment variable "VK_LOADER_DEBUG" to "all".
For this experiment I have a pair of GPUs. That causes the same .json file to be found twice, and it exercises the code that prunes duplicate json files.
Steam is installed, and the existence of the steam overlay demonstrates coexistence of new-style and old-style layer regekey values.

For the first trial I used an unmodified vulkan-1.dll.
As expected, the loader failed to find an ICD like this:
INFO: loaderGetRegistryFiles: opening device ROOT\DISPLAY\0000
INFO: loaderGetDeviceRegistryEntry: DeviceID(1) Failed to obtain VulkanDriverName size
INFO: loaderGetRegistryFiles: unable to open child-device error:13
INFO: loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1B30&SUBSYS_11A010DE&REV_A1\4&35d4f288&0&0008
ERROR: loaderGetDeviceRegistryEntry: Invalid VulkanDriverName data type. Expected REG_SZ.
INFO: loaderGetRegistryFiles: Opening child device 3 - DISPLAY\NVDFFFE\5&1E129203&4&UID4359
DEBUG: loaderGetRegistryFiles: GUID for 3 is not SoftwareComponent skipping
INFO: loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1B30&SUBSYS_11A010DE&REV_A1\4&ae59f48&0&0009
ERROR: loaderGetDeviceRegistryEntry: Invalid VulkanDriverName data type. Expected REG_SZ.
INFO: loaderGetRegistryFiles: unable to open child-device error:13
ERROR: loader_get_manifest_files: Registry lookup failed to get ICD manifest files.  Possibly missing Vulkan driver?
WARNING: loader_get_manifest_files: Registry lookup failed to get layer manifest files.
INFO: Located json file "C:\Program Files (x86)\Steam\SteamOverlayVulkanLayer64.json" from registry "HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\ImplicitLayers"
DEBUG: Searching the following paths for manifest files: C:\Program Files (x86)\Steam\SteamOverlayVulkanLayer64.json

INFO: Found manifest file C:\Program Files (x86)\Steam\SteamOverlayVulkanLayer64.json, version "1.0.0"
DEBUG: Adding VK_LAYER_LUNARG_standard_validation using the loader legacy path.  This is not an error.
INFO: Meta-layer VK_LAYER_LUNARG_standard_validation all 0 component layers appear to be valid.
INFO: loaderGetRegistryFiles: opening device ROOT\DISPLAY\0000
INFO: loaderGetDeviceRegistryEntry: DeviceID(1) Failed to obtain VulkanDriverName size
INFO: loaderGetRegistryFiles: unable to open child-device error:13
INFO: loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1B30&SUBSYS_11A010DE&REV_A1\4&35d4f288&0&0008
ERROR: loaderGetDeviceRegistryEntry: Invalid VulkanDriverName data type. Expected REG_SZ.
INFO: loaderGetRegistryFiles: Opening child device 3 - DISPLAY\NVDFFFE\5&1E129203&4&UID4359
DEBUG: loaderGetRegistryFiles: GUID for 3 is not SoftwareComponent skipping
INFO: loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1B30&SUBSYS_11A010DE&REV_A1\4&ae59f48&0&0009
ERROR: loaderGetDeviceRegistryEntry: Invalid VulkanDriverName data type. Expected REG_SZ.
INFO: loaderGetRegistryFiles: unable to open child-device error:13
ERROR: loader_get_manifest_files: Registry lookup failed to get ICD manifest files.  Possibly missing Vulkan driver?
ModLoad: 00000000`6c950000 00000000`6eb38000   C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nvoglv64.dll

For the second trial I replaced vulkan-1.dll with one I built that includes your change from the pull request. Everything else was left unchanged from first trial.
This time the loader succeeded in finding both the ICD and the optimus layer in driverstore, both using REG_MULTI_SZ. Pruning of the duplicate .json file seems to work correctly.
INFO: loaderGetRegistryFiles: opening device ROOT\DISPLAY\0000
INFO: loaderGetDeviceRegistryEntry: Device ID(1) Does not contain a value for "VulkanDriverName"
INFO: loaderGetRegistryFiles: unable to open child-device error:13
INFO: loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1B30&SUBSYS_11A010DE&REV_A1\4&35d4f288&0&0008
INFO: Located json file "C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json" from PnP registry: VulkanDriverName
INFO: loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1B30&SUBSYS_11A010DE&REV_A1\4&ae59f48&0&0009
INFO: Located json file "C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json" from PnP registry: VulkanDriverName
DEBUG: Searching the following paths for manifest files: C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json;C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json

WARNING: Skipping manifest file C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json - The file has already been read once
INFO: Found ICD manifest file C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json, version "1.0.0"
DEBUG: Searching for ICD drivers named .\nvoglv64.dll, using default dir
ModLoad: 00000000`6c950000 00000000`6eb38000   C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nvoglv64.dll

[...]

INFO: loaderGetRegistryFiles: opening device ROOT\DISPLAY\0000
INFO: loaderGetDeviceRegistryEntry: Device ID(1) Does not contain a value for "VulkanImplicitLayers"
INFO: loaderGetRegistryFiles: unable to open child-device error:13
INFO: loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1B30&SUBSYS_11A010DE&REV_A1\4&35d4f288&0&0008
INFO: Located json file "C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json" from PnP registry: VulkanImplicitLayers
INFO: loaderGetRegistryFiles: opening device PCI\VEN_10DE&DEV_1B30&SUBSYS_11A010DE&REV_A1\4&ae59f48&0&0009
INFO: Located json file "C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json" from PnP registry: VulkanImplicitLayers
INFO: Located json file "C:\Program Files (x86)\Steam\SteamOverlayVulkanLayer64.json" from registry "HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\Vulkan\ImplicitLayers"
DEBUG: Searching the following paths for manifest files: C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json;C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json;C:\Program Files (x86)\Steam\SteamOverlayVulkanLayer64.json

WARNING: Skipping manifest file C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json - The file has already been read once
INFO: Found manifest file C:\WINDOWS\System32\DriverStore\FileRepository\nv_disp.inf_amd64_01391cb8d6f2c2f2\nv-vk64.json, version "1.0.0"
INFO: Found manifest file C:\Program Files (x86)\Steam\SteamOverlayVulkanLayer64.json, version "1.0.0"


Add 2D Shape features

Add a new featureclass implementing shape features describing a 2D shape.
This class can only be extracted if force2D = True and the size of the bounding box is 1 in the dimension specified by force2Ddimension (i.e. it must be a truly 2D segmentation)
This featureclass is therefore not enabled by default.
cc @Radiomics/developers

the size of the bounding box is 1 in the dimension specified by force2Ddimension (i.e. it must be a truly 2D segmentation)

I would say the input is "truly 2D" if the ITK image passed as input is a 2D image, or perhaps if the spacing in z dimension is 0. Otherwise the definition can be ambiguous.

I don't think a spacing of zero is a good idea.  I would think we can come up with a reasonable definition of grid samples that gracefully handles any combination of dimensions and spacings in any dimension without becoming degenerate.

Definitely - I think it is better if the tool allowed processing of true 2d images. I suggested 0 z spacing in case we want to maintain the current convention that the input is always a 3d ITK image.

I would say the input is "truly 2D" if the ITK image passed as input is a 2D image, or perhaps if the spacing in z dimension is 0. Otherwise the definition can be ambiguous.

Very true, and would nicely help those users that use 2D input formats (e.g. PNG; though it does not address the multiple channels issue). On the other hand, it is likely that there are also users who have 3D input image data, but only single-slice segmentations. Those are also really 2D shapes (even though the real-world shape is 3D), but there it is more likely that dimensionality of the input data is 3D.
By the way, the latter also holds true for 2D DICOM (e.g. x-ray, mammography). ITK will read this in as 3D data, with size 1 in a certain dimension.

I would say the input is "truly 2D" if the ITK image passed as input is a 2D image, or perhaps if the spacing in z dimension is 0. Otherwise the definition can be ambiguous.

Very true, and would nicely help those users that use 2D input formats (e.g. PNG; though it does not address the multiple channels issue). On the other hand, it is likely that there are also users who have 3D input image data, but only single-slice segmentations. Those are also really 2D shapes (even though the real-world shape is 3D), but there it is more likely that dimensionality of the input data is 3D.
By the way, the latter also holds true for 2D DICOM (e.g. x-ray, mammography). ITK will read this in as 3D data, with size 1 in a certain dimension.

I would say the input is "truly 2D" if the ITK image passed as input is a 2D image, or perhaps if the spacing in z dimension is 0. Otherwise the definition can be ambiguous.

Very true, and would nicely help those users that use 2D input formats (e.g. PNG; though it does not address the multiple channels issue). On the other hand, it is likely that there are also users who have 3D input image data, but only single-slice segmentations. Those are also really 2D shapes (even though the real-world shape is 3D), but there it is more likely that dimensionality of the input data is 3D.
By the way, the latter also holds true for 2D DICOM (e.g. x-ray, mammography). ITK will read this in as 3D data, with size 1 in a certain dimension.

I would say the input is "truly 2D" if the ITK image passed as input is a 2D image, or perhaps if the spacing in z dimension is 0. Otherwise the definition can be ambiguous.

Very true, and would nicely help those users that use 2D input formats (e.g. PNG; though it does not address the multiple channels issue). On the other hand, it is likely that there are also users who have 3D input image data, but only single-slice segmentations. Those are also really 2D shapes (even though the real-world shape is 3D), but there it is more likely that dimensionality of the input data is 3D.
By the way, the latter also holds true for 2D DICOM (e.g. x-ray, mammography). ITK will read this in as 3D data, with size 1 in a certain dimension.

I would say the input is "truly 2D" if the ITK image passed as input is a 2D image, or perhaps if the spacing in z dimension is 0. Otherwise the definition can be ambiguous.

Very true, and would nicely help those users that use 2D input formats (e.g. PNG; though it does not address the multiple channels issue). On the other hand, it is likely that there are also users who have 3D input image data, but only single-slice segmentations. Those are also really 2D shapes (even though the real-world shape is 3D), but there it is more likely that dimensionality of the input data is 3D.
By the way, the latter also holds true for 2D DICOM (e.g. x-ray, mammography). ITK will read this in as 3D data, with size 1 in a certain dimension.

I would say the input is "truly 2D" if the ITK image passed as input is a 2D image, or perhaps if the spacing in z dimension is 0. Otherwise the definition can be ambiguous.

Very true, and would nicely help those users that use 2D input formats (e.g. PNG; though it does not address the multiple channels issue). On the other hand, it is likely that there are also users who have 3D input image data, but only single-slice segmentations. Those are also really 2D shapes (even though the real-world shape is 3D), but there it is more likely that dimensionality of the input data is 3D.
By the way, the latter also holds true for 2D DICOM (e.g. x-ray, mammography). ITK will read this in as 3D data, with size 1 in a certain dimension.

I would say the input is "truly 2D" if the ITK image passed as input is a 2D image, or perhaps if the spacing in z dimension is 0. Otherwise the definition can be ambiguous.

Very true, and would nicely help those users that use 2D input formats (e.g. PNG; though it does not address the multiple channels issue). On the other hand, it is likely that there are also users who have 3D input image data, but only single-slice segmentations. Those are also really 2D shapes (even though the real-world shape is 3D), but there it is more likely that dimensionality of the input data is 3D.
By the way, the latter also holds true for 2D DICOM (e.g. x-ray, mammography). ITK will read this in as 3D data, with size 1 in a certain dimension.


Fix for lifecycle postStart and preStop tests

This required to modify the Dockerfile of cnf-app-mac-operator to be able to launch commands through a shell

SUCCESS https://www.distributed-ci.io/jobs/37815ba2-52a1-4813-ac7a-42b9f0f15676/jobStates
from [WIP] Fix for lifecycle postStart and preStop tests #34

In this change, you can see the lifecycle-container-startup/shutdown tests are now passing, and the rest of tests remain in the same status, so this is ready for review.

Let's wait for confirmation from tnf regarding the issue we have with cnf-app-mac-operator, just to know if it's a hard requirement to have a shell for running commands.

I've decided not to change cnf-app-mac-operator in this PR, I'll address it in a separate change. The changes for the other operators are correct and this can be merged. @capolrik @tkrishtop could anyone of you please take a look to the change to have it merged?

This change will be used to integrate the fix for cnf-app-mac-operator: https://github.com/openshift-kni/example-cnf/pull/35.
In the meanwhile, this PR can be merged safely.


Remove g2p?

Since we have moved to a weighted edit distance, we don't need compare forms anymore and so we can remove g2p as a dependency.

The only reason not to remove g2p would be if we wanted to also keep support for the compare-form based unweighted search. I'm not yet sure if we want to do that.

just adding more info to this thread. As it stands, g2p needs to be installed in order to run unit tests locally (I had to manually pip install it into my poetry env).

Yes in fact it seems that it is necessary just to run the CLI, e.g.:
$ poetry run mothertongues
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/home/dhd/work/p2wilrc/mothertongues-mothertongues/mothertongues/cli.py", line 14, in <module>
    from mothertongues.config import SchemaTypes, get_schemas
  File "/home/dhd/work/p2wilrc/mothertongues-mothertongues/mothertongues/config/__init__.py", line 3, in <module>
    from mothertongues.config.models import (
  File "/home/dhd/work/p2wilrc/mothertongues-mothertongues/mothertongues/config/models.py", line 26, in <module>
    from mothertongues.utils import string_to_callable
  File "/home/dhd/work/p2wilrc/mothertongues-mothertongues/mothertongues/utils.py", line 9, in <module>
    from g2p import Mapping, Transducer
ModuleNotFoundError: No module named 'g2p'

As a side note, I tried adding it to my environment with poetry add g2p (is this the right command??) and this took a surprisingly long time.  Really, I do not like poetry at all.

I used a regular pip install in my poetry env
poetry run pip install g2p
hth!


Make StructuredTransformer public

As discussed here #801

While making StructuredTransformer public is sufficient short term, its user experience for creating the transforms is still pretty bad right?
What about the proposal from the issue?
            var transformBuilder = app.ApplicationServices.GetRequiredService<ITransformBuilder>();
            var transforms = transformBuilder.Create(transformBuilderContext =>
            {
                transformBuilderContext.AddXForwarded();
            });

We already have all those types and extensions, only the Create method would be new. I bring it up here because this proposal wouldn't use a public StructuredTransformer and I'd like to avoid a stopgap if possible.

What would Create return?

The base type HttpTransformer.

There is now a related PR #913 introducing the Create method discussed above.

Replaced by #913. @leastprivilege give that a try and let us know what you think.

Cool thanks!
Is there an ETA for the next preview?

Nothing specific, though we are about due for our monthly preview. You can try the daily builds in the meantime:
https://github.com/microsoft/reverse-proxy/blob/main/docs/DailyBuilds.md


Panel closes when view in recycler view (inside a panel) is clicked.

Hi
I am using your library (Which btw is awesome)
I am having a plus and minus button in my recycler view(which is inside a sliding panel)
Whenever i click any of these two button a view is update in that row and i have to call notifyDataSetChanged() , but the problem is that sliding panel closes when i perform this action.
But if i click that row it stays open.
I want to fix this problem that whenever i click plus/minus panel stays open.
I have also tried setting dragView in xml as well as in activity but no change in the behaviour.
Can anyone help me?

i have the same isssue, any solution?


docs: Add NodeJS SDK docs

This commit adds documentation for the NodeJS SDK.
Closes #3640
Signed-off-by: Vikram Vaswani<EMAIL_ADDRESS>

Marked as draft since these are stubs atm.

Closing this PR as it was incorrectly rebased


[PREVIEW] Use String instead of empty object

Passing an empty object results in an empty response from CCD now

Tech task so I will merge. No need for QA to test


using type in Markers Info Parts

Hello,
I'm using your maps abstraction and its a lot of fun.
Thank you very much for publishing it.
I would like to know how I can use an odata type like this:
var oMarkers = new openui5.googlemaps.Marker({
    lat : "{latitude}",
    lng : "{longitude}",
    info : {
        parts : [ {
                path : 'name'
        }, {
                path : 'timeFrom',
                type : new sap.ui.model.odata.type.Time()
        }, {
                path : 'timeTo',
                type : new sap.ui.model.odata.type.Time()
        } ]
    },
    click : oController.onMarkerClick
});

this example don't work with your markes :-(
PS: I've already found examples like "formatter:'util.Formatter.info'", but I would prefer the standard way if it is possible.
Is it possible in with your maps abstraction?
kind regards,
Alex

You question doesnt really relate to an issue with the library, the question relates to expression binding in xml views,
please ask on Stackoverflow and see if anyone can help there
JSP


Potential idea for handling user credits in plan

After having many long-winded conversations about how to handle user credits in both the "Credits" and "Plans" page, I have a proposed solution.
Changes

Change "Credits" page to "Course History"
Give users the option to add credits when creating their plan. Templates will never load user credits
Add a UI indicator for semesters where it's not "synced" with the courses from a user's course history

Below are gifs of the proposed changes
Creating a new plan

Creating a template

Let me know what you guys think! I hopping this solution straddles the line between preventing users from making bad decisions while providing them with freedom and flexibility.

Liking the look of this so far, I think this is a good compromise based on the discussions we've had :)
Concerns:
* When moving a completed course from its original semester to another semester it loses its golden color - is this intended? I think it should keep its color when moved so that it's still clear that the course was populated from course history.

That's a good point. Gold is supposed to denote transfer credit and I'll keep the indicator even if you change the semester.

* I noticed an error when I click on the Create Plan button in the custom plan creation modal, although the plan does get created successfully.

 Fixed now :)

Some other thoughts that I'd like to discuss at some point (non-blocking, could be addressed in another PR later down the road):
* Is there some way to add a legend for what the gold color means somewhere, just so it's clearer to the user that it's a transfer credit? We could try making the "Show Transfer Credits" toggle the same color as the courses.

Yeah good point it's not super clear. That's a good idea to make it the same color. Kevin suggested using tags instead so I might give that a go and see how it looks. I can also add a tooltip to mention that it's a transfer credit.

* On the note of the colors, the blue on gold combo for completed courses is a bit hard to read imo, might be worth changing if we can...

Ye sure I just did a random color xD

* It'd also be nice if there was a way to see what courses are misplaced when the "Courses not synced with course history" icon gets displayed. Not sure how we'd go about that yet, would be happy to hear anyone's thoughts on these points :)

I might just have a tooltip that specifies it on the Semester level which courses are misplaced. See how that looks but I'm down to change it if we have other ideas.

Changes Made

Added "tags" C & T which signify Complete and Transfer Credit respectively. This replaces the golden background.
Replaced sync indicator on Semester card with an error count along with descriptions of error type.
Added specific course error messages to courses.

How Logic Works

Check for whether course has been completed/is a transfer. If so, we give it the appropriate tag
We show an error on the semester and course level for the following cases:

semester with course history contains an extra course or is missing a course
a completed course is placed in another semester

We're currently assuming that if there is a course for a semester in Course History, that semester should only contain courses from course history, otherwise there is an error message that appears. Where this gets interesting is for new students coming into UTD with transfer credit (which will be listed in their first semester of their plan).
Should we operate under the assumption that courses the user is currently taking should be listed in course history? If not, this logic may need to be reworked. Hope that made sense 😓
Also here's a gif of updated functionality (cause git checkout too much work sometimes)


Unstar all messages in topic.

The previous attempt at this #16898 was buggy and hence was reverted in #17429.
This PR is another attempt which addresses the bugs noticed there.
This also adds node tests for static/starred_messages.js.
https://user-images.githubusercontent.com/55339528/110300208-a0ca8a80-801c-11eb-98f5-5b972565a4c6.mp4

Resolved conflicts in the last push.

@timabbott Thanks for the review! I updated the PR with the following changes-

Added 3 new commits

673e22b23e2bf38d2f38cba4e60a24df9a04d690 addresses a small bug/discrepancy I noticed while working on this. This is at the beginning of the PR.

b37d3f785ebc686f2d0d58f9132b83af7463834e adds the helper as you suggested in the comment above.

and fills out plausible values for all the other fields

I left this part out, the reasoning being that it would restrict the use of this helper, and I think it would be better for test readability to not add more fields in the helper. I've written more about this in the commit message, but please correct me if I'm wrong! In this commit I also changed some existing instances of get() mocks to use this new helper method. One more thing -- I added this helper in static/message_store.js itself, should it be somewhere else, or this is a fine place for it? (I added a comment in there saying that its for use in tests only, though)

3fefa525c2337c21e8b22a2f8bf95b180daf3d9c refactors the current unstar-all modal code so that click-handlers for the modal are registered in the same function which opens it.

Changes in old commits are

(Re) renamed send_flag_update to send_flag_update_for_msgs in d67ab725063cb8da904a2bcc7f43e5450ecbe8df
New code for unstar-all-in-topic in b219313ac39bbc7f1620226f6bbcf3184ac0a607 now uses the style described above (use on_confirm function instead of storing the data in DOM). I agree that it is cleaner this way, so that stream_popovers.js contains click-handlers only directly involved with the left sidebar, and this also avoids some code-duplication 🙂

@timabbott Thanks for the review! This is ready for another look. Here are the changes since the last review-

Added 3 new commits

8c18676508de04fcf6138c52fc2e93b61180498f addresses a small bug/discrepancy I noticed while working on this. This is at the beginning of the PR.

c0faed6ba9248255851aedb51a819feb3e872d33 adds the helper as you suggested in the comment above.

and fills out plausible values for all the other fields

I left this part out, the reasoning being that it would restrict the use of this helper, and I think it would be better for test readability to not add more fields in the helper. I've written more about this in the commit message, but please correct me if I'm wrong! In this commit I also changed some existing instances of get() mocks to use this new helper method. One more thing -- I added this helper in static/message_store.js itself, should it be somewhere else, or this is a fine place for it? (I added a comment in there saying that its for use in tests only, though)

e3844fbd340d9ef111edda22931baec86c3b4dc2 replaces the current unstar-all modal with the confirm_dialog Widget..

Changes in old commits are

(Re) renamed send_flag_update to send_flag_update_for_msgs in ee68a60e7ea4aed687539101f36ccc81cda60626
New code for unstar-all-in-topic in a8c84f58e6ac735d0a5dc37ea04ac28141e1c746 also uses the widget from static/confirm_dialog.js

I resolved conflicts in the last push. @timabbott this is ready for another review, please take a look!

@timabbott This is ready for another review! I wrote the changes inline, plus added one new commit at the beginning of the PR as a small bugfix.

I merged the first several commits as the series ending with 91234b2a86f026c575f7b5eb60d0df4507b2e4ee, and then commented on the last bit.  Thanks for all your work on this so far @abhijeetbodas2001!

@timabbott Thanks for the review! This is ready for another look. Apart from the inline comments, here are the changes since the last review.

Added a small bugfix at the beginning of this PR.

In the video in the PR description comment above, a lag can be seen after clicking on "Unstar messages". I thought earlier that it was my machine being slow, but that isn't the case. I've added a commit (the second one in this PR) which fixes this.
Here's a GIF after this change-

Put starred_messages.js back in test-js-with-node/EXEMPT_FILES -- it isn't a data only module anymore, and I couldn't figure out how to write tests for this. Is that fine, or should I try to write zjquery tests?

@timabbott Thanks for the review! This is ready for another look. Apart from the inline comments, here are the changes since the last review.

Added a small bugfix at the beginning of this PR.
In the video in the PR description comment above, a lag can be seen after clicking on "Unstar messages". I thought earlier that it was my machine being slow, but that isn't the case. I've added a commit (the second one in this PR) which fixes this.

Here's a GIF after this change

Put starred_messages.js back in test-js-with-node/EXEMPT_FILES -- it isn't a data only module anymore, and I couldn't figure out how to write tests for this, nor could I find any examples in the codebase which test other widgets. Is that fine, or should I try to write zjquery tests?

Merged, thanks @abhijeetbodas2001!  I think this is a reasonable checkpoint even though we'll want to do some follow-up work, which I'd appreciate your driving.

Can you open an issue for making the starred_messages.js logic fetch the set of messages to unstar from the server?  Most simply, this would basically entail doing a GET /messages query with is:starred, stream:, and topic: filters and throwing away the result aside from the returned message IDs.
For test coverage, I think the right model would be split out a starred_messages_ui.js module that contains the confirm dialog (etc.) -- similar to various commits @showell has been doing this week for other modules (for a different reason).  I think that's probably a reasonable path forward there -- feel free to just submit a PR without an issue since it's pretty small.

I opened #17790 and #17793 respectively for these.
I'm also working on the confirm dialog sweep and will try to open a PR for it soon.


broken link to sample page in readme

Is there an existing issue for this?

[X] I have searched the existing issues

Flutter Quill version
(latest on master branch)
Steps to reproduce
On github readme, there is the sentence: "Check out Sample Page for more advanced usage."
This goes to a 404 not found page.
Expected results
Should link properly.
Actual results
goes to 404 not found, instead of Samples page as intended
Code sample
(not code-related)
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Fixed


Prove that polynomials form a ring

Prove that the definition of polynomials via lists satisfies all the ring axioms. Some existing proofs were changed a bit, mostly to simplify them or make use of lemmas that were introduced in the course of proving other properties.

Thanks!


Fix suspected race condition in prompt handling

Description
Fixes https://github.com/zalando/go-keyring/issues/104
The current approach to handling prompts involves calling for a prompt and then registering a signal handler for a response that indicates the prompt had completed. In most cases, if the user were to take action, this would be quite slow. However, in the case of automatic responses to the prompt, the signal response may appear before the signal handler is configured, resulting in blocking forever.
This commit moves the call for a prompt after the signal handling has been configured, closing the race window.
Reviewer Notes
I'll admit that I'm not very familiar with all the nuances of dbus or this library so it's entirely possible I've missed something. We've had three reports over on https://github.com/cli/cli/issues/8802 that this has resolved the issue they were facing but I can't say for sure that there's not some unintended side effects.

@williammartin thanks for the PR, the description and the detailed issue, really great work!
Reviewing the timestamps of the message, I would say you are right to call it a race condition.

:+1:

:+1:

Thanks so much for the quick review and merge! Will you create a new release with this or should I pin to the sha in the meantime?

thanks for the PR, the description and the detailed issue, really great work!

OSS maintainers have to stick together 😉

I have created a new release! https://github.com/zalando/go-keyring/releases/tag/v0.2.4


During search operations fields set read only were throwing exception…

…s when the record was being created. This should be ignored during the initial creation of the objects.
Using a nested validate_value class and runtime patching active only during the execution of the search function. It simply removes the read only check during searches.

Thanks for the contribution, we've pulled this issue into our next release cycle, and will be fixing internally without the need for the provided patch workaround.


Currently selected theme bugs

In light theme, it is not visible that the currently selected theme is the light theme.

System theme button is not shown as currently selected theme when selected.

https://github.com/user-attachments/assets/6411a103-8a9e-4a20-b116-c6d8819ad653

Oh...you compiled the app from the latest commit.
Anyway the current selected theme could be rounded instead squared. @AbdurazaaqMohammed

System theme button is not shown as currently selected theme when selected.

Fixed, I update the last release instead because the changes are minor

In light theme, it is not visible that the currently selected theme is the light theme.
the current selected theme could be rounded instead squared

Well, this is how the MaterialButtonToggleGroup looks, I don't know why the selection in light mode is barely visible, at least it looks a little better for me


cudatext-qt: 1.169.2 -> 1.170.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for cudatext-qt is: "Cross-platform code editor"
meta.homepage for cudatext-qt is: "https://cudatext.github.io/"
meta.changelog for cudatext-qt is: "https://cudatext.github.io/history.txt"
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.170.0 with grep in /nix/store/1myfy33cj6ad06i7axdhsqvdm3vfc0hx-cudatext-1.170.0
found 1.170.0 in filename of file in /nix/store/1myfy33cj6ad06i7axdhsqvdm3vfc0hx-cudatext-1.170.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
cudatext
cudatext-gtk
cudatext-qt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1myfy33cj6ad06i7axdhsqvdm3vfc0hx-cudatext-1.170.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cudatext-qt https://github.com/r-ryantm/nixpkgs/archive/9a863a972ebfc1a7fddfd2e17879ecbfac06d873.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1myfy33cj6ad06i7axdhsqvdm3vfc0hx-cudatext-1.170.0
ls -la /nix/store/1myfy33cj6ad06i7axdhsqvdm3vfc0hx-cudatext-1.170.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

cudatext
cudatext-gtk

Maintainer pings
cc @sikmir for testing.

Duplicates #189229


Expose configuration file (archives.json) to be web accessible

Memento 1.0-RC8 exposes the list of archives aggregated on the /about and primary web endpoint.
## Upstream Archives

1. [Archive.today](https://archive.today/)
2. [Portuguese Web Archive](https://arquivo.pt/)
3. [Perma Archive](https://perma.cc/)
4. [Stanford Web Archive](https://swap.stanford.edu/)
5. [BAnQ](https://waext.banq.qc.ca/)
6. [Archive-It](https://wayback.archive-it.org/)
7. [Icelandic Web Archive](https://wayback.vefsafn.is/)
8. [Bibliotheca Alexandrina Web Archive](https://web.archive.bibalex.org/)
9. [Internet Archive](https://web.archive.org/)
10. [Australian Web Archive](https://web.archive.org.au/)
11. [Library and Archives Canada](https://webarchive.bac-lac.gc.ca/)
12. [Library of Congress](https://webarchive.loc.gov/)
13. [UK National Archives Web Archive](https://webarchive.nationalarchives.gov/)
14. [National Records of Scotland](https://webarchive.nrscotland.gov.uk/)
15. [UK Web Archive](https://webarchive.org.uk/)
16. [UK Parliament Web Archive](https://webarchive.parliament.uk/)

It might be useful to expose the archives' respective endpoints. If an archive is disabled or "sleeping", it might also be useful to expose this information. From what I recall, the "disabled" status is present in the JSON file but the "sleeping" attribute that occurs after some number of failures is runtime generated, so that might be trickier.
Regardless, it would be useful to expose the archives.json file that is being used in the current instance.

From what I recall, the "disabled" status is present in the JSON file but the "sleeping" attribute that occurs after some number of failures is runtime generated, so that might be trickier.

On the contrary, I think it will be trickier to report ignored (disabled explicitly in the input archive list file) archives because we filter them off immediately after parsing the file and do not keep any records of those ignored archives in the memory as they will not be contributing in the process for the entire uptime of the service. The runtime structure is easier to report, it simply requires marshaling the array into JSON.
I can think of adding more runtime attributes to the structure of each archive, such as:

Number of requests sent
Number of successful responses
Number of times an archive gone dormant
The last time when an archive (only if currently dormant?) was put to sleep

Obviously, these counters will only keep track of the state for the uptime of the instance. If we also report the uptime of the instance and total number of received requests under the /about endpoint, this will enable a nice time series visualization about the health of instance and upstream archives.

All of the extra information you suggested would be really useful, too.
What about also keeping a record of timestamps/ranges for which an archive was dormant? This seems like it might require a lot of bookkeeping.

we filter them off immediately after parsing the file and do not keep any records

Couldn't we keep a record of when we filter them off to be reported later?

What about also keeping a record of timestamps/ranges for which an archive was dormant? This seems like it might require a lot of bookkeeping.

That would be a serious memory leak as the amount of memory needed to run the service will continue to rise indefinitely for the lifetime of the instance. Keeping counters is cheap as the value is replaced in place. By knowing the number of dormant sessions of each archives and already knowing the configurable dormant period, one can simple multiply the two to get an overall duration for which an archive was not being aggregated from.

Couldn't we keep a record of when we filter them off to be reported later?

We could, but I do not see a compelling reason to do so. The purpose of the option to ignore selected archives before an instance is started is to allow the service maintainers to keep record of things that they used in the past, anticipate using in the future, or have some private entries for testing. There is not a lot to offer by exposing such private information. The ignore attribute of the archives list is a way to say, "hey aggregator, don't bother about these and assume as if they don't exist".


Include documentation on how to make UI extensions work in airgap mode

Fixes SURE-8077
Reminders

See the README for more details on how to work with the Rancher docs.

Verify if changes pertain to other versions of Rancher. If they do, finalize the edits on one version of the page, then apply the edits to the other versions.

If the pull request is dependent on an upcoming release, make sure to target the release branch instead of main.

Description

Largely based on content from https://github.com/rancher/ui-plugin-charts?tab=readme-ov-file#air-gapped-rancher
Also reorganizes the air-gapped related content. Do you think maybe we should put it all on a separate page? Disadvantage is that some of other instructions are still relevant for air-gapped, so air-gapped users might not realize that deletion, uninstall, etc. are listed on another page.
Comments

Need to sync versions

Need to sync versions

Woops, sorry jumped the gun.


move into conventional-changelog organization

@Xiphe would you have any interest in moving this changelogrc-spec into the conventional-changelog organization? I think it's a good starting point to discussion what configuration options we expose moving forward.

I don't work for Jimdo anymore and don't feel as a maintainer for this code. It's MIT though and since this is basically a stale repo I guess it would be totally fine if you copy this over given its of value for the org.

Summoning @TobiasBales 🧙♂


Handle SkColor creation from rgba tuple

Skia.Color accepts number[], but the native constructor doesn't actually account for it.
In JsiSkColor::createCtor, if argument[0].isObject() (true for both Array and Float32Array), it's returned as is as the color value.
When the jsi::Value is made into to an SkColor in JsiSkColor::FromValue, the .buffer property (which is of course is not there on an array -- thus undefined) is attempted to be accessed.
I've added support here.
Orthogonally, have you considered using [r: number, g: number, b: number, a: number] instead of number[] for extra type saftey?
Resolves #2113

Thanks a lot I'm excited to sanitize the situation there. I added some tests for it at https://github.com/louix/react-native-skia/pull/1 but it seems to fail on Android.
I will look into it.

You were correct about 0-1 vs 0-255!
I changed the JSI side slightly to mimic the web one (Array become Float32Array), and added the offscreen canvas test.
The native side was just returning undefined if it wasn't sure how to handle the value, so you'd get an error where you tried to use the SkColor instead of when you created it.
I added an throw at creation time (and an exhaustive one to the web side to match).

but either way the tests you've written will be very useful.


[bzip2] Build error on x64-windows

Package<EMAIL_ADDRESS>Host Environment

Host: x64-windows
Compiler: MSVC 19.39.33523.0
vcpkg-tool version: 2024-04-23-d6945642ee5c3076addd1a42c331bbf4cfc97457
vcpkg-scripts version: 66a252f70 2024-05-15 (2 hours ago)

To Reproduce
vcpkg install opencv[cuda,dnn-cuda]
Failure logs
-- Downloading https://sourceware.org/pub/bzip2/bzip2-1.0.8.tar.gz -> bzip2-1.0.8.tar.gz...
-- Extracting source C:/source/(3rd-party)/vcpkg/downloads/bzip2-1.0.8.tar.gz
-- Applying patch fix-import-export-macros.patch
-- Using source at C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: "C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
    Working Directory: C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      C:\source\(3rd-party)\vcpkg\buildtrees\bzip2\config-x64-windows-dbg-CMakeCache.txt.log
      C:\source\(3rd-party)\vcpkg\buildtrees\bzip2\config-x64-windows-rel-CMakeCache.txt.log
      C:\source\(3rd-party)\vcpkg\buildtrees\bzip2\config-x64-windows-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:261 (vcpkg_execute_required_process)
  ports/bzip2/portfile.cmake:20 (vcpkg_cmake_configure)
  scripts/ports.cmake:175 (include)

C:\source\(3rd-party)\vcpkg\buildtrees\bzip2\config-x64-windows-out.log
[1/2] "C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe" -E chdir ".." "C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe" "C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/source/(3rd-party)/vcpkg/packages/bzip2_x64-windows" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DBZIP2_SKIP_TOOLS=OFF" "-DBZ2_VERSION=1.0.8" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/source/(3rd-party)/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/source/(3rd-party)/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/source/(3rd-party)/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/source/(3rd-party)/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
FAILED: ../CMakeCache.txt
"C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe" -E chdir ".." "C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe" "C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/source/(3rd-party)/vcpkg/packages/bzip2_x64-windows" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DBZIP2_SKIP_TOOLS=OFF" "-DBZ2_VERSION=1.0.8" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/source/(3rd-party)/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/source/(3rd-party)/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/source/(3rd-party)/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/source/(3rd-party)/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF"
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- The C compiler identification is MSVC 19.39.33523.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe - broken
CMake Error at C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/share/cmake-3.29/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: 'C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-rel/CMakeFiles/CMakeScratch/TryCompile-32flwb'

    Run Build Command(s): "C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v cmTC_aafde
    [1/2] C:\PROGRA~1\MIB055~1\2022\PROFES~1\VC\Tools\MSVC\1439~1.335\bin\Hostx64\x64\cl.exe  /nologo   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP   /MDd /Zi /Ob0 /Od /RTC1 /showIncludes /FoCMakeFiles\cmTC_aafde.dir\testCCompiler.c.obj /FdCMakeFiles\cmTC_aafde.dir\ /FS -c C:\source\(3rd-party)\vcpkg\buildtrees\bzip2\x64-windows-rel\CMakeFiles\CMakeScratch\TryCompile-32flwb\testCCompiler.c
    [2/2] C:\WINDOWS\system32\cmd.exe /C "cd . && C:\source\(3rd-party)\vcpkg\downloads\tools\cmake-3.29.2-windows\cmake-3.29.2-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_aafde.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe --manifests  -- C:\PROGRA~1\MIB055~1\2022\PROFES~1\VC\Tools\MSVC\1439~1.335\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_aafde.dir\testCCompiler.c.obj  /out:cmTC_aafde.exe /implib:cmTC_aafde.lib /pdb:cmTC_aafde.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    FAILED: cmTC_aafde.exe
    C:\WINDOWS\system32\cmd.exe /C "cd . && C:\source\(3rd-party)\vcpkg\downloads\tools\cmake-3.29.2-windows\cmake-3.29.2-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_aafde.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe --manifests  -- C:\PROGRA~1\MIB055~1\2022\PROFES~1\VC\Tools\MSVC\1439~1.335\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_aafde.dir\testCCompiler.c.obj  /out:cmTC_aafde.exe /implib:cmTC_aafde.lib /pdb:cmTC_aafde.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    "C:\source\" no se reconoce como un comando interno o externo,

    programa o archivo por lotes ejecutable.

    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)

-- Configuring incomplete, errors occurred!
[2/2] "C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe" -E chdir "../../x64-windows-dbg" "C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe" "C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/source/(3rd-party)/vcpkg/packages/bzip2_x64-windows/debug" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DBZIP2_SKIP_TOOLS=OFF" "-DBZ2_VERSION=1.0.8" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/source/(3rd-party)/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/source/(3rd-party)/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/source/(3rd-party)/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/source/(3rd-party)/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DBZIP2_SKIP_HEADERS=ON" "-DBZIP2_SKIP_TOOLS=ON"
FAILED: ../../x64-windows-dbg/CMakeCache.txt
"C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe" -E chdir "../../x64-windows-dbg" "C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe" "C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/source/(3rd-party)/vcpkg/packages/bzip2_x64-windows/debug" "-DFETCHCONTENT_FULLY_DISCONNECTED=ON" "-DBZIP2_SKIP_TOOLS=OFF" "-DBZ2_VERSION=1.0.8" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/source/(3rd-party)/vcpkg/scripts/toolchains/windows.cmake" "-DVCPKG_TARGET_TRIPLET=x64-windows" "-DVCPKG_SET_CHARSET_FLAG=ON" "-DVCPKG_PLATFORM_TOOLSET=v143" "-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON" "-DCMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY=ON" "-DCMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP=TRUE" "-DCMAKE_VERBOSE_MAKEFILE=ON" "-DVCPKG_APPLOCAL_DEPS=OFF" "-DCMAKE_TOOLCHAIN_FILE=C:/source/(3rd-party)/vcpkg/scripts/buildsystems/vcpkg.cmake" "-DCMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION=ON" "-DVCPKG_CXX_FLAGS=" "-DVCPKG_CXX_FLAGS_RELEASE=" "-DVCPKG_CXX_FLAGS_DEBUG=" "-DVCPKG_C_FLAGS=" "-DVCPKG_C_FLAGS_RELEASE=" "-DVCPKG_C_FLAGS_DEBUG=" "-DVCPKG_CRT_LINKAGE=dynamic" "-DVCPKG_LINKER_FLAGS=" "-DVCPKG_LINKER_FLAGS_RELEASE=" "-DVCPKG_LINKER_FLAGS_DEBUG=" "-DVCPKG_TARGET_ARCHITECTURE=x64" "-DCMAKE_INSTALL_LIBDIR:STRING=lib" "-DCMAKE_INSTALL_BINDIR:STRING=bin" "-D_VCPKG_ROOT_DIR=C:/source/(3rd-party)/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/source/(3rd-party)/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DBZIP2_SKIP_HEADERS=ON" "-DBZIP2_SKIP_TOOLS=ON"
CMake Deprecation Warning at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 will be removed from a future version of
  CMake.

  Update the VERSION argument <min> value or use a ...<max> suffix to tell
  CMake that the project does not need compatibility with older versions.

-- The C compiler identification is MSVC 19.39.33523.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe - broken
CMake Error at C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/share/cmake-3.29/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

    "C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe"

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: 'C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-dbg/CMakeFiles/CMakeScratch/TryCompile-ns5bkx'

    Run Build Command(s): "C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v cmTC_e0b50
    [1/2] C:\PROGRA~1\MIB055~1\2022\PROFES~1\VC\Tools\MSVC\1439~1.335\bin\Hostx64\x64\cl.exe  /nologo   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP   /MDd /Zi /Ob0 /Od /RTC1 /showIncludes /FoCMakeFiles\cmTC_e0b50.dir\testCCompiler.c.obj /FdCMakeFiles\cmTC_e0b50.dir\ /FS -c C:\source\(3rd-party)\vcpkg\buildtrees\bzip2\x64-windows-dbg\CMakeFiles\CMakeScratch\TryCompile-ns5bkx\testCCompiler.c
    [2/2] C:\WINDOWS\system32\cmd.exe /C "cd . && C:\source\(3rd-party)\vcpkg\downloads\tools\cmake-3.29.2-windows\cmake-3.29.2-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_e0b50.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe --manifests  -- C:\PROGRA~1\MIB055~1\2022\PROFES~1\VC\Tools\MSVC\1439~1.335\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_e0b50.dir\testCCompiler.c.obj  /out:cmTC_e0b50.exe /implib:cmTC_e0b50.lib /pdb:cmTC_e0b50.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    FAILED: cmTC_e0b50.exe
    C:\WINDOWS\system32\cmd.exe /C "cd . && C:\source\(3rd-party)\vcpkg\downloads\tools\cmake-3.29.2-windows\cmake-3.29.2-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_e0b50.dir --rc=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\rc.exe --mt=C:\PROGRA~2\WI3CF2~1\10\bin\100226~1.0\x64\mt.exe --manifests  -- C:\PROGRA~1\MIB055~1\2022\PROFES~1\VC\Tools\MSVC\1439~1.335\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_e0b50.dir\testCCompiler.c.obj  /out:cmTC_e0b50.exe /implib:cmTC_e0b50.lib /pdb:cmTC_e0b50.pdb /version:0.0 /machine:x64  /debug /INCREMENTAL /subsystem:console  kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib && cd ."
    "C:\source\" no se reconoce como un comando interno o externo,

    programa o archivo por lotes ejecutable.

    ninja: build stopped: subcommand failed.

  CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
  CMakeLists.txt:2 (project)

-- Configuring incomplete, errors occurred!
ninja: build stopped: subcommand failed.

C:\source\(3rd-party)\vcpkg\buildtrees\bzip2\config-x64-windows-rel-CMakeCache.txt.log
# This is the CMakeCache file.
# For build in directory: c:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-rel
# It was generated by CMake: C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//No help, variable specified on the command line.
BUILD_SHARED_LIBS:UNINITIALIZED=ON

//No help, variable specified on the command line.
BZ2_VERSION:UNINITIALIZED=1.0.8

//No help, variable specified on the command line.
BZIP2_SKIP_TOOLS:UNINITIALIZED=OFF

//Path to a program.
CMAKE_AR:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/lib.exe

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=Release

CMAKE_CROSSCOMPILING:STRING=OFF

CMAKE_CXX_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP '

CMAKE_CXX_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

CMAKE_CXX_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//C compiler
CMAKE_C_COMPILER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe

CMAKE_C_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP '

CMAKE_C_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

//Flags used by the C compiler during MINSIZEREL builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /DNDEBUG

CMAKE_C_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//Flags used by the C compiler during RELWITHDEBINFO builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//No help, variable specified on the command line.
CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION:UNINITIALIZED=ON

//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during DEBUG builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during MINSIZEREL builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during RELWITHDEBINFO builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=

//No help, variable specified on the command line.
CMAKE_EXPORT_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY:UNINITIALIZED=ON

//Value Computed by CMake.
CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-rel/CMakeFiles/pkgRedirects

//No help, variable specified on the command line.
CMAKE_INSTALL_BINDIR:STRING=bin

//No help, variable specified on the command line.
CMAKE_INSTALL_LIBDIR:STRING=lib

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=C:/source/(3rd-party)/vcpkg/packages/bzip2_x64-windows

//No help, variable specified on the command line.
CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP:UNINITIALIZED=TRUE

//Path to a program.
CMAKE_LINKER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/link.exe

//make program
CMAKE_MAKE_PROGRAM:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe

//Flags used by the linker during the creation of modules during
// all build types.
CMAKE_MODULE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of modules during
// DEBUG builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of modules during
// MINSIZEREL builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of modules during
// RELWITHDEBINFO builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

CMAKE_MSVC_RUNTIME_LIBRARY:STRING=MultiThreaded$<$<CONFIG:Debug>:Debug>$<$<STREQUAL:dynamic,dynamic>:DLL>

//Path to a program.
CMAKE_MT:FILEPATH=C:/Program Files (x86)/Windows Kits/10/bin/10.0.22621.0/x64/mt.exe

//Value Computed by CMake
CMAKE_PROJECT_DESCRIPTION:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_HOMEPAGE_URL:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=bzip2

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=C:/Program Files (x86)/Windows Kits/10/bin/10.0.22621.0/x64/rc.exe

CMAKE_RC_FLAGS:STRING=-c65001 /DWIN32

//Flags for Windows Resource Compiler during DEBUG builds.
CMAKE_RC_FLAGS_DEBUG:STRING=-D_DEBUG

//Flags for Windows Resource Compiler during MINSIZEREL builds.
CMAKE_RC_FLAGS_MINSIZEREL:STRING=

//Flags for Windows Resource Compiler during RELEASE builds.
CMAKE_RC_FLAGS_RELEASE:STRING=

//Flags for Windows Resource Compiler during RELWITHDEBINFO builds.
CMAKE_RC_FLAGS_RELWITHDEBINFO:STRING=

//Flags used by the linker during the creation of shared libraries
// during all build types.
CMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of shared libraries
// during DEBUG builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of shared libraries
// during MINSIZEREL builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of shared libraries
// during RELWITHDEBINFO builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries
// during all build types.
CMAKE_STATIC_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of static libraries
// during DEBUG builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during MINSIZEREL builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during the creation of static libraries
// during RELEASE builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during RELWITHDEBINFO builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

CMAKE_SYSTEM_NAME:STRING=Windows

CMAKE_SYSTEM_PROCESSOR:STRING=AMD64

CMAKE_SYSTEM_VERSION:STRING=10.0.19045

//The CMake toolchain file
CMAKE_TOOLCHAIN_FILE:FILEPATH=C:/source/(3rd-party)/vcpkg/scripts/buildsystems/vcpkg.cmake

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=ON

//No help, variable specified on the command line.
FETCHCONTENT_FULLY_DISCONNECTED:UNINITIALIZED=ON

//Automatically copy dependencies into the output directory for
// executables.
VCPKG_APPLOCAL_DEPS:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_CHAINLOAD_TOOLCHAIN_FILE:UNINITIALIZED=C:/source/(3rd-party)/vcpkg/scripts/toolchains/windows.cmake

//No help, variable specified on the command line.
VCPKG_CRT_LINKAGE:UNINITIALIZED=dynamic

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_RELEASE:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_RELEASE:UNINITIALIZED=

//The directory which contains the installed libraries for each
// triplet
VCPKG_INSTALLED_DIR:PATH=C:/source/(3rd-party)/vcpkg/installed

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_RELEASE:UNINITIALIZED=

//The path to the vcpkg manifest directory.
VCPKG_MANIFEST_DIR:PATH=

//Use manifest mode, as opposed to classic mode.
VCPKG_MANIFEST_MODE:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_PLATFORM_TOOLSET:UNINITIALIZED=v143

//Appends the vcpkg paths to CMAKE_PREFIX_PATH, CMAKE_LIBRARY_PATH
// and CMAKE_FIND_ROOT_PATH so that vcpkg libraries/packages are
// found after toolchain/system libraries/packages.
VCPKG_PREFER_SYSTEM_LIBS:BOOL=OFF

//Enable the setup of CMAKE_PROGRAM_PATH to vcpkg paths
VCPKG_SETUP_CMAKE_PROGRAM_PATH:BOOL=ON

//No help, variable specified on the command line.
VCPKG_SET_CHARSET_FLAG:UNINITIALIZED=ON

//No help, variable specified on the command line.
VCPKG_TARGET_ARCHITECTURE:UNINITIALIZED=x64

//Vcpkg target triplet (ex. x86-windows)
VCPKG_TARGET_TRIPLET:STRING=x64-windows

//Trace calls to find_package()
VCPKG_TRACE_FIND_PACKAGE:BOOL=OFF

//Enables messages from the VCPKG toolchain for debugging purposes.
VCPKG_VERBOSE:BOOL=OFF

//(experimental) Automatically copy dependencies into the install
// target directory for executables. Requires CMake 3.14.
X_VCPKG_APPLOCAL_DEPS_INSTALL:BOOL=OFF

//(experimental) Add USES_TERMINAL to VCPKG_APPLOCAL_DEPS to force
// serialization.
X_VCPKG_APPLOCAL_DEPS_SERIALIZED:BOOL=OFF

//The directory which contains the installed libraries for each
// triplet
_VCPKG_INSTALLED_DIR:PATH=C:/source/(3rd-party)/vcpkg/installed

//No help, variable specified on the command line.
_VCPKG_ROOT_DIR:UNINITIALIZED=C:/source/(3rd-party)/vcpkg

//Value Computed by CMake
bzip2_BINARY_DIR:STATIC=C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-rel

//Value Computed by CMake
bzip2_IS_TOP_LEVEL:STATIC=ON

//Value Computed by CMake
bzip2_SOURCE_DIR:STATIC=C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean

########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=c:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-rel
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=29
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=2
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/ctest.exe
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake-gui.exe
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Generator instance identifier.
CMAKE_GENERATOR_INSTANCE:INTERNAL=
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MT
CMAKE_MT-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
//Platform information initialized
CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1
//noop for ranlib
CMAKE_RANLIB:INTERNAL=:
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_DEBUG
CMAKE_RC_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_MINSIZEREL
CMAKE_RC_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELEASE
CMAKE_RC_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELWITHDEBINFO
CMAKE_RC_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/share/cmake-3.29
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_TOOLCHAIN_FILE
CMAKE_TOOLCHAIN_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Install the dependencies listed in your manifest:
//\n    If this is off, you will have to manually install your dependencies.
//\n    See https://github.com/microsoft/vcpkg/tree/master/docs/specifications/manifests.md
// for more info.
//\n
VCPKG_MANIFEST_INSTALL:INTERNAL=OFF
//ADVANCED property for variable: VCPKG_VERBOSE
VCPKG_VERBOSE-ADVANCED:INTERNAL=1
//Making sure VCPKG_MANIFEST_MODE doesn't change
Z_VCPKG_CHECK_MANIFEST_MODE:INTERNAL=OFF
//Vcpkg root directory
Z_VCPKG_ROOT_DIR:INTERNAL=C:/source/(3rd-party)/vcpkg

C:\source\(3rd-party)\vcpkg\buildtrees\bzip2\config-x64-windows-dbg-CMakeCache.txt.log
# This is the CMakeCache file.
# For build in directory: c:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-dbg
# It was generated by CMake: C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe
# You can edit this file to change values found and used by cmake.
# If you do not want to change any of the values, simply exit the editor.
# If you do want to change a value, simply edit, save, and exit the editor.
# The syntax for the file is as follows:
# KEY:TYPE=VALUE
# KEY is the name of a variable in the cache.
# TYPE is a hint to GUIs for the type of VALUE, DO NOT EDIT TYPE!.
# VALUE is the current value for the KEY.

########################
# EXTERNAL cache entries
########################

//No help, variable specified on the command line.
BUILD_SHARED_LIBS:UNINITIALIZED=ON

//No help, variable specified on the command line.
BZ2_VERSION:UNINITIALIZED=1.0.8

//No help, variable specified on the command line.
BZIP2_SKIP_HEADERS:UNINITIALIZED=ON

//No help, variable specified on the command line.
BZIP2_SKIP_TOOLS:UNINITIALIZED=ON

//Path to a program.
CMAKE_AR:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/lib.exe

//Choose the type of build, options are: None Debug Release RelWithDebInfo
// MinSizeRel ...
CMAKE_BUILD_TYPE:STRING=Debug

CMAKE_CROSSCOMPILING:STRING=OFF

CMAKE_CXX_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP '

CMAKE_CXX_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

CMAKE_CXX_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//C compiler
CMAKE_C_COMPILER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/cl.exe

CMAKE_C_FLAGS:STRING=' /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP '

CMAKE_C_FLAGS_DEBUG:STRING='/D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1 '

//Flags used by the C compiler during MINSIZEREL builds.
CMAKE_C_FLAGS_MINSIZEREL:STRING=/MD /O1 /Ob1 /DNDEBUG

CMAKE_C_FLAGS_RELEASE:STRING='/MD /O2 /Oi /Gy /DNDEBUG /Z7 '

//Flags used by the C compiler during RELWITHDEBINFO builds.
CMAKE_C_FLAGS_RELWITHDEBINFO:STRING=/MD /Zi /O2 /Ob1 /DNDEBUG

//Libraries linked by default with all C applications.
CMAKE_C_STANDARD_LIBRARIES:STRING=kernel32.lib user32.lib gdi32.lib winspool.lib shell32.lib ole32.lib oleaut32.lib uuid.lib comdlg32.lib advapi32.lib

//No help, variable specified on the command line.
CMAKE_ERROR_ON_ABSOLUTE_INSTALL_DESTINATION:UNINITIALIZED=ON

//Flags used by the linker during all build types.
CMAKE_EXE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during DEBUG builds.
CMAKE_EXE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during MINSIZEREL builds.
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_EXE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during RELWITHDEBINFO builds.
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//Enable/Disable output of compile commands during generation.
CMAKE_EXPORT_COMPILE_COMMANDS:BOOL=

//No help, variable specified on the command line.
CMAKE_EXPORT_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY:UNINITIALIZED=ON

//No help, variable specified on the command line.
CMAKE_FIND_PACKAGE_NO_SYSTEM_PACKAGE_REGISTRY:UNINITIALIZED=ON

//Value Computed by CMake.
CMAKE_FIND_PACKAGE_REDIRECTS_DIR:STATIC=C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-dbg/CMakeFiles/pkgRedirects

//No help, variable specified on the command line.
CMAKE_INSTALL_BINDIR:STRING=bin

//No help, variable specified on the command line.
CMAKE_INSTALL_LIBDIR:STRING=lib

//Install path prefix, prepended onto install directories.
CMAKE_INSTALL_PREFIX:PATH=C:/source/(3rd-party)/vcpkg/packages/bzip2_x64-windows/debug

//No help, variable specified on the command line.
CMAKE_INSTALL_SYSTEM_RUNTIME_LIBS_SKIP:UNINITIALIZED=TRUE

//Path to a program.
CMAKE_LINKER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.39.33519/bin/Hostx64/x64/link.exe

//make program
CMAKE_MAKE_PROGRAM:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Professional/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe

//Flags used by the linker during the creation of modules during
// all build types.
CMAKE_MODULE_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of modules during
// DEBUG builds.
CMAKE_MODULE_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of modules during
// MINSIZEREL builds.
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_MODULE_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of modules during
// RELWITHDEBINFO builds.
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

CMAKE_MSVC_RUNTIME_LIBRARY:STRING=MultiThreaded$<$<CONFIG:Debug>:Debug>$<$<STREQUAL:dynamic,dynamic>:DLL>

//Path to a program.
CMAKE_MT:FILEPATH=C:/Program Files (x86)/Windows Kits/10/bin/10.0.22621.0/x64/mt.exe

//Value Computed by CMake
CMAKE_PROJECT_DESCRIPTION:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_HOMEPAGE_URL:STATIC=

//Value Computed by CMake
CMAKE_PROJECT_NAME:STATIC=bzip2

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=C:/Program Files (x86)/Windows Kits/10/bin/10.0.22621.0/x64/rc.exe

CMAKE_RC_FLAGS:STRING=-c65001 /DWIN32

//Flags for Windows Resource Compiler during DEBUG builds.
CMAKE_RC_FLAGS_DEBUG:STRING=-D_DEBUG

//Flags for Windows Resource Compiler during MINSIZEREL builds.
CMAKE_RC_FLAGS_MINSIZEREL:STRING=

//Flags for Windows Resource Compiler during RELEASE builds.
CMAKE_RC_FLAGS_RELEASE:STRING=

//Flags for Windows Resource Compiler during RELWITHDEBINFO builds.
CMAKE_RC_FLAGS_RELWITHDEBINFO:STRING=

//Flags used by the linker during the creation of shared libraries
// during all build types.
CMAKE_SHARED_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of shared libraries
// during DEBUG builds.
CMAKE_SHARED_LINKER_FLAGS_DEBUG:STRING=/nologo    /debug /INCREMENTAL

//Flags used by the linker during the creation of shared libraries
// during MINSIZEREL builds.
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL:STRING=/INCREMENTAL:NO

CMAKE_SHARED_LINKER_FLAGS_RELEASE:STRING='/nologo /DEBUG /INCREMENTAL:NO /OPT:REF /OPT:ICF  '

//Flags used by the linker during the creation of shared libraries
// during RELWITHDEBINFO builds.
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO:STRING=/debug /INCREMENTAL

//If set, runtime paths are not added when installing shared libraries,
// but are added when building.
CMAKE_SKIP_INSTALL_RPATH:BOOL=NO

//If set, runtime paths are not added when using shared libraries.
CMAKE_SKIP_RPATH:BOOL=NO

//Flags used by the linker during the creation of static libraries
// during all build types.
CMAKE_STATIC_LINKER_FLAGS:STRING=/machine:x64

//Flags used by the linker during the creation of static libraries
// during DEBUG builds.
CMAKE_STATIC_LINKER_FLAGS_DEBUG:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during MINSIZEREL builds.
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL:STRING=

//Flags used by the linker during the creation of static libraries
// during RELEASE builds.
CMAKE_STATIC_LINKER_FLAGS_RELEASE:STRING=/nologo

//Flags used by the linker during the creation of static libraries
// during RELWITHDEBINFO builds.
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO:STRING=

CMAKE_SYSTEM_NAME:STRING=Windows

CMAKE_SYSTEM_PROCESSOR:STRING=AMD64

CMAKE_SYSTEM_VERSION:STRING=10.0.19045

//The CMake toolchain file
CMAKE_TOOLCHAIN_FILE:FILEPATH=C:/source/(3rd-party)/vcpkg/scripts/buildsystems/vcpkg.cmake

//If this value is on, makefiles will be generated without the
// .SILENT directive, and all commands will be echoed to the console
// during the make.  This is useful for debugging only. With Visual
// Studio IDE projects all commands are done without /nologo.
CMAKE_VERBOSE_MAKEFILE:BOOL=ON

//No help, variable specified on the command line.
FETCHCONTENT_FULLY_DISCONNECTED:UNINITIALIZED=ON

//Automatically copy dependencies into the output directory for
// executables.
VCPKG_APPLOCAL_DEPS:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_CHAINLOAD_TOOLCHAIN_FILE:UNINITIALIZED=C:/source/(3rd-party)/vcpkg/scripts/toolchains/windows.cmake

//No help, variable specified on the command line.
VCPKG_CRT_LINKAGE:UNINITIALIZED=dynamic

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_CXX_FLAGS_RELEASE:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_C_FLAGS_RELEASE:UNINITIALIZED=

//The directory which contains the installed libraries for each
// triplet
VCPKG_INSTALLED_DIR:PATH=C:/source/(3rd-party)/vcpkg/installed

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_DEBUG:UNINITIALIZED=

//No help, variable specified on the command line.
VCPKG_LINKER_FLAGS_RELEASE:UNINITIALIZED=

//The path to the vcpkg manifest directory.
VCPKG_MANIFEST_DIR:PATH=

//Use manifest mode, as opposed to classic mode.
VCPKG_MANIFEST_MODE:BOOL=OFF

//No help, variable specified on the command line.
VCPKG_PLATFORM_TOOLSET:UNINITIALIZED=v143

//Appends the vcpkg paths to CMAKE_PREFIX_PATH, CMAKE_LIBRARY_PATH
// and CMAKE_FIND_ROOT_PATH so that vcpkg libraries/packages are
// found after toolchain/system libraries/packages.
VCPKG_PREFER_SYSTEM_LIBS:BOOL=OFF

//Enable the setup of CMAKE_PROGRAM_PATH to vcpkg paths
VCPKG_SETUP_CMAKE_PROGRAM_PATH:BOOL=ON

//No help, variable specified on the command line.
VCPKG_SET_CHARSET_FLAG:UNINITIALIZED=ON

//No help, variable specified on the command line.
VCPKG_TARGET_ARCHITECTURE:UNINITIALIZED=x64

//Vcpkg target triplet (ex. x86-windows)
VCPKG_TARGET_TRIPLET:STRING=x64-windows

//Trace calls to find_package()
VCPKG_TRACE_FIND_PACKAGE:BOOL=OFF

//Enables messages from the VCPKG toolchain for debugging purposes.
VCPKG_VERBOSE:BOOL=OFF

//(experimental) Automatically copy dependencies into the install
// target directory for executables. Requires CMake 3.14.
X_VCPKG_APPLOCAL_DEPS_INSTALL:BOOL=OFF

//(experimental) Add USES_TERMINAL to VCPKG_APPLOCAL_DEPS to force
// serialization.
X_VCPKG_APPLOCAL_DEPS_SERIALIZED:BOOL=OFF

//The directory which contains the installed libraries for each
// triplet
_VCPKG_INSTALLED_DIR:PATH=C:/source/(3rd-party)/vcpkg/installed

//No help, variable specified on the command line.
_VCPKG_ROOT_DIR:UNINITIALIZED=C:/source/(3rd-party)/vcpkg

//Value Computed by CMake
bzip2_BINARY_DIR:STATIC=C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-dbg

//Value Computed by CMake
bzip2_IS_TOP_LEVEL:STATIC=ON

//Value Computed by CMake
bzip2_SOURCE_DIR:STATIC=C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean

########################
# INTERNAL cache entries
########################

//ADVANCED property for variable: CMAKE_AR
CMAKE_AR-ADVANCED:INTERNAL=1
//This is the directory where this CMakeCache.txt was created
CMAKE_CACHEFILE_DIR:INTERNAL=c:/source/(3rd-party)/vcpkg/buildtrees/bzip2/x64-windows-dbg
//Major version of cmake used to create the current loaded cache
CMAKE_CACHE_MAJOR_VERSION:INTERNAL=3
//Minor version of cmake used to create the current loaded cache
CMAKE_CACHE_MINOR_VERSION:INTERNAL=29
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=2
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/ctest.exe
//ADVANCED property for variable: CMAKE_C_COMPILER
CMAKE_C_COMPILER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS
CMAKE_C_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_DEBUG
CMAKE_C_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_MINSIZEREL
CMAKE_C_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELEASE
CMAKE_C_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_FLAGS_RELWITHDEBINFO
CMAKE_C_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_C_STANDARD_LIBRARIES
CMAKE_C_STANDARD_LIBRARIES-ADVANCED:INTERNAL=1
//Path to cache edit program executable.
CMAKE_EDIT_COMMAND:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/bin/cmake-gui.exe
//Executable file format
CMAKE_EXECUTABLE_FORMAT:INTERNAL=Unknown
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS
CMAKE_EXE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_DEBUG
CMAKE_EXE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_MINSIZEREL
CMAKE_EXE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELEASE
CMAKE_EXE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_EXE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_EXPORT_COMPILE_COMMANDS
CMAKE_EXPORT_COMPILE_COMMANDS-ADVANCED:INTERNAL=1
//Name of external makefile project generator.
CMAKE_EXTRA_GENERATOR:INTERNAL=
//Name of generator.
CMAKE_GENERATOR:INTERNAL=Ninja
//Generator instance identifier.
CMAKE_GENERATOR_INSTANCE:INTERNAL=
//Name of generator platform.
CMAKE_GENERATOR_PLATFORM:INTERNAL=
//Name of generator toolset.
CMAKE_GENERATOR_TOOLSET:INTERNAL=
//Source directory with the top level CMakeLists.txt file for this
// project
CMAKE_HOME_DIRECTORY:INTERNAL=C:/source/(3rd-party)/vcpkg/buildtrees/bzip2/src/bzip2-1-336d4794a3.clean
//ADVANCED property for variable: CMAKE_LINKER
CMAKE_LINKER-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS
CMAKE_MODULE_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_DEBUG
CMAKE_MODULE_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL
CMAKE_MODULE_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELEASE
CMAKE_MODULE_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_MODULE_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_MT
CMAKE_MT-ADVANCED:INTERNAL=1
//number of local generators
CMAKE_NUMBER_OF_MAKEFILES:INTERNAL=1
//Platform information initialized
CMAKE_PLATFORM_INFO_INITIALIZED:INTERNAL=1
//noop for ranlib
CMAKE_RANLIB:INTERNAL=:
//ADVANCED property for variable: CMAKE_RC_COMPILER
CMAKE_RC_COMPILER-ADVANCED:INTERNAL=1
CMAKE_RC_COMPILER_WORKS:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS
CMAKE_RC_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_DEBUG
CMAKE_RC_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_MINSIZEREL
CMAKE_RC_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELEASE
CMAKE_RC_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_RC_FLAGS_RELWITHDEBINFO
CMAKE_RC_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//Path to CMake installation.
CMAKE_ROOT:INTERNAL=C:/source/(3rd-party)/vcpkg/downloads/tools/cmake-3.29.2-windows/cmake-3.29.2-windows-i386/share/cmake-3.29
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS
CMAKE_SHARED_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_DEBUG
CMAKE_SHARED_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL
CMAKE_SHARED_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELEASE
CMAKE_SHARED_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_SHARED_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_INSTALL_RPATH
CMAKE_SKIP_INSTALL_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_SKIP_RPATH
CMAKE_SKIP_RPATH-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS
CMAKE_STATIC_LINKER_FLAGS-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_DEBUG
CMAKE_STATIC_LINKER_FLAGS_DEBUG-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL
CMAKE_STATIC_LINKER_FLAGS_MINSIZEREL-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELEASE
CMAKE_STATIC_LINKER_FLAGS_RELEASE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO
CMAKE_STATIC_LINKER_FLAGS_RELWITHDEBINFO-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_TOOLCHAIN_FILE
CMAKE_TOOLCHAIN_FILE-ADVANCED:INTERNAL=1
//ADVANCED property for variable: CMAKE_VERBOSE_MAKEFILE
CMAKE_VERBOSE_MAKEFILE-ADVANCED:INTERNAL=1
//Install the dependencies listed in your manifest:
//\n    If this is off, you will have to manually install your dependencies.
//\n    See https://github.com/microsoft/vcpkg/tree/master/docs/specifications/manifests.md
// for more info.
//\n
VCPKG_MANIFEST_INSTALL:INTERNAL=OFF
//ADVANCED property for variable: VCPKG_VERBOSE
VCPKG_VERBOSE-ADVANCED:INTERNAL=1
//Making sure VCPKG_MANIFEST_MODE doesn't change
Z_VCPKG_CHECK_MANIFEST_MODE:INTERNAL=OFF
//Vcpkg root directory
Z_VCPKG_ROOT_DIR:INTERNAL=C:/source/(3rd-party)/vcpkg

Try without parentheses in path.

Thanks for the quick hand!