SSC Build Error

9 posts / 0 new
Last post
brettstone
brettstone's picture
SSC Build Error

I am building the SAM Open Source and ran into an issue in building the SSC solution. Attached is the image of the error message I get.

I tried deleting google test and re-building and releasing it because of the C1083 error code suggesting a file missing in the googletest. I also have tried multiple different folders in the google test as my environment variables.

Do you have any other suggestions?

Thank you,

Brett

ndiorio
ndiorio's picture

Hi Brett,

I believe you are getting the C1083 errors because your environment does not know where google test is installed. Please try:

1. Close Visual Studio (environment variable re-definitions don't get picked up by Visual Studio unless you restart it)
2. Ensure your "GTEST" environment variable points to the folder containing the Google Test "README.md" file. For instance, on my computer, it is: "C:\Projects\googletest\googletest\".
You can set an environment variable in a command prompt by typing: SETX GTEST C:\path\to\googletest\googletest
You can verify your environment variable value by opening up a command prompt and typing: echo %GTEST%
3. Reopen Visual Studio, try and build again.

Please let us know if that doesn't work, hopefully that helps.

Best,
Nick

brettstone
brettstone's picture

Thank you for the reply. This did solve the C1083 error but I am still getting an MSB3073 error code. The MSB3073 still gives the same error output from my picture in the original post.

Any suggestions on how to solve the MSB3073 error?

Thank you for your help.

Brett

brettstone
brettstone's picture

Attached is an image showing the output from the build when the MSB3073 error occurs. It occurs almost immediately once the build initializes.

Hope this helps.

brettstone
brettstone's picture

The image is attached in my original post and is labeled SSC_Build_Error_MSB3073.png

Paul Gilman

Hi Brett,

It looks like there is a problem with the Google Test directory and build. You could try building SSC without the test project by doing a batch build (Choose "Batch Build" from the VS 2017 Build menu) and select all of the projects except the test ones at the bottom.

Best regards,
Paul.

brettstone
brettstone's picture

Hi Paul,

I am still receiving the MSB3073 error when I perform a batch build and do not select the test. This time the MSB3073 occurs at the end and the failed builds are as follows:

(2980):Done building project "ssc_vs2017.vcxproj" -- FAILED.
(3317):Done building project "ssc_vs2017.vcxproj" -- FAILED.
(3356):========== Rebuild All: 14 succeeded, 2 failed, 0 skipped ==========

The MSB3073 error code is the same as the image from my original post. Is there an option for a SAM representative to virtually access my laptop and troubleshoot the issue?

Thank you,

Brett

brettstone
brettstone's picture

Actually the build error is different than my original post the path has changed and now added the WEX path as well as the SSC path.

I have attached another image that shows this error message. The image is titled MSB3073_Error_with_WEX_path. Is there an option for a SAM representative to virtually access my laptop and troubleshoot the issue?

Thank you for your help,

Brett

Paul Gilman

Hi Brett,

The latest error messages are also caused by a "post build event," which is attempting to copy the ssc.dll files to a SAM folder that does not exist. That means that the builds succeeded, it's just the file copy process that failed.

If you are just using SSC without SAM, you can ignore the error. The SDKtool and tcsconsole applications should run.

If you are trying to build the SAM user interface, you will need to clone the SAM repository, and set the SAMNTDIR environment variable to the folder containing the SAM code as described in the SAM build instructions on GitHub:

https://github.com/NREL/SAM/wiki/Windows-Build-Instructions

Best regards,
Paul.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer