Skip to content
This repository has been archived by the owner on Jan 12, 2022. It is now read-only.

VS2012-branch #5

Closed
fkorak opened this issue Mar 4, 2013 · 16 comments
Closed

VS2012-branch #5

fkorak opened this issue Mar 4, 2013 · 16 comments

Comments

@fkorak
Copy link
Contributor

fkorak commented Mar 4, 2013

Hia,

I've been battling with getting the vs-tools to run on Visual Studio 2012. Here is how far I got:

  • The Path for the MSBuild-platform has changed from "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms" to "C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Platforms". I've adapted the path for "VCMessage" in "Microsoft.Cpp.Clang.targets" and "Microsoft.Cpp.Emscripten.targets" to say "Microsoft.Build.CppTasks.Common.v110".
  • I've gotten the "vs-android.Build.CPPTasks.Android"-source from the vs-android-project and have added the new paths to the dependencies to rebuilt the .dll. I've then added the path of my new .dll to GCCCompile, GCCLink and so on.

Sadly I must be missing one of the changes, since I'm still getting "warning MSB8003: Could not find VCInstallDir variable from the registry. TargetFrameworkVersion or PlatformToolset may be set to an invalid version number. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppBuild.targets" as an error.

Maybe significant, the source of my general tries: https://code.google.com/p/vs-android/issues/detail?id=61

Greetings,
Fabian Korak

@SiENcE
Copy link

SiENcE commented May 13, 2013

I have this issues too. Currently no idea how to fix this.

@marc40000
Copy link

The emscripten and mingw part of vs-tool works for me in vs2012 as in vs2010. I followed the install instruction for vs2010 and it just works correctly for vs2012 as well.

I haven't tried the others.

@Maria-Angelova
Copy link

I have the same problem. I only have Visual Studio 2012 (Premium) installed and I don't have either VCInstallDir registry key, nor environment variable. I have the latest nvidia android ndk installed and am using the vs-tool.
I get the this warning: "MSB8003: Could not find VCInstallDir variable from the registry. TargetFrameworkVersion or PlatformToolset may be set to an invalid version number" in
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.CppBuild.targets, which mentions VCInstallDir a couple of times in some error reporting section, so perhaps it assumes there was a previous VS version installed?

@caseymcc
Copy link

caseymcc commented Nov 6, 2014

I forked the project and added support for VS2012. I took the changes needed from vs-android along with a fix for 64bit Python in the linking phase. Can anyone verify if VS2010 and 2013 are functional?

@trippleflux
Copy link

@caseymcc any plan for visual studio 2013 supports?

@caseymcc
Copy link

@trippleflux my changes also include fixes for VS2013. Once Microsoft put out the VS2013 Community version I started using that instead of VS2012 and is seems to work fine. I just committed a change to include an Embind option in the project settings as well.

@Cardinal-DeepSea-Blues
Copy link

@caseymcc I've tried your changes with VS2013 Ultimate with no luck,even the property sheet in the 'Configuration Properties' not showing up. Any clue why its not working?or how can I debug this?

@galek
Copy link

galek commented Apr 9, 2015

9.04.15
I've tried with VS2013 Com-no luck

@caseymcc
Copy link

Was out of town and didn't have a chance to look at it till now. Likely
something todo with the installation as the documented install seems to be
missing a few steps.

You need to take the folders (Clang, Emscripten, MinGW, NaCL) from the
repository and copy them to the MSBuild folder (usually: C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Platforms for VS2013) once there you
need to copy the dll out of the "Emscripten\2013 DLL" into the MSBuild
"Platforms\Emscripten" folder.

Hopefully that will work for you. I will change the documentation in a few
assuming this works for you.

Thanks,
Casey

On Thu, Apr 9, 2015 at 8:53 AM, Nick Galko notifications@github.com wrote:

9.04.15
I've tried with VS2013 Com-no luck


Reply to this email directly or view it on GitHub
#5 (comment).

@galek
Copy link

galek commented Apr 14, 2015

ok,thanks!

@galek
Copy link

galek commented Apr 15, 2015

caseymcc,i can't find "Emscripten\2013 DLL" folder

@caseymcc
Copy link

https://github.com/caseymcc/vs-tool/tree/master/Emscripten/2013%20DLL

its in the source tree as far as I can tell.

On Tue, Apr 14, 2015 at 8:00 PM, Nick Galko notifications@github.com
wrote:

caseymcc,i can't find "Emscripten\2013 DLL" folder


Reply to this email directly or view it on GitHub
#5 (comment).

@galek
Copy link

galek commented Apr 15, 2015

caseymcc,
thanks for reply
i got
"
error MSB8006: The Platform for project '.vcxproj' is invalid. Platform='Emscripten'. This error may also appear if some other project is trying to follow a project-to-project reference to this project, this project has been unloaded or is not included in the solution, and the referencing project does not build using the same or an equivalent Platform. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.InvalidPlatform.Targets 21 7
"

@caseymcc
Copy link

hmm, little hard to debug VS issues.

Things to check,

To enable an existing solution to be built via vs-tool, create a a platform
for it from Configuration Manager -> Active Solution Platform -> New... ->
platform.

Verify you set the Clan and Emscripten environments variables or set path
directories after installing them (I have not used the VS directories only
the environment variables).

  1. Set MINGW_BIN environment variable to point to the bin\ directory
    where the MinGW toolchain executables (gcc.exe et al.) reside in.
  2. Set CLANG_BIN environment variable to point to the directory where
    the Clang toolchain executables (clang.exe and the rest) reside in.
  3. Set EMSCRIPTEN environment variable to point to the emscripten root
    directory (location of emcc.bat et al)

or

  1. Alternatively, in Visual Studio, go to Project Properties ->
    Toolchain Directories

On Tue, Apr 14, 2015 at 10:50 PM, Nick Galko notifications@github.com
wrote:

caseymcc,
thanks for reply
i got
"
error MSB8006: The Platform for project '.vcxproj' is invalid.
Platform='Emscripten'. This error may also appear if some other project is
trying to follow a project-to-project reference to this project, this
project has been unloaded or is not included in the solution, and the
referencing project does not build using the same or an equivalent
Platform. C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.InvalidPlatform.Targets
21 7

"


Reply to this email directly or view it on GitHub
#5 (comment).

@Akiat
Copy link

Akiat commented Jun 12, 2015

Hi Caseymcc and thank you for your work on this plugin.

I need to install it on vs2013, I followed the tutorial for vs2012 but i'm facing this problem:

error MSB4096: The item "core\src\fdrm\crypto\fx_crypt.cpp" in item list "ClCompile" does not define a value for metadata "ProgramDataBaseFileName".  In order to use this metadata, either qualify it by specifying %(ClCompile.ProgramDataBaseFileName), or ensure that all items in this list define a value for this metadata.  C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppBuild.targets

I found this post : http://stackoverflow.com/questions/17681548/clcompile-and-emscripten

But I don't know where I must set the Program Database File Name..

Do you have any idea ?

@fkorak
Copy link
Contributor Author

fkorak commented Dec 5, 2019

Since we are on Visual Studio 2019 now, and this project hasn't seen commits in years, I think this can be closed.

@fkorak fkorak closed this as completed Dec 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants