Closed Nathan-Stohs closed 9 years ago
Are you using the TestSystem? I got this last week while using the TestSystem and informed Chris about it. He checked-in a fix for it - https://github.com/Samraksh/TestSystem/commit/6e992fb643e5f18782e890189b5122737fdda6a8
Are you using the TestSystem? I got this last week while using the TestSystem and informed Chris about it. He checked-in a fix for it - Samraksh/TestSystem@6e992fb
This is in current (EDIT: MF) master for TinyCLR builds. I think its a different although related issue than what you linked.
Are you defining SAM_VERSION_REVISION in your msbuild command line?
Are you defining SAM_VERSION_REVISION in your msbuild command line?
No. Should I be? My command line is always:
msbuild /maxcpucount /p:memory=FLASH,flavor=release /t:cleanbuild TinyCLR.proj
Do you not have this in your own build output? I am very confused if you don't.
No, you shouldn't be. A previous version of the TestSystem had SAM_VERSION_REVISION defined in the msbuild command line but we removed it. What you have is what the TestSystem uses.
No, you shouldn't be. A previous version of the TestSystem had SAM_VERSION_REVISION defined in the msbuild command line but we removed it. What you have is what the TestSystem uses.
So then what's the resolution here?
We need to remove the references from Microsoft.Spot.system.gcc.targets. I could see cases where we have to build a specific version of eMote for a specific platform, so we should keep the version number in the platform area.
builds as of 3b396b3d775b2676e6a40a3896815f5edca6dfed (and earlier) produce numerous instances of:
or another example