can any one help me width flutter? - windows

that is a visual studio is missing necessary components.
[!] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.5)
X Visual Studio is missing necessary components. Please re-run the Visual Studio installer for the "Desktop
development with C++" workload, and include these components:
MSVC v142 - VS 2019 C++ x64/x86 build tools
- If there are multiple build tool versions available, install the latest
C++ CMake tools for Windows
Windows 10 SDK

like the error description explains, you are missing the VS 2019 C++ build tools. This is only relevant if you want to build and run your flutter project for windows.
You could follow the description on the flutter page for additional windows requirements.
Download and run the Visual Studio 2019 Community Installer.
In the Installer Window, select "Desktop development with C++", the default parameters should be fine, and install it.
After the installation you should restart your computer. Then you should be able to run flutter doctor without any errors.

Related

Flutter Visual Studio - develop for Windows

There is a warning when I use flutter doctor :
Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
What does it mean ? i didnt find the installation component !
It's basically saying that if you want to develop your flutter app for windows
you will need to install Visual Studio 2022 and while installing Visual Studio 2022 you will need to download this: Desktop development with C++
Also you have to install the third link in this: https://visualstudio.microsoft.com/downloads/
You could also get Desktop development with C++ tool after installing visual studio and then navigating to tool -> Get tools and features -> Desktop development with C++

Possible to build Windows drivers using Visual Studio 2019 Build Tools + SDK + WDK without using the EWDK ISO?

We're trying to build some Windows driver (on Windows 10 Enterprise) from within Jenkins. To do that, we were using the Visual Studio 2019 Build Tools, installed the SDK and the WDK as described here: https://learn.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk
Doing that will always result in the following error message:
error MSB8020: The build tools for WindowsKerne
lModeDriver10.0 (Platform Toolset = 'WindowsKernelModeDriver10.0') cannot be found. To build using the WindowsKernelModeDriver10.0 build tools, please install WindowsKerne
lModeDriver10.0 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecti
ng "Retarget solution".
Doing the same on a PC where Visual Studio is installed will work.
The interesting part is:
Using the .iso image linked on the page, where Microsoft claims that it would include the VS2019 build tools + SDK + WDK, works as well.
Now I do not want to use that ISO file, as we already have the Visual Studio build tools installed on our Jenkins machines - for building other C++ software.
Is there any known solution available to just extend an existing build tools 2019 installation to allow building Windows drivers?

install C++ "X64 Compiler and Tools" on Visual Studio 2017

I'm trying to run LevelZap on Windows 10 and the readme states the following:
In order to build all targets, make sure to install the x64 Compiler and Tools
I've gone to Control Panel → Visual Studio Community → Change/Modify but this particular category isn't listed that I can find. A little help please?
Run the "Visual Studio Installer" which is a desktop app (the same thing is launched by the Modify/Change button you hit).
Select "Modify" for your Visual Studio Community 2017 install.
Select the "Individual components" tab.
Under the section Compilers, build tools, and runtimes you can verify you have "VC++ 2017 version 15.x v14.x latest v141 tools" selected. If not, select it and hit Modify.
This component includes booth the x86 and x64 toolsets. Only the ARM and ARM64 toolsets are split out as individual components.
For more on the VS 2017 installer, see this post.
That said, the tool you are using needs to actually supporting finding the toolsets for VS 2017, so the problem way well be in the other software and not your system setup.
Try installing the build tools for Visual Studio 2017 using one of the installers from the website https://visualstudio.microsoft.com/downloads/

TeamCity Visual Studio Build Runner Requirement

We're running TeamCity 9.0.3 and have had Visual Studio 2010, 2012 & 2013 full install on our build server for years now.
I know for a fact that we need certain Visual Studio targets in order to deploy our applications but I'm convinced we don't need to have a full Visual Studio installation in order to use the Visual Studio (sln) build runner but can't find any documentation to say whether or not we do need it.
Can anyone show me documentation or verify from their own experience whether or not a full Visual Studio install is needed for this build runner to work?
Edit: I have seen this question:
Does MSbuild require Visual Studio to be installed on the build server?
And mine is not the same question, it's a different topic. That question is asking whether or not Visual Studio is needed to as a prerequisite for the MSBuild build runner. My question pertains to the Visual Studio build runner
Roughly speaking, by installing Windows SDKs you get what's required to build applications.
Windows 7 SDK
Windows 8.1 SDK
Windows 10 SDK
Multi targeting packs are also required if you use that.
Starting from Visual Studio 2013, you also need to install the separate MSBuild 2013. And MSBuild 2015.
C++ might require you to install other bits.
So you will have to go through lots of trials. Most people simply give up and install full VS.
You don't need full Visual Studio Installed for running the build, all you need are the build tools.
In the "Step" you create to build your solution, the dropdown allows you to select which version of Microsoft builds you want to use where you can specify whether you use MSBuild12 or the latest MSBuild14 for VS2015 projects.
All you have to do is make sure that you install the required Microsoft Build tools in this instance:
Build tools for 2010, 2012 and 2013. The TC build step should then try detecting this install by default in C:/Program Files (x86)/MS Build/Build Tool Number/MSBuild.exe
Note: You will have to restart your agent after you install these tools on the Agent Machine for TeamCity to detect the tools.
The Visual Studio (sln) build runner requires the proper version of Microsoft Visual Studio installed on the build agent.
Reference: https://confluence.jetbrains.com/pages/viewpage.action?pageId=74847254

install VC++ Debug Runtime Distributable

Is there anyway to install or have VC++ Debug Runtime Distributable without installing Visual Studio ?
Just to run a dll that has been compiled in debug mode using VS2013 on another machine that hasn't VS2013.
For testing purposes, you can include the Debug DLLs you need 'side-by-side' with your application. You can find them on a machine with VS 2013 installed:
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\redist\Debug_NonRedist
When you deploy your app, you must use Release mode distributions. For Win32 desktop apps, use these instructions. For Windows Store apps, you don't have to deploy the CRT as it's handled by the Windows Store.
OP was asking about 2013, but the title is general, so..
I just wanted to point out that in newer Visual Studio releases with the "select what you want" installer, for the debug runtime you need just "tools" or "build tools" (e.g. VC++ 2017 version 15.9 v14.16 latest v141 tools or MSVC v142 - VS 2019 C++ Build Tools, not to be confused with the toolset)
As for where you can find the libs, VS 2015 still has them basically in the same path outlined in Chuck's answer. From 2017, you should have something like:
<root>\Microsoft Visual Studio\2017\Community\VC\Redist\MSVC\14.16.27012\debug_nonredist

Resources