sysapi build failure in window: NMAKE: expanded cmdline too long about tpm2-tss

[BenyuXu]

Hi, Jimmy
maybe you could try like below:

1. open a command window,
   

2. subst K: “C:\Program Files (x86)\Microsoft Visual Studio 11.0”,
3. run “k:\VC\bin\vcvars.bat “ ,
4. in computer -> properties -> advanced systerm setting -> environment varibles, add a new value: TSSTOOLS_PATH=K:

FYI

[flihp]

Do we intend to support nmake? Has anyone successfully built this code using nmake before?

[wcarthur1]

For command line builds, I use msbuild from the project’s root dir:

msbuild tss.sln

I think you have to be in a VS 2010 command prompt window OR a command window from which you’ve run the following:
call %TSSTOOLS_PATH%\vc\bin\vcvars32.bat

I don’t know if nmake works—haven’t tried it. I’d suggest msbuild.

Will Arthur
Intel Corporation
Server Security Firmware
803-216-2101

From: Philip Tricca [mailto:[email protected]]
Sent: Thursday, November 12, 2015 9:54 PM
To: 01org/TPM2.0-TSS [email protected]
Subject: Re: [TPM2.0-TSS] sysapi build failure in window: NMAKE: expanded cmdline too long (#64)

Do we intend to support nmake? Has anyone successfully built this code using nmake before?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/64#issuecomment-156307749.

[gwei3]

msbuild tss.sln will report similar error.

the issue is how to build the tpm20lib-tpm project. that project is using nmake to build, isn't it?

[wcarthur1]

I guess I got around this by doing the following:

subst k: c:"Program Files (x86)\Microsoft Visual Studio 11.0"
call k:\vc\bin\vcvars32.bat"
set TSSTOOLS_PATH=k:"\VC\bin"

Will Arthur
Intel Corporation
Server Security Firmware
803-216-2101

From: Gang(Jimmy) Wei [mailto:[email protected]]
Sent: Tuesday, November 24, 2015 3:10 PM
To: 01org/TPM2.0-TSS [email protected]
Cc: Arthur, Will C [email protected]
Subject: Re: [TPM2.0-TSS] sysapi build failure in window: NMAKE: expanded cmdline too long (#64)

msbuild tss.sln will report similar error.

the issue is how to build the tpm20lib-tpm project. that project is using nmake to build, isn't it?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/64#issuecomment-159391066.

[gwei3]

I am using VS2012, and it seems like the TSSTOOLS_PATH variable doesn't impact it at all - I tried.

IMHO, the expanded NMAKE cmdline is now 11446 chars, just reduce tens of chars in the beginning should not make sense for fix it.

Have you ever build the tip in window? and have you ever tried VS2012?

Maybe I should try VS2011 later...

[theopolis]

Maybe a can of worms, but CMake is very nice for support cross-platform builds. You can then generate your Makefile/SLNs/NMake files, etc. ;)

[gwei3]

thanks Teddy, will give it a try when possible.

[flihp]

The build instructions state that VS2010 is the supported VS version and as @gwei3 says he's using VS2012. IMO this issue should be closed as "won't fix". If we'd like to upgrade to a newer version of VS that should probably go into a new ticket. If anyone disagrees with this please feel free to reopen the issue.

[theopolis]

I agree!

(another plug!) If you get CI building for VS you can explicitly choose/test the versions. ;)

I can also add some anecdotal memories from trying VS 15 and having the build bark.