This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Fast Models 9.1 and Two Versions of Visual Studio Problem

I have a Windows x86_64 PC. I installed Fast Models 9.1 and Visual Studio 2013 and 2010 (2013 was installed firstly).

I used System Canvas to load an example and built it for VC 2013 configuration. Unfortunately, I got this error.

Launching MSBUILD ("C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe"  /nologo .\Win64-Release-VC2013\FVP_VE_Cortex_A15x1_isim_system_Win64-Release-VC2013.vcxproj /p:Configuration=Release  /p:Platform=x64 )

Build started 2/12/2015 10:54:30 AM.

Project "D:\Win10\ARM\FastModelsPortfolio_9.1\examples\FVP_VE\Build_Cortex-A15x1\Win64-Release-VC2013\FVP_VE_Cortex_A15x1_isim_system_Win64-Release-VC2013.vcxproj" on node 1 (default targets).

C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms\x64\Microsoft.Cpp.x64.Targets(514,5): error MSB8008: Specified platform toolset (v120) is not installed or invalid. Please make sure that a supported PlatformToolset value is selected. [D:\Win10\ARM\FastModelsPortfolio_9.1\examples\FVP_VE\Build_Cortex-A15x1\Win64-Release-VC2013\FVP_VE_Cortex_A15x1_isim_system_Win64-Release-VC2013.vcxproj]

I searched the Internet and found the reason:

Changes In MSBuild with Visual Studio 2013

System Canvas should invoke this MSBuild:

C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe

, not this one:

C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe

Does anyone has a workaround for this problem?

  • There are a couple of workarounds that you could use for this.   The one that I use is to set up the environment variables for the version of visual studio that you plan to use before running System Canvas. 

    for VS2013:     call "C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\vcvarsall.bat" amd64

    for VS2010:     call "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\vcvarsall.bat" amd64

    then run System Canvas.

    Let me know how you get on.

    FYI, we plan to remove the need for this workaround in an upcoming release of Fast Models (v9.3) in Q2.