VCVars | Add , Push , or Pop Visual C environment variables | Command Line Interface library

by slurps-mad-rips PowerShell Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | VCVars Summary

VCVars is a PowerShell library typically used in Utilities, Command Line Interface, Visual Studio Code applications. VCVars has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Add, Push, or Pop Visual C++ environment variables to your system PATH

Support

Quality

Security

License

Reuse

Support

VCVars has a low active ecosystem.

It has 18 star(s) with 3 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

VCVars has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of VCVars is current.

Quality

VCVars has 0 bugs and 0 code smells.

Security

VCVars has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

VCVars code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

VCVars is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

VCVars releases are not available. You will need to build from source code and install.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of VCVars

Get all kandi verified functions for this library.

VCVars Key Features

No Key Features are available at this moment for VCVars.

VCVars Examples and Code Snippets

No Code Snippets are available at this moment for VCVars.

Community Discussions

Trending Discussions on VCVars

SCons detects Visual C++ v14.2 (2019) but not v14.1 (2017)

SCons super slow startup in windows

Visual Studio 2017: vcvars for toolset v140

Tcl tclsh Set Up

QUESTION

SCons detects Visual C++ v14.2 (2019) but not v14.1 (2017)

Asked 2020-May-29 at 09:58

I need to build a dependency that uses SCons, and I need to build it with VC++2017, because another dependency I have cannot be built with VC++2019.

SCons successfully detects VC++2019 (v14.2), but not VC++2017 (v14.1):

...

ANSWER

Answered 2020-May-29 at 09:58

Update: This is still (2020-05-26) an issue, and a simple workaround may be https://stackoverflow.com/a/62015647/2279059 - My answer also has a workaround, but it is more complicated and mostly for educational purposes on how recent versions of VC++ compilers can be detected and are (not properly) detected by SCons. You may also want to use my workaround if you are creating a build script for a build server or multiple development machines with varying setups.

The current version of SCons does not support selecting MSVC v14.1 (aka "Visual C++ 2017") if Visual Studio 2019 is installed, but Visual Studio 2017 is not. I confirmed this by looking at the code of SCons (see below).

An alternative approach is to use the --msvc-script option instead of --msvc-version.

In the MSVC installation folder, typically c:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Auxiliary\Build\, you will find a file called vcvarsall.bat. If you run this without arguments, you will see that you can give it arguments for target platform and tools version, e.g.,

Source https://stackoverflow.com/questions/57477926

QUESTION

SCons super slow startup in windows

Asked 2018-Jul-20 at 12:26

I have since long suffered from long startup times when building with SCons. On my old work laptop, it could take up to 60 seconds to just build the most fundamental hello world-example.

I just received a new laptop, so I had the opportunity to investigate this further. Our laptops come preloaded with Visual Studio 2010 and some other stuff. I also need Visual Studio 2015.

On the newly unpacked PC, a build of hello world took "only" 10 seconds (python 2.7.14, scons 3.0.0, no other major applications running)

After installing VS2015, the time went up to 20 seconds.

I can compare this with my 10 year old PC at home, where the same build takes less than 2 seconds (however, only VS2015 there).

What could be the reason for this extreme slowness? Can something be done? It seems like execution of the vcvars scripts and so are responsible. But why so slow on my work computers and not at home? How can I troubleshoot this further?

...

ANSWER

Answered 2018-Jul-20 at 12:26

The solution here, according to the chat, was to disable the Antivirus software running on the machine.

With this, the SCons startup time went from 40 to 2 seconds. Also significant performance improvement in other areas could be noticed.

Source https://stackoverflow.com/questions/50030787

QUESTION

Visual Studio 2017: vcvars for toolset v140

Asked 2018-Jan-26 at 13:54

I installed Visual Studio 2017 and toolsets v140 and v141. To work with v140 toolset, I need to set the necessary environment via vcvars. However, running the necessary vcvars, I get various errors. I am taking vcvars from this directory - C:\Program Files (x86)\Microsoft Visual Studio\Shared\14.0\VC - as I need to initiate the environment for the work with v140 toolset.

If I run vcvarsall, for example, then vcvarsall.bat x86 or vcvarsall.bat x86_amd64 - and I get the following error:

Error in script usage. The correct usage is:

vcvarsall.bat [option] or
vcvarsall.bat [option] store or
vcvarsall.bat [option] [version number] or
vcvarsall.bat [option] store [version number]

where [option] is: x86 | amd64 | arm | x86_amd64 | x86_arm | amd64_x86 | >amd64_arm
where [version number] is either the full Windows 10 SDK version number or "8.1" to use the windows 8.1 SDK

: The store parameter sets environment variables to support store (rather than desktop) development. :

For example:

vcvarsall.bat x86_amd64
vcvarsall.bat x86_arm store
vcvarsall.bat x86_amd64 10.0.10240.0
vcvarsall.bat x86_arm store 10.0.10240.0
vcvarsall.bat x64 8.1
vcvarsall.bat x64 store 8.1 :

Please make sure either Visual Studio or C++ Build SKU is installed.

If I run a specific file vcvars, for example, vcvars32.bat, then I get another error:

ERROR: Cannot determine the location of the VS Common Tools folder.

Has anyone had the same issue, could you help? Thank you.

...

ANSWER

Answered 2017-May-25 at 13:40

I've managed to solve, so to speek, this issue using the following approach. For toolset v140 vcvars tries to obtain the required data from the registry (Visual Studio 14.0 installation directory), but, because it fails to do so, exits with an error. If you add to the Windows registry the required value, vcvars will work correctly. In case of toolset v140 installed along with Visual Studio 2017 this path for the default installation is C:\Program Files (x86)\Microsoft Visual Studio\Shared\14.0\.

You need to locate the existing key where the Visual Studio 2017 installation directory is set (in my case it is HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\SxS\VS7) and add the key with name 14.0 and value C:\Program Files (x86)\Microsoft Visual Studio\Shared\14.0\

Source https://stackoverflow.com/questions/43939301

QUESTION

Tcl tclsh Set Up

Asked 2017-Jul-19 at 08:53

I am just starting out in Tcl and am trying to properly configure an editor and interpreter for use. On Tcl's download page it is recommended to use ActiveState's ActiveTcl, but I am learning Tcl for possible production use and want to avoid paying for it.

I tried setting up Eclipse's DLTK to use for learning, but from what I found I need to direct it to the tclsh executable to use it as the interpreter. In Tcl version 8.6.6, I can't find anything that will work. The supposed formats (I'm on Windows) should follow what's seen here, as I've seen this a few examples/tutorials.

As a last resort, I tried following the Windows instructions here to use my MS Visual Studio 2015 work with this, but there is no such vcvars file (what's asked for when reading makefile.vc after downloading Tcl).

I would really like to use Eclipse for this, so I guess my question is as follows: How do you use tclsh as a Tcl interpreter in Tcl 8.6.6?

...

ANSWER

Answered 2017-Jul-19 at 08:53

ActiveTcl isn't a pay-for product. (ActiveState have some of those, but their language distribution isn't one of them as long as you're not after a support plan.)

To configure Eclipse to use the right installed version of Tcl, go to the Tcl → Interpreters page in the main Preferences panel. That lets you Add… an interpreter, which essentially just requires you to find where the tclsh you want to use is on your filesystem, and to give it a name. I use names like “Tcl 8.6” in my installation, so it isn't exactly rocket science. The DLTK system can find out pretty much everything else once it knows where the interpreter implementation is, but if you have several set up (e.g., I have both 8.5 and 8.6) then you'll need to say which one is default using the checkboxes in the list in the Interpreters pane.
_{_{(I've verified the above against Eclipse Neon running on OSX, but I don't think it will vary very much with other versions or platforms.)}}

Source https://stackoverflow.com/questions/45170599

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install VCVars

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: