PR: Profile in the IPython console to gain access to variables and get a result in case of cancellation

Description of Changes
Add profile_file and profile_cell functions to the shell with the same signature as runcell/debugcell and runfile/debugfile
This solves a few issues I have with profiling, including:

Profiling when the user want to use the current namespace
Profiling when the user want to stop the profiled script in the middle
Profiling a Cell
Depends on #spyder-ide/spyder-kernels#451.

Issue(s) Resolved

Fixes #2378
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

Hello @impact27! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file external-deps/spyder-kernels/spyder_kernels/customize/spydercustomize.py:

Line 458:35: W291 trailing whitespace
Line 459:17: E128 continuation line under-indented for visual indent
Line 460:17: E128 continuation line under-indented for visual indent
Line 461:13: E124 closing bracket does not match visual indentation
Line 465:26: W291 trailing whitespace
Line 585:47: W291 trailing whitespace
Line 638:17: E128 continuation line under-indented for visual indent
Line 657:1: E305 expected 2 blank lines after class or function definition, found 1
Line 731:1: W293 blank line contains whitespace
Line 770:1: E305 expected 2 blank lines after class or function definition, found 1

In the file external-deps/spyder-kernels/spyder_kernels/customize/spyderpdb.py:

Line 731:9: E303 too many blank lines (2)

In the file spyder/plugins/ipythonconsole/plugin.py:

Line 783:26: E225 missing whitespace around operator
Line 788:28: E225 missing whitespace around operator
Line 821:22: E127 continuation line over-indented for visual indent
Line 824:24: E128 continuation line under-indented for visual indent
Line 825:24: E128 continuation line under-indented for visual indent
Line 831:24: E128 continuation line under-indented for visual indent
Line 832:24: E128 continuation line under-indented for visual indent

In the file spyder/plugins/profiler/widgets/main_widget.py:

Line 384:1: W293 blank line contains whitespace

Hey @impact27, please post an animated gif/video of the new behavior.

List of improvements:

Access to local variables in the console
Can compare several runs by profiling in different consoles
Can profile in the same environment as the code is run
Can get a result even if the run is interrupted (For example if the code reaches an infinite loop)

@impact27, so this replaces the existing "Run profiler" menu item with "Profile file" and "Profile cell", correct? And the heavy lifting is moved to spyder-kernels so that the profiler is always run in an existing IPython Console environment (inheriting its os.environ, etc.), correct?
If the above is correct, then I agree that this PR should resolve #18010 and obviate PR #18031.

@impact27, so this replaces the existing "Run profiler" menu item with "Profile file" and "Profile cell", correct? And the heavy lifting is moved to spyder-kernels so that the profiler is always run in an existing IPython Console environment (inheriting its os.environ, etc.), correct?
If the above is correct, then I agree that this PR should resolve #18010 and obviate PR #18031.

Yes exactly, the profiling would happen in the spyder-kernel, so there would be no difference with runfile and debugfile

@impact27 and @ccordoba12, when will this PR be ready for review? Should this be included in 5.3.2 milestone?

This is ready for review, assuming the tests pass when they are fixed

If the IPythonConsole will profile the files, we would prefer to use the viewer run API instead.

The toolobar looks like:
Dark:

Light:

@impact27, I think you need to rewrite this work on top of the new Run architecture defined in PR #17467, which I just merged.

@impact27, I think you need to rewrite this work on top of the new Run architecture defined in PR #17467, which I just merged.
Sorry for the inconvenience, but that's something I finally have time to review and merge until now

I am not sure what I should do, what I do here is basically the same as in the debug plugin, but the changes there include the following warning:
# TODO: This is a temporary measure to debug selections whilst the
# debug API is defined.

Should I replicate this here?

I used the new Run architecture but I find it a bit confusing. If I want to switch from regular execute to profiling I have to go to the setting every time, and I need to use the green arrow to launch the profiling. I guess this would be the same for debugging

@ccordoba12 I will adapt the debugger as well

@ccordoba12 the profiler and debugger have been ported to the run plug-in. Furthermore I added a toolbar in both plugins so you can run the file/cell/selection from there. There also is a toolbar in the main toolbar and it can be disabled.

@ccordoba12 I moved the "Run code" section of the editor plugin because it doesn't make sense there

@ccordoba12 I split the debugger and editor cleanup in https://github.com/spyder-ide/spyder/pull/20557

@ccordoba12 I moved the runfile to magics code to https://github.com/spyder-ide/spyder/pull/20633 so you can take a look at this one independently

@ccordoba12 @impact27 I was checking and, if understand correctly, this PR changes quite a bit the way the Profiler pane looks and works, right? Should the changes here supersede the ones defined at https://github.com/spyder-ide/ux-improvements/issues/20 ? or how should we align the changes here with the ones proposed there in some other way?

@dalthviz There are several things in spyder-ide/ux-improvements#20. I would say:

I am doing console integration rather than editor integration, because you could want to profile cells or selections or snippets and these do not match neatly to a file.
I am not against a history function but for now this PR improves the save / load features so part of the functionality is there

In general I think there are some ideas we can keep from spyder-ide/ux-improvements#20. But these can be included in future PRs?

Thanks for the response @impact27 ! Seems like we should rediscuss https://github.com/spyder-ide/ux-improvements/issues/20 reevaluating how those old ideas apply not only for the interaction with the Editor but also with the integration you are doing here with the IPython console and in general the new functionality to not only profile files but cells/code selections, right?

In general I think there are some ideas we can keep from https://github.com/spyder-ide/ux-improvements/issues/20. But these can be included in future PRs?

Definitely more things can be done in follow up PRs! I just wanted to have a more clear idea on how the profiler is expected to work and also bring up some UX/UI ideas that were discussed in the past about the Profiler plugin.

Do you have a specific modification you want to propose to this PR?

I don't have any specific modification but I will try to check this more thoroughly to give some feedback :+1:

Hi @dalthviz , I am trying to add the actions in the run menu, but I can't find a way to add them after the run actions. There is no "after_section" and the profiler is called before the run module.

@dalthviz I worked around this issue by checking that the main menu is setup before adding secondary run buttons, as you can see in my last commit

Hi @dalthviz , I am trying to add the actions in the run menu, but I can't find a way to add them after the run actions. There is no "after_section" and the profiler is called before the run module.

@dalthviz I worked around this issue by checking that the main menu is setup before adding secondary run buttons, as you can see in my last commit

Hi @impact27 ! I think another option is to use the RunMenuSections.RunInExecutors section. I think the order for the Run menu section is RunMenuSections.Run (main run actions, i.e run file and config), then comes RunMenuSections.RunExtras (extra run options like run cell/selection) and then the final section which is RunMenuSections.RunInExecutors (I think this last section was though for the actions of executors like in this case the profiler).
Your approach seems fine too so not sure what could be the best 🤔 What do you think with this new info?

Well this is not exactly the same as you have a list of plot and are browsing them vs the previous / next of a web browser. What do you think?

I was checking and seems like the same previous/next icon for Plots is being used in the Online Help pane:

Not sure if there are other panes where back/forward - previous/next icons are set. I think it would be nice to have the same icon for all panes for similar actions for consistency around the UI but its true that maybe we could have one set for more page like navigation (as a browser, like here and in the Online Help pane) and other set for more previous/next like actions (like the Plots pane) so actually not sure.
Pinging @ccordoba12 @conradolandia and @CAM-Gerlach maybe they could have some ideas regarding the icons

Hmm, not sure but the Plots pane button match much more closely the typical icons for forward/back in a web browser and other contexts, vs. the buttons icons used in the Profiler pane.
Given the plots are actually listed vertical rather than horizontally, maybe vertical arrows would make more sense there instead?

The name of the icons are undo / redo, which is what they are used for. I feel like left / right arrows would be more suited for browsing different profiling results (which this plugin doesn't do)

Oh sorry, I guess I'm confused—I thought the buttons were for browsing previous profiling runs on the file, but I guess not? Could you explain what action/change the buttons undo and redo?

So the idea is that you can change the way the profiling results are shown:

by default, only the top-level elements are shown
You can focus on elements with large local time (Which might be called from different code path)
You can switch the direction of the tree from callers to callees
You can focus on a specific function

When you change the view, some elements appear / disappear. The undo / redo button allow you to go back to the previous view

Ah, gotcha, thanks. In that case, it seems to me that the undo/redo buttons make more sense, then, given I'd assume more typical "Back" and "Forward" buttons would be navigating the history of different profiles instead.

@impact27, could you fix the merge conflicts in this PR so I can start reviewing it? Thanks!

@impact27, please update this PR to see if we can merge it next.

@ccordoba12 I updated this PR to merge on 6.x but there are no tests running?

@impact27, now 6.x and master are independent branches, so you can't perform merges between them (that's why your history now shows all backport PRs we created against 6.x, which can't be merged back to master because the code for them is already there).
Do you want me to give you hand to fix your branch?

Do you want me to give you a hand to fix your branch?
Yes that would be great thanks


Anyway to do events without callbacks? like my_sockette_instance.on('message', () => { })

Nope, sorry! This is because the WS instance swaps out over time, and it would be another 300 bytes to setup that abstraction.
Sorry 😀


Add a draft for a blog entry

This is a draft for the promised blog entry about my BSSW fellowship @bernhold. I have one question concerning figures: Should I make a  separate PR to betterscientificsoftware/images for them? And is there a way to preview the figures in the final text? I would like to see if they have an appropriate size and how they fit into the sections.
Let me know what you think about it, I am happy to modify it.

I updated with some small fixes and a note that can be pursued or ignored.

I have reviewed this and it looks good overall. Fixed a few more typos. I saw a note from Gail in there for clarification on a particular sentence (IMO, the sentence makes sense as is and Gail's note can be  disregarded but I leave it up to David/Rene to decide)

Thank you all for the comments, I think the text is much better now. I am fine with the current version, just waiting for some guidance on the one remaining question.


handle private packages

https://www.npmjs.com/npm/private-packages#organizations
This is the only thing that is preventing me from using ied :(

See #7.

They're on their way! I promise!


Github webhook enhancements

Resolves #886 #910
Call whisk.error() with the actual error object received.
Call whisk.error() when the status code from Github is something other than 200.
Allow the repository parameter to optionally be specified as <organization>/<repoName> so that it can be used to track repositories that aren't directly owned by the user.

@psuter @rabbah @starpit Would you mind having a look at this? I believe all the returns are in order: One when lifeCycleEvent is CREATE and one for all other cases.

Merged as 9fceba2ee3f9a06e6466f6fe71f2d1235c4dbde1.


Update argocd-ingress example to work with new argocd helm 6.x

Depends on https://github.com/gitops-bridge-dev/gitops-bridge-argocd-control-plane-template/issues/41

Closed by #54


Pod install error

Hi. I am new at apple. i can't  solve this. When i write pod install it gives error. When i delete pod geoswift it works. My podfile
source 'https://github.com/CocoaPods/Spces.git'
platform :ios, '8.0'
use_frameworks!
pod 'Alamofire', '~> 3.0'
pod 'GEOSwift'

@Thornaci can you please post the error message you are getting?
Have you read the note below, extracted from the readme file?

Run pod install.

NOTE: running pod install may cause some errors if your machine does not have autoconf, automake and glibtool, if you encounter those errors you can run brew install autoconf automake libtool to install those packages and run again pod install.

Thornaci-MacBook-Pro:deneme Thornaci$ pod install
Updating local specs repositories
Analyzing dependencies
Downloading dependencies
Using Alamofire (3.1.3)
Installing GEOSwift (0.3.0)
Installing geos (3.4.2a)
[!] Error installing geos
[!] /usr/bin/svn export --non-interactive --trust-server-cert --force https://svn.osgeo.org/geos/tags/3.4.2 /var/folders/jm/v6xncwpn3bx9t7lw55fb_lbr0000gn/T/d20151126-405-ooxwka
svn: E175002: Unable to connect to a repository at URL 'https://svn.osgeo.org/geos/tags/3.4.2'
svn: E175002: OPTIONS of 'https://svn.osgeo.org/geos/tags/3.4.2': Could not resolve hostname `svn.osgeo.org': Host not found (https://svn.osgeo.org)

@Thornaci are you behind a proxy by any chance?
Can you open the URL https://svn.osgeo.org/geos/tags/3.4.2 on your browser?
Have a look at how to setup svn to work with a proxy
http://stackoverflow.com/questions/1491180/how-to-configure-a-http-proxy-for-svn

Thank you the problem solved :)


Merge develop into master

Codecov Report

Merging #147 into master will decrease coverage by -0.59%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #147      +/-   ##
==========================================
- Coverage    93.5%   92.91%   -0.59%
==========================================
  Files          33       38       +5
  Lines        1140     1257     +117
  Branches       55       69      +14
==========================================
+ Hits         1066     1168     +102
- Misses         62       77      +15
  Partials       12       12

Impacted Files
Coverage Δ

datahub/interaction/views.py
100% <100%> (ø)
:white_check_mark:

datahub/company/admin.py
88.88% <100%> (ø)

datahub/company/management/commands/manageusers.py
100% <100%> (ø)

datahub/metadata/admin.py
100% <0%> (ø)

datahub/core/admin.py
68.57% <0%> (ø)

datahub/interaction/admin.py
100% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fd2606b...29b110d. Read the comment docs.


Fix README broken link and add missing Migration Guides section

This pull request:

fixes the Migration Guides broken link by adding a missing section to the README.md file

Resolved issues:

#597

Short description:
Currently there's a broken link in the README.md's Contents section - Migration Guides link doesn't lead anywhere since a section with that name doesn't exist. In this pull request I've added that missing Migration Guides section and I've listed migration guides stored in Snapkit/Documentation/ directory (currently it contains just one file: SnapKit 3.0 Migration Guide.md).

Thank you


Handle Callback without waiting/reattempting?

I'll preface this with saying my use case here might be a little niche.
I'm using go-github-ratelimit in a Kubernetes controller where I have a pool of go-github clients allocated. Because of the nature of the controller, it's not feasible to wait/block for significant periods of time. Instead, it's preferable for the controller to requeue and reattempt later.
I've defined a callback function that cordons off the affect client until the wait period is over, and allows the HTTP request to fail/return an error. At which point, the controller will requeue and reattempt with a different client. However, go-github-ratelimit is still waiting outside of the callback function, and reattempting the request.
Basically what I'm wondering is, is it possible to use go-github-ratelimit to catch the Secondary rate limit error, execute some callback function, and then allow the request to fail, without waiting?
My current alternative is to manually check the response from go-github for a secondary rate limit error and do the necessary steps there, but being able to do this in a package would be nice 🙂

Just realized that I can achieve what I need by using github_ratelimit.WithSingleSleepLimit and passing a 0 (or small value) to the sleep limit.
The callback context's sleepUntil value will still be based on what was set in the Retry-After / x-ratelimit-reset header, and I can use that in my callback if needed.
I think this issue can be closed, unless there's any problems with this approach?

Just realized that I can achieve what I need by using github_ratelimit.WithSingleSleepLimit and passing a 0 (or small value) to the sleep limit.

Yep, that's exactly what I was about to suggest.
Just note that you need to use the onSingleLimitExceeded callback now (the onLimitDetected isn't triggered if the sleep duration is above the limit).
Also note that rather than getting an error from the ratelimit client, it'll return the original response.
Assuming you use go-github as the client, you'll get an AbuseRateLimitError from it.
btw, it doesn't support x-ratelimit-reset for secondary rate limit yet, which I know you're facing - so don't rely on its RetryAfter field for the sleep (it'll still return that error AbuseRateLimitError though).
I was planning to support to add the option to get an error rather than sleep-and-retry as part of the breaking changes for V2, but I can implement that part without breaking anything - so let's keep this issue open for that purpose.

One last thing -
In the original notification I got in the mail for the issue in appstudio, you mentioned:
In my tests, I'm finding that time.Until(*cbContext.SleepUntil) is a negative number, and the callback function is already sleeping before I call my time.Sleep
This should never happen: the callback should be called before the sleep. I think I'll add some tests for the callback context.
Anyway, you edited this comment so I hope that means that it was because something was wrong in the testing, but I want to make sure that there's no real issue lurking here (so please elaborate).

Anyway, you edited this comment so I hope that means that it was because something was wrong in the testing, but I want to make sure that there's no real issue lurking here (so please elaborate).

Yup, it wasn't an issue in go-github-ratelimit, it was related to the testing and the fact I was stopping at breakpoints.


Add flexibility to JWT token validation in openapi-security

The openapi-security module, via the JwtVerifyHandler class, extracts and validates 2 JWT tokens:

Subject Token - located in the header in the Authorization header
Scope Token - located in the header in the X_Scope_token header

In both cases, the extracted claims, after validation, are stored in the AuditInfo, and made available to subsequent handlers in the handler chain.
The Scope Token is being extracted from the request and validated only if scope verification is enabled.
To allow for additional flexibility, this issue should address the following items:

Allow for the scope token to be extracted, its signature validated, independent of whether scope validation is enabled / disabled and its claims extracted.
Allow for the configuration to extract and validate custom tokens from the request, in case a developer has a use case where such tokens are beneficial. A custom location in the header would have to be pre-configured with the header location to look into

If my memory serves, we only extract custom claims from the Subject token because customer claims only associate with the login user from the originator. I am not sure if we should support custom claims from additional tokens.

We are extracting the claims from both Subject and Scope Token and store them in AUDIT_INFO, under "subject_claims", respectively "access_claims". That change was made a long time ago.
The claims from the Subject token identify the original caller, and the Subject token is propagated in an API chain.
The claims from the Scope Token are claims set by the immediate caller.
To solve this issue, addressing what is listed above in [1] is sufficient, for simplicity reasons.

 Add flexibility to JWT token validation in openapi-security light-rest-4j 1.6.x

 Add flexibility to JWT token validation in openapi-security

My client is using this flag and, unless there is a compelling reason for changing, it might be better to leave it as is.

@jsu216 When there are too many flags to control fine-grained behaviors, it is very easy to make users confused. Do you think we can make the comment in the config file more clear to resolve the problem?

I am not asking for any code change. Just want to make sure that the comment or document should reflect what the behaviour is supposed to be.

@jsu216 Any suggestions on how to update the comment and the document?

@stevehu Can you give me the link to the document regarding this? What I found was from the comments in openapi-security.yml at the test resource folder, which is the official doc.

Yes. The most important place is inline comments in the openapi-security.yml file. Also, this document link needs to be in sync. https://doc.networknt.com/style/light-rest-4j/openapi-security/


[testing] Fixing Extra Trees and Random Forest preview test_common.py issues

Description
Unify and modernize aspects of preview ensemble for test coverage and maintainability
Changes proposed in this pull request:

estimators to BaseForest
onedal_fit to BaseForest (matches sklearn)
cleanup in cpu_supported etc.

/azp run Nightly

/intelci: run

/intelci: run

/intelci: run

/intelci: run

Oh man, a green private CI.


[pkgconf] Build error on x64-windows

Package<EMAIL_ADDRESS>Host Environment

Host: x64-windows
Compiler: MSVC 19.36.32537.0
vcpkg-tool version: 2024-01-11-710a3116bbd615864eef5f9010af178034cb9b44
vcpkg-scripts version: a1a1cbc97 2024-01-19 (4 hours ago)

To Reproduce
vcpkg install libusb
Failure logs
-- Downloading https://github.com/pkgconf/pkgconf/archive/pkgconf-2.1.0.tar.gz -> pkgconf-pkgconf-pkgconf-2.1.0.tar.gz...
-- Extracting source C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/pkgconf-pkgconf-pkgconf-2.1.0.tar.gz
-- Using source at C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/src/conf-2.1.0-7b1cf1fe7f.clean
-- Found external ninja('1.11.0').
-- Getting CMake variables for x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
    Working Directory: C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      C:\Users\PrintedJungle38\Desktop\vcpkg\buildtrees\pkgconf\get-cmake-vars-x64-windows-dbg-CMakeCache.txt.log
      C:\Users\PrintedJungle38\Desktop\vcpkg\buildtrees\pkgconf\get-cmake-vars-x64-windows-rel-CMakeCache.txt.log
      C:\Users\PrintedJungle38\Desktop\vcpkg\buildtrees\pkgconf\get-cmake-vars-x64-windows-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:314 (vcpkg_execute_required_process)
  scripts/cmake/z_vcpkg_get_cmake_vars.cmake:18 (vcpkg_configure_cmake)
  scripts/cmake/vcpkg_configure_meson.cmake:317 (z_vcpkg_get_cmake_vars)
  ports/pkgconf/portfile.cmake:9 (vcpkg_configure_meson)
  scripts/ports.cmake:170 (include)

C:\Users\PrintedJungle38\Desktop\vcpkg\buildtrees\pkgconf\get-cmake-vars-x64-windows-out.log
[1/2] "C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" -E chdir ".." "C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" "C:/Users/PrintedJungle38/Desktop/vcpkg/scripts/get_cmake_vars" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/Users/PrintedJungle38/Desktop/vcpkg/packages/pkgconf_x64-windows" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/vcpkg" "-DZ_VCPKG_ROOT_DIR=C:/Users/PrintedJungle38/Desktop/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Users/PrintedJungle38/Desktop/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DVCPKG_OUTPUT_FILE:PATH=C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/cmake-vars-x64-windows-rel.cmake.log"
FAILED: ../CMakeCache.txt
"C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" -E chdir ".." "C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" "C:/Users/PrintedJungle38/Desktop/vcpkg/scripts/get_cmake_vars" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Release" "-DCMAKE_INSTALL_PREFIX=C:/Users/PrintedJungle38/Desktop/vcpkg/packages/pkgconf_x64-windows" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/vcpkg" "-DZ_VCPKG_ROOT_DIR=C:/Users/PrintedJungle38/Desktop/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Users/PrintedJungle38/Desktop/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DVCPKG_OUTPUT_FILE:PATH=C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/cmake-vars-x64-windows-rel.cmake.log"
-- The C compiler identification is MSVC 19.36.32537.0
-- The CXX compiler identification is MSVC 19.36.32537.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/cl.exe - broken
CMake Error at C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/share/cmake-3.27/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

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

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: 'C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/x64-windows-rel/CMakeFiles/CMakeScratch/TryCompile-umuoar'

    Run Build Command(s): "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v cmTC_473c2
    [1/2] C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe  /nologo   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP   /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -MDd /showIncludes /FoCMakeFiles\cmTC_473c2.dir\testCCompiler.c.obj /FdCMakeFiles\cmTC_473c2.dir\ /FS -c C:\Users\PrintedJungle38\Desktop\vcpkg\buildtrees\pkgconf\x64-windows-rel\CMakeFiles\CMakeScratch\TryCompile-umuoar\testCCompiler.c
    [2/2] cmd.exe /C "cd . && C:\Users\PrintedJungle38\Desktop\vcpkg\downloads\tools\cmake-3.27.1-windows\cmake-3.27.1-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_473c2.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_473c2.dir\testCCompiler.c.obj  /out:cmTC_473c2.exe /implib:cmTC_473c2.lib /pdb:cmTC_473c2.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_473c2.exe
    cmd.exe /C "cd . && C:\Users\PrintedJungle38\Desktop\vcpkg\downloads\tools\cmake-3.27.1-windows\cmake-3.27.1-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_473c2.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_473c2.dir\testCCompiler.c.obj  /out:cmTC_473c2.exe /implib:cmTC_473c2.lib /pdb:cmTC_473c2.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 ."
    RC Pass 1: command "rc /fo CMakeFiles\cmTC_473c2.dir/manifest.res CMakeFiles\cmTC_473c2.dir/manifest.rc" failed (exit code 0) with the following output:
    Impossibile trovare il file specificato
    ninja: build stopped: subcommand failed.

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

-- Configuring incomplete, errors occurred!
[2/2] "C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" -E chdir "../../x64-windows-dbg" "C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" "C:/Users/PrintedJungle38/Desktop/vcpkg/scripts/get_cmake_vars" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/Users/PrintedJungle38/Desktop/vcpkg/packages/pkgconf_x64-windows/debug" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/vcpkg" "-DZ_VCPKG_ROOT_DIR=C:/Users/PrintedJungle38/Desktop/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Users/PrintedJungle38/Desktop/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DVCPKG_OUTPUT_FILE:PATH=C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/cmake-vars-x64-windows-dbg.cmake.log"
FAILED: ../../x64-windows-dbg/CMakeCache.txt
"C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" -E chdir "../../x64-windows-dbg" "C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe" "C:/Users/PrintedJungle38/Desktop/vcpkg/scripts/get_cmake_vars" "-G" "Ninja" "-DCMAKE_BUILD_TYPE=Debug" "-DCMAKE_INSTALL_PREFIX=C:/Users/PrintedJungle38/Desktop/vcpkg/packages/pkgconf_x64-windows/debug" "-DCMAKE_MAKE_PROGRAM=C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" "-DBUILD_SHARED_LIBS=ON" "-DVCPKG_CHAINLOAD_TOOLCHAIN_FILE=C:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/vcpkg" "-DZ_VCPKG_ROOT_DIR=C:/Users/PrintedJungle38/Desktop/vcpkg" "-D_VCPKG_INSTALLED_DIR=C:/Users/PrintedJungle38/Desktop/vcpkg/installed" "-DVCPKG_MANIFEST_INSTALL=OFF" "-DVCPKG_OUTPUT_FILE:PATH=C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/cmake-vars-x64-windows-dbg.cmake.log"
-- The C compiler identification is MSVC 19.36.32537.0
-- The CXX compiler identification is MSVC 19.36.32537.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/cl.exe
-- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/cl.exe - broken
CMake Error at C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/share/cmake-3.27/Modules/CMakeTestCCompiler.cmake:67 (message):
  The C compiler

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

  is not able to compile a simple test program.

  It fails with the following output:

    Change Dir: 'C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/x64-windows-dbg/CMakeFiles/CMakeScratch/TryCompile-b9ndvx'

    Run Build Command(s): "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v cmTC_fa944
    [1/2] C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\cl.exe  /nologo   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /MP   /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -MDd /showIncludes /FoCMakeFiles\cmTC_fa944.dir\testCCompiler.c.obj /FdCMakeFiles\cmTC_fa944.dir\ /FS -c C:\Users\PrintedJungle38\Desktop\vcpkg\buildtrees\pkgconf\x64-windows-dbg\CMakeFiles\CMakeScratch\TryCompile-b9ndvx\testCCompiler.c
    [2/2] cmd.exe /C "cd . && C:\Users\PrintedJungle38\Desktop\vcpkg\downloads\tools\cmake-3.27.1-windows\cmake-3.27.1-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_fa944.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_fa944.dir\testCCompiler.c.obj  /out:cmTC_fa944.exe /implib:cmTC_fa944.lib /pdb:cmTC_fa944.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_fa944.exe
    cmd.exe /C "cd . && C:\Users\PrintedJungle38\Desktop\vcpkg\downloads\tools\cmake-3.27.1-windows\cmake-3.27.1-windows-i386\bin\cmake.exe -E vs_link_exe --intdir=CMakeFiles\cmTC_fa944.dir --rc=rc --mt=CMAKE_MT-NOTFOUND --manifests  -- C:\PROGRA~1\MICROS~4\2022\COMMUN~1\VC\Tools\MSVC\1436~1.325\bin\Hostx64\x64\link.exe /nologo CMakeFiles\cmTC_fa944.dir\testCCompiler.c.obj  /out:cmTC_fa944.exe /implib:cmTC_fa944.lib /pdb:cmTC_fa944.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 ."
    RC Pass 1: command "rc /fo CMakeFiles\cmTC_fa944.dir/manifest.res CMakeFiles\cmTC_fa944.dir/manifest.rc" failed (exit code 0) with the following output:
    Impossibile trovare il file specificato
    ninja: build stopped: subcommand failed.

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

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

C:\Users\PrintedJungle38\Desktop\vcpkg\buildtrees\pkgconf\get-cmake-vars-x64-windows-rel-CMakeCache.txt.log
# This is the CMakeCache file.
# For build in directory: c:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/x64-windows-rel
# It was generated by CMake: C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-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

//Path to a program.
CMAKE_AR:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/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

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/cl.exe

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/Community/VC/Tools/MSVC/14.36.32532/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=/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=/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:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/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:/Users/PrintedJungle38/Desktop/vcpkg/packages/pkgconf_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/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/link.exe

//make program
CMAKE_MAKE_PROGRAM:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/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=CMAKE_MT-NOTFOUND

//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=get_cmake_vars

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=rc

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.22631

//The CMake toolchain file
CMAKE_TOOLCHAIN_FILE:FILEPATH=C:/Users/PrintedJungle38/Desktop/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

//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:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/vcpkg/installed

//Languages to enables for this project
VCPKG_LANGUAGES:STRING=C;CXX

//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_OUTPUT_FILE:PATH=C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/cmake-vars-x64-windows-rel.cmake.log

//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

//No help, variable specified on the command line.
Z_VCPKG_ROOT_DIR:UNINITIALIZED=C:/Users/PrintedJungle38/Desktop/vcpkg

//The directory which contains the installed libraries for each
// triplet
_VCPKG_INSTALLED_DIR:PATH=C:/Users/PrintedJungle38/Desktop/vcpkg/installed

//No help, variable specified on the command line.
_VCPKG_ROOT_DIR:UNINITIALIZED=C:/Users/PrintedJungle38/Desktop/vcpkg

//Value Computed by CMake
get_cmake_vars_BINARY_DIR:STATIC=C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/x64-windows-rel

//Value Computed by CMake
get_cmake_vars_IS_TOP_LEVEL:STATIC=ON

//Value Computed by CMake
get_cmake_vars_SOURCE_DIR:STATIC=C:/Users/PrintedJungle38/Desktop/vcpkg/scripts/get_cmake_vars

########################
# 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:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/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=27
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/ctest.exe
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//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:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-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:/Users/PrintedJungle38/Desktop/vcpkg/scripts/get_cmake_vars
//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:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/share/cmake-3.27
//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

C:\Users\PrintedJungle38\Desktop\vcpkg\buildtrees\pkgconf\get-cmake-vars-x64-windows-dbg-CMakeCache.txt.log
# This is the CMakeCache file.
# For build in directory: c:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/x64-windows-dbg
# It was generated by CMake: C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-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

//Path to a program.
CMAKE_AR:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/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

//CXX compiler
CMAKE_CXX_COMPILER:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/cl.exe

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/Community/VC/Tools/MSVC/14.36.32532/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=/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=/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:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/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:/Users/PrintedJungle38/Desktop/vcpkg/packages/pkgconf_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/Community/VC/Tools/MSVC/14.36.32532/bin/Hostx64/x64/link.exe

//make program
CMAKE_MAKE_PROGRAM:FILEPATH=C:/Program Files/Microsoft Visual Studio/2022/Community/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=CMAKE_MT-NOTFOUND

//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=get_cmake_vars

//RC compiler
CMAKE_RC_COMPILER:FILEPATH=rc

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.22631

//The CMake toolchain file
CMAKE_TOOLCHAIN_FILE:FILEPATH=C:/Users/PrintedJungle38/Desktop/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

//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:/Users/PrintedJungle38/Desktop/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:/Users/PrintedJungle38/Desktop/vcpkg/installed

//Languages to enables for this project
VCPKG_LANGUAGES:STRING=C;CXX

//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_OUTPUT_FILE:PATH=C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/cmake-vars-x64-windows-dbg.cmake.log

//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

//No help, variable specified on the command line.
Z_VCPKG_ROOT_DIR:UNINITIALIZED=C:/Users/PrintedJungle38/Desktop/vcpkg

//The directory which contains the installed libraries for each
// triplet
_VCPKG_INSTALLED_DIR:PATH=C:/Users/PrintedJungle38/Desktop/vcpkg/installed

//No help, variable specified on the command line.
_VCPKG_ROOT_DIR:UNINITIALIZED=C:/Users/PrintedJungle38/Desktop/vcpkg

//Value Computed by CMake
get_cmake_vars_BINARY_DIR:STATIC=C:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/x64-windows-dbg

//Value Computed by CMake
get_cmake_vars_IS_TOP_LEVEL:STATIC=ON

//Value Computed by CMake
get_cmake_vars_SOURCE_DIR:STATIC=C:/Users/PrintedJungle38/Desktop/vcpkg/scripts/get_cmake_vars

########################
# 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:/Users/PrintedJungle38/Desktop/vcpkg/buildtrees/pkgconf/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=27
//Patch version of cmake used to create the current loaded cache
CMAKE_CACHE_PATCH_VERSION:INTERNAL=1
//Path to CMake executable.
CMAKE_COMMAND:INTERNAL=C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cmake.exe
//Path to cpack program executable.
CMAKE_CPACK_COMMAND:INTERNAL=C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/cpack.exe
//Path to ctest program executable.
CMAKE_CTEST_COMMAND:INTERNAL=C:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/bin/ctest.exe
//ADVANCED property for variable: CMAKE_CXX_COMPILER
CMAKE_CXX_COMPILER-ADVANCED:INTERNAL=1
//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:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-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:/Users/PrintedJungle38/Desktop/vcpkg/scripts/get_cmake_vars
//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:/Users/PrintedJungle38/Desktop/vcpkg/downloads/tools/cmake-3.27.1-windows/cmake-3.27.1-windows-i386/share/cmake-3.27
//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

We hope your question was answered to your satisfaction; if it wasn't, you can reopen with more info.


tags v20240531 and v20240605 seem overloaded

When I run git checkout v20240605, I see that it ends up checking out v20240531 (or at least the same commit: 0fdc793)

This is expected, there are no changes in the AMI template between these two releases; only updated packages (the NVIDIA driver). This is mentioned in the release notes.


Use typographic apostrophe instead of acute accent

(Note: I haven’t tested this, so I’m not quite sure if it works. However, the acute accent is already outside 7-bit ASCII, and it worked, so I think it’s unlikely that the typographic apostrophe will break anything.)

@FroMage comments?

Which is better: let's or let’s? They are both present after the patch, and I'd lean towards the first, since it's easier to type and keep consistent in a text editor, at least on my keyboard.

I’d say let’s, because it’s prettier, recommended by Unicode for this use, and it’s not the 70s anymore ;) but I’m biased since I use a keyboard layout that can type these characters, so they’re not as inconvenient for me as they are for others.

Note: some argue that the English apostrophe should be represented by a different character altogether.

The 70s had it right. Like being able to simply type l instead of having to deal with the invention of the completely frivolous 1 key.

Frankly I find ' less jarring than most of the other options :-)

'

The article about the two apostrophes does have a good point, but I wonder how both options are affected by word breaking? It wouldn’t do do have breaks in the middle of words.

Let’s try it out:

U+0027 APOSTROPHE

aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'aaa'

U+2019 RIGHT SINGLE QUOTATION MARK

aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’aaa’

U+02BC MODIFIER LETTER APOSTROPHE

aaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼaaaʼ

Looks like none of them allow a word break.

@lucaswerkmeister
If I remember from when I read the article (it’s been a while), it talks about how it affects the word break when the apostrophe is at the end or at the beginning of a word (for when double‐clicking, for example). Consider:
There were multiple cars.
U+0027 APOSTROPHE
The cars' windows were broken.
U+2019 RIGHT SINGLE QUOTATION MARK
The cars’ windows were broken.
U+02BC MODIFIER LETTER APOSTROPHE
The carsʼ windows were broken.
Honestly, I think using U+2019 is a little bit puristic, the U+0027 conveys the same meaning. I do use U+2019 because the Unicode Consortium says so, but I’ll admit I’m a bit puristic myself (I’d get bothered if someone said “There was multiple cars.”); I’m the only person I know that goes to the trouble of hitting ctrl+shit+u and then typing “2010” to write a hyphen or “2212” to write a minus sign.

This PR has been closed as a result of moving Ceylon to the Eclipse Foundation, not as a judgement of its value. We are unfortunately unable to restore it ourselves, but if you feel this PR should be reopened, please rebase your work on the current master and create a new PR. Thanks, and sorry for the inconvenience.

So the result of some arguing about which proposed solution is better is that we haven’t merged any solution and still use backticks, which I don’t think anyone has argued for :/
Does anyone care about this enough to pick it up again?


Bugfix/golangci-lint

Fixes a number of linting related issues.

Pull Request Test Coverage Report for Build 238

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 31.034%

Totals

Change from base Build 235:
0.0%

Covered Lines:
216

Relevant Lines:
696

💛  - Coveralls


3.5.4 version not on npm (while 3.4.3, 3.4.5, 3.5.1, etc are there)

As a bit of a follow up to: https://github.com/select2/select2/issues/4040
I'm currently seeing these pre 4. versions on NPM:
3.5.2-browserify
3.5.1-browserify-fix
3.5.1-browserify
3.5.1
3.4.5
3.4.3
While the project I'm currently working on, and would want to manage our dependency on properly, uses 3.5.4
Would it be possible to publish it to NPM to avoid us from keeping it locally (before we upgrade etc - can't afford it now, make breaking changes etc)?
It would help us a lot and would expose the "latest bugfix" of the 3.5 thread via NPM (it would be reasonable given we have 3.5.1 and 3.5.2 there already)

3.x is not supported. I'm sorry that you're still making use of it, but the juice isn't worth the squeeze to get it released on NPM.

I understand, it's just that the migration is not always easy and to the point a bit... 3.5.1 had 30k downloads just last week and all of these people could benefit from releasing what's already there under 3.5.4 - if you'd be able to reconsider I'm sure it would help out at least a bit before/until all of "us" can upgrade.


isSleeping() ARP Check Addition and ffMonitor() Updates For Client Broadcasts

Fixes for issue #631
isSleeping() has been updated to check the PI's ARP table to help determine if a client is sleeping or awake.  This should help clients that inconsistently reply to ICMP ping requests.
ffMonitor() has been re-activated and modified to update a client's state when the client sends a Foreflight heartbeat packet to broadcast.
Logging messages have been added to help troubleshooting.  These messages are controlled via the Verbose Message Logging toggle within the GUI.

Will this affect the client sleep stuff?

@Ergonomicmike  - I do not believe there will be any difference in behavior between this change and the existing code for sleeping clients.  Definitely would appreciate a peer review/testing confirmation of that though.

Just a heads-up, flew about 10 hours these past few weeks and the ADS-B Disconnected messages are still occurring even with this patch, however much less frequently. I would say I have gotten 3 messages in the past 10 flying hours. I have not had time to pull the logs, but will do so and report back.

I wonder how this will do on iOS 11?


Python upgrade

This is for showing @guzijones the chnages I still need to make based on Carlos' changes.


move pages to subscriptions

part of RHCLOUD-25607

The validation hsa failed:
18:00:57 #15 1.238 Validating navigation definitions
18:00:57 #15 1.258 panic: The id subscriptions in /src/chrome-service-backend/static/beta/stage/navigation/subscriptions-navigation.json is not valid because it is duplicated
18:00:57 #15 1.258


yae miko change destruction of kitsune totem on Q to instant

I haven't looked at the Yae implementation much so I'm going to punt this to srl since he's looked at the code more than me.


Remove deprecated Error::description

Error::description has been documented as soft-deprecated since 1.27.0 (17 months ago). It is going to be hard-deprecated soon.
This PR:

Removes an implementation of description in all error types

Related PR: https://github.com/rust-lang/rust/pull/66919

Thanks!


https://go.dev/ref/spec#Constant_declarations

What is the URL of the page with the issue?
https://go.dev/ref/spec#Constant_declarations
What is your user agent?

Screenshot

What did you do?
i think the grammer is error

why this ConstSpec can omit the ExpressionList
What did you expect to see?
What did you see instead?

Read to the end of that section you referenced. ExpressionLists can be omitted. It is particularly helpful with iota.

thank you , but const declaration list the expression list may be omitted from any but the first ConstSpec.The grammer is not reflected.Does it mean that the compiler promise correctness in constant declarations instead of grammar?

Read to the end of that section you referenced. ExpressionLists can be omitted. It is particularly helpful with iota.

thank you , but const declaration list the expression list may be omitted from any but the first ConstSpec.The grammer is not reflected.Does it mean that the compiler promise correctness in constant declarations instead of grammar?

Not everything that can be parsed by the grammar is correct Go code. So yes, the compiler implements additional restrictions.
So something like
const (
    X
    Y
)

Will generate a compile-time error even though it parses just fine.

Thank you for your help, I will study further


Make more transaction fields smaller

Related to https://github.com/oasisprotocol/oasis-wallet-web/pull/2003

Before
After

Fixed in https://github.com/oasisprotocol/oasis-wallet-web/commit/03d11db623478ac54a306d1498217df09647d73e
:/ playwright passing is still not required for auto-merge, I guess from when Transak was failing


Clearer directions for a newbie?

Hi,
I am not seeing any caching behavior. I have set my request's caching policy to NSURLRequestReturnCacheDataElseLoad as well.
Can you update the documentation to make it more clear where we need to alloc init the SDURLCache object? I assume that it's in viewDidLoad or right before an NSURLRequest is made?
Thanks

No, it should be done in appDidFinishLaunching - just once per app.

Thank you so much!


Feature request

received from<EMAIL_ADDRESS>Original Subject : Feature Requests from Metro
Urgency Level : Non-Critical Issue
Support Department : Programming Support
For Application : Peaks
Supplied Message Body :
CAO bumped me today and is very interested in moving forward with PEAKS. I still need it to be a bit more featureful before I can recommend porting our data. Below are some of my requests and some searching for ideas.
Key Imports: should include all fields for People otherwise we're retyping phone numbers, titles, start/end dates, supervisors.
Workstation Imports: would be helpful to be able to import workstation by kerbid. It looks like workstation vs spaces vs keys is interesting. You need to tie a key to a space separately from the import. Makes sense given that spaces looks like it's an import all its own (maybe Facilities link?) and keys may span multiple spaces.
People: While we expect to import data from PEAKS to our own inventory system so our apps have something to work with, the less extra typing we need to do the better. Is it possible to get a PPS/UCPATH Title as well as the working Title field? We might be able to do this as part of our import from PEAKS to our inventory system but we're trying to keep our inventory system, now that PEAKS is being pushed, as minimal data entry as possible.
Roles: We use our people inventory system to populate email lists. Someone in Dept: LAWR, Type: Faculty, Academic Program: Hydrology would wind up on the lawrfaculty and hydfaculty lists. It looks like departments would each be their own Team. So Team: LAWR, Category: Faculty would at least get them into lawrfaculty list. Any chance of custom fields for people like equipment has?
Computer inventory:

I'd talked about a separate "Owner" field rather than just a "User" field. We could likely make due with a report that let us view equipment by Supervisor of the users.
We discussed IP address tracking in Slack. While we use DHCP lightly, we assign static IPs for tracking and because many people need remote access to their systems and a changing IP would be problematic. I could, conceivably, rethink our network setup and do assigned IPs via DHCP and then do the tracking using Infoblox. It would be a step backward in some ways as we'd lose system history. I'm still trying to figure out a way to track IP addresses and use PEAKS. I'm open to ideas.

Default Title in PR #676


the [get_code] button in aistudio.google.com provide a code that doesn't run when grounding is switched on

Description of the bug:
When I switch on the grounding

"""
Install an additional SDK for JSON schema support Google AI Python SDK

$ pip install google.ai.generativelanguage
"""

import os
import time
import google.generativeai as genai
from google.ai.generativelanguage_v1beta.types import content

genai.configure(api_key=os.environ["GEMINI_API_KEY"])

# Create the model
generation_config = {
  "temperature": 1,
  "top_p": 0.95,
  "top_k": 40,
  "max_output_tokens": 8192,
  "response_mime_type": "text/plain",
}

model = genai.GenerativeModel(
  model_name="gemini-2.0-flash-exp",
  generation_config=generation_config,
  system_instruction="You're an expert video parser and extracts the places mentioned in the given videos. You're very helpful and harmless.",
  tools = [
    genai.protos.Tool(
      google_search = genai.protos.Tool.GoogleSearch(),
    ),
  ],
)

Below is the error message I'm receiving

I've installed google-generativeai==0.8.3
I'm using grounding with video input, please help.
Actual vs expected behavior:
I'm using grounding with video input.
While that's running on the ai studio website, the code given in "Get Code" section doesn't work.
Any other information you'd like to share?
No response

Hi @hitchhiker3010, We already have similar issue on this #650
For time being, you can try replacing the code below to make grounding work.
model = genai.GenerativeModel(
  model_name="models/gemini-1.5-pro",
  generation_config=generation_config,
  tools="google_search_retrieval"
)

Thanks

Thank you @Gunand3043 for the reply. Can you please help me with the correct code to get the desired output.
Have gone through the documentation and tried implementing, but I'm getting the following error
InvalidArgument: 400 Search Grounding is supported only for text-only requests


Add api test

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Types: Fix PEP 484 implicit-optional compliance

This was done automatically with hauntsaninja/no_implicit_optional.
This will help avoid bugs such as the one fixed by #1295, since possibly-None values are marked as such by the type annotations.

Really appreciate your recent contributions (e.g. bitsandbytes) thanks a lot @akx !

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Great catch @akx ! Any pointers on how we could test that through a CI workflow?

Ruff can quickly catch simple mistakes (these included).
Mypy and Pyright are more fully-fledged type checkers which take more time and can be annoyingly strict in certain cases.


add possibility to generate the xml report

Yes. What does this module actually produce? I can't see any artifacts in TeamCity.

It's produce only proper output to tell TeamCity about tests. But it doesn't produce any files output, so task it's about.

Thanks for the reply. Could you be a little more specific about what is produced? According to TeamCity I actually need an artifact:
https://confluence.jetbrains.com/display/TCD10/Including+Third-Party+Reports+in+the+Build+Results
And when I use a similar package for Jest (with the similar set up instructions) TeamCity automatically produces a new test tab and tells me how many tests have passed in the overview.

It's strange because I use this reporter and get following:

@HairyMaclary which TeamCity version is used?

@HairyMaclary ping

Hi Sorry about the delay. The TC version is 10.0.4. But I think my problem has been a conflict with the Jest TC reporter. My webdriver tests are actually Spectron tests that are run within Jest. So a big confusing mess. Please don't leave this issue open because of me.


add missing semicolon in c26478.md

@frozenpandaman : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


uninitialized constant Spree::Preferences (NameError)

There is a loading issue after updating to version 2.4.0.
ruby '3.2.0'
gem 'rails', '6.1.6'
gem 'spree', '4.3.2'
gem 'spree_multi_vendor', '2.4.0'
...

$ rails c
/Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/spree_multi_vendor-2.4.0/lib/spree_multi_vendor/configuration.rb:2:in `<module:SpreeMultiVendor>': uninitialized constant Spree::Preferences (NameError)
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/spree_multi_vendor-2.4.0/lib/spree_multi_vendor/configuration.rb:1:in `<main>'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/spree_multi_vendor-2.4.0/lib/spree_multi_vendor/engine.rb:1:in `require_relative'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/spree_multi_vendor-2.4.0/lib/spree_multi_vendor/engine.rb:1:in `<main>'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/spree_multi_vendor-2.4.0/lib/spree_multi_vendor.rb:4:in `<main>'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bundler-2.4.3/lib/bundler/runtime.rb:60:in `block (2 levels) in require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bundler-2.4.3/lib/bundler/runtime.rb:55:in `each'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bundler-2.4.3/lib/bundler/runtime.rb:55:in `block in require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bundler-2.4.3/lib/bundler/runtime.rb:44:in `each'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bundler-2.4.3/lib/bundler/runtime.rb:44:in `require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bundler-2.4.3/lib/bundler.rb:195:in `require'
	from /Users/marocchino/Documents/smv/config/application.rb:7:in `<main>'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/railties-6.1.6/lib/rails/command/actions.rb:22:in `require_application!'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/railties-6.1.6/lib/rails/command/actions.rb:14:in `require_application_and_environment!'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/railties-6.1.6/lib/rails/commands/console/console_command.rb:101:in `perform'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/thor-1.2.1/lib/thor/command.rb:27:in `run'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/railties-6.1.6/lib/rails/command/base.rb:69:in `perform'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/railties-6.1.6/lib/rails/command.rb:48:in `invoke'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/railties-6.1.6/lib/rails/commands.rb:18:in `<main>'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
	from /Users/marocchino/.asdf/installs/ruby/3.2.0/lib/ruby/gems/3.2.0/gems/bootsnap-1.15.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'

This seems to be due to the file location change in spree itself.
https://github.com/spree/spree/blob/v4.3.2/core/app/models/spree/preferences/configuration.rb
https://github.com/spree/spree/blob/v4.5.0/core/lib/spree/core/preferences/configuration.rb
It looks like you need to either upload the minimum required version or condition for 4.3.
related #218

Hi @marocchino - thank you for reporting this. I reviewed the issue and it doesn't even make sense to inherit from Spree::Preference for this, as vendorized models don't make sense to be persisted into the database. I've made some adjustments in this PR and released v2.4.1 It should work fine now, and in case of any problems, please reopen this issue