-
Notifications
You must be signed in to change notification settings - Fork 222
Build MF v4.4 on clean x64 machine? #270
Comments
The last entry in visixpkg.log says "warning NETMF: Visual Studio 2013 SDK not found VSIX package will not be generated". Maybe I misunderstood that earlier issues resolved this and that VS2013 was no longer required to be installed? Sorry if these are dumb newbie questions. visixpkg.log is:
|
I have been working thru similar problems. Your initial problem is the location of the build tools.zip. The references in the projects for things like CODESIGN.Submitter are SPOROOT\Tools\X86.. Your second point about VS2013 vsix is, if you have VS2013/SDK installed, then a vsix will be generated for vs2013 as well, if it is not installed then this step will be skipped, but you must have vs2015 installed or you will fail the first check in build-sdk |
Directory structure did not come out as clear as I intended in above post - so to clarify |
Thank you! The Build is now running fine! Awesome |
When doing a clean build_sdk, the following warning is raised. Is this a concern?
|
I am closing this issue as the final question is already covered in #257 |
I am failing to build vanilla MF v4.4. Appreciate any suggestions what I might have done incorrectly.
I believe I have followed the initial 6 steps in the Getting Started correctly and have a local copy of netmf-interpreter, CMSIS & build-tools. I have checked the VS2015 setup and have nearly everything installed.
I note that unzipping the "build-tools.zip" into the netmf-interpreter folder adds a x86 folder to tools.
My Virtual machine is running Windows 10 in x64 mode. Do I need x64 versions of the items in x86 folder?
See errors below: Note that CODESIGN.Submitter.dll is in the folder "C:\Projects\BP+\netmf\netmf-interpreter\build-tools.zip\tools\x86\CODESIGN"
What sort of command window should I open to run the build_sdk.cmd? I have tried a few with the same results each time.
I must have something simple wrong in my setup. Appreciate a pointer as to what might be wrong.
When Build_sdk.cmd executes, the following errors are displayed.
The text was updated successfully, but these errors were encountered: