I installed the non-commercial intel Fortran 2018 in Windows 10. According to the starting guide, I should run psxevars.bat. But when I typed 'psxevars' in cmd. It showed 'psxevars command not found'. So I used another way, double clicking it in windows. Then I try ifort in cmd. It doesn't work. It showed 'ifort command not found'. How can I make it work? Btw, I used the cmd in the product group from start menu.
First, make sure Visual Studio (e.g. Visual Studio Community 2015 version) is installed before installing Intel Parallel Studio.
After installing Intel Parallel Studio successfully, a "command line prompt" should be listed at the start menu like this:
There is no need to run psxevars.bat because the installing process has already done this for us.
Another situation might be that we try to use Intel tools in Windows command-line prompt through the cmd command. In this case, we need to run psxevars.bat. And do not forget to specify two arguments, arch and vs, as shown in below.
And notice that it only takes effects in this command-line window, i.e. the same running need to be done for every cmd command-line prompt.
an eternal way is to set the environment variable. Add directories containing Intel tool executables to the "PATH" environment variable, and other related things(libs, include).
On Windows, I recommend using Intel Parallel Studio with the Visual Studio IDE.
Related
I have a fully updated install of Visual Studio Enterprise 2017 (currently 15.9.2) on my machine, and I want to do some Rust coding. The Rust installer tells me to install "Visual C++" build tooling, but I can't seem to figure out which one is needed.
That is, I tried installing "VC++ 2017 version 15.9 v14.16", but when I do cargo run on my hello world application, it halts with a message:
error: linker link.exe not found
I don't want to go rampant and install all the C++ components in the installer, just the one I need. I'd prefer to install it as part of the Visual Studio installer, if possible.
Which "Individual Component" in the Visual Studio installer do I need for Rust?
Here's what's currently checked:
As a workaround, I was advised to run rustup default stable-x86_64-pc-windows-gnu which at least allows me to run the hello world example. (Or perhaps this is in fact a proper solution even?)
Installing any "VC++ toolset" should be enough to get cargo run to link properly. It looks like the minimum dependencies are:
Required dependencies are VC++ 2017 version 15.7 v14.14 latest v141 tools and Windows 10 SDK (10.0.17134.0)
Note that VC does not add its tools to the path (so that you can have multiple versions of the MS toolchain installed in parallel). Instead it adds entries to your Start menu like: "VC++ 2017 version 15.9 v14.16 command prompt" (not sure of the name), that allow you to start a command prompt with the proper path. This should also be possible from a VS toolbar button or menu entry.
You can't start cargo from a generic command prompt, you need to open the prompt with one of the above solutions.
Alternatively, you need to run c:\path\to\your\VS\installation\VCVARS.BAT inside your prompt to set the correct path before running cargo.
I have a weird problem when I want to compile a Visual Studio 2012 solution via msbuild on the command line. Whatever I do, it exits with Specified platform toolset (v110) is not installed or invalid. I have tried launching it via the regular command prompt, the Windows 7 SDK prompt, and all three command prompts included in VS2012. However, compiling in Visual Studio itself works.
where msbuild outputs:
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe
c:\Windows\Microsoft.NET\Framework64\v3.5\MSBuild.exe
You have probably solved the problem yourself but perhaps it may help others with a similar problem. Try to set the VisualStudioVersion environment variable before running MSBuild, e.g
SET VisualStudioVersion=11.0
There is a possibility that it helps.
You could also try passing the command line parameter /p:VisualStudioVersion=11.0 to MSBuild, when trying to build your project. It seems to have the same effect as setting the environment variable, in the above answer.
I want to learn how to use QtWebKit by creating a simple project, but I can't even install it. I found some tutorials like this, but it's for the standard Qt package. I am using for another project the Visual Studio Qt Add-in, so I don't want to uninstall it.
I found some WebKit source code in Qt-VS, but I don't know what to do with it. It does not contain any Perl script so the tutorial above is not good for it, but it does contain some makefiles. Or should I download the QtWebKit package separately, and follow the tutorial above? Will it generate compatible libraries? (I could not find any Qt command prompt, and the tutorial says the VS command prompt must be compatible. How do I know it?) Also, where should I move the binaries generated, so the project made with the built-in Qt template in Visual Studio to be able to find these new files?
Sorry for these lame questions, but I get lost really fast when it comes to building stuff from source and not given in binary form.
I would appreciate any feedback or link to stuff
EDIT:
The only thing I could pull of is to install another copy of Qt, the normal one, and use it for the WebKit project changing the Qt environment variable value each time I'm switching the project, but that would be the lamest thing ever.
Download the Qt 4.7.3 source code:
http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-4.7.3.zip
Unzip and copy to a convenient location.
Open a Visual Studio 2010 command prompt.
You may need to run the command prompt as administrator. To do this, go to Start Menu > All Programs > Microsoft Visual Studio 2010 > Visual Studio Tools, right-click on Visual Studio Command Prompt (2010) and select Run as administrator.
To make a 64-bit build, select Visual Studio x64 Win64 Command Prompt (2010) instead.
Change the working directory to the Qt top folder.
Run the commands:
configure.exe -platform win32-msvc2010
nmake
Wait an hour.
This will build Qt, with all components, including QtWebKit.
Does this answer your question?
user763305's steps will work with these additions:
You need to install Perl. I used "ActiveState Perl"
You need to install WinFlex and WinBison. For some reason the QT script refers to the flex as "win_flex" but tries to find an executable called "bison.exe." I renamed "win_bison" to "bison.exe" and it worked.
I was also able to configure it successfully and build for msvc2012
configure.exe -platform win32-msvc2012
nmake
And it didn't take a few hours on my machine. Just about 55 minutes.
I'm doing an RDP into a machine that has just the CLR installed, and doesn't have Visual Studio on it. Can I somehow load all the Visual Studio-specific environment variables on to the regular command prompt and convert it into the VS command prompt so that I'm able to build my projects via command line?
I looked at the vcvarsall.bat file. That calls the appropriate processor-specific batch file. Couldn't get any inputs from there.
Short of installing all VS, or tracing thru all the various batch files to find out what's getting set, you may be able to simply capture the env vars that are set.
Open up a VS command prompt, and run set > vars.bat
Then open up vars.bat, and put a set command in front of each line.
Not sure how much this will help, since you're going to be missing all the utilities that come with Visual Studio, but it does answer your question.
I don't recommend trying to copy only what you need. You'll need other header files, libraries, dlls, etc... You can instead install VS express edition.
If you are trying to debug a problem you can use remote debugging in Visual Studio or use WinDbg on the computer.
I hav my execuatable produced by command line building.
I want to debug it in command line itself as like as gdb does in linux.
Also i want run my program in Visual studio GUI from command line options..
How can i do that?
Make sure it is compiled in the debug version. Run the program. Then "Attach to Process" from VS tools menu.
You can also specify the runtime options when running the debugger (it's in the project properties).
I don't think that VS has a pure command line mode, but you could use CDB/NTSD.
http://msdn.microsoft.com/en-us/library/cc266320.aspx
It is what lots of developers at MS do.