Build fails about netmf-interpreter HOT 20 CLOSED

Can you post the complete log file? That warning is normal and expected, it's an .NET Framework BUILD warning that indicates it can't find the libraries for the specified framework which of course it can't find because you are in the process of building them. Unfortunately we haven't found a way to disable that particular warning short of cloning and modifying the standard .NET MS build targets files (Not a good idea).

from netmf-interpreter.

Sure. Here is the link to the file on my OneDrive (a max. of ~26K characters allowed here):

https://onedrive.live.com/redir?resid=e11170f8ecc6005c!27816&authkey=!AJkbSi7NMYUDImw&ithint=file%2ctxt

from netmf-interpreter.

I have written a blog-post a while ago, how to compile 4.3 and what the requirements are:

http://www.awsomedevsigner.com/2015/01/04/successful-compilation-of-the-netmf-4-3-rtm-codeplex-version/

Maybe this helps. Looks like its missing also the WiX assemblies and some dependencies mentioned in my blog-post.

from netmf-interpreter.

Did you install the Bin and TOOLS from the pre-requisites ZIP file? Based on your log file those should be expanded to D:\gitsource\bin and D:\gitsource\tools

That's where the WIX libraries are "installed" We are planning to change the build to use a normal installation point for all of the required binaries, as well as include pre-build testing to report helpful error messages regarding any thing that isn't found.

from netmf-interpreter.

Yes, I did. But not in within the directories you mentioned. Let me try that.

from netmf-interpreter.

ok, assuming that works if you have a suggestion on how to explain that better I can update the readme. (I did it with a bit more detail in the wiki, perhaps I should update the readme to just point to the WIKI)

from netmf-interpreter.

I think it works now (compiling). Thanks ;) A good explanation could be something like:

1. Create a directory like netmf-build-root (or something like that and refer to it as "netmf build root folder")
2. Checkout the source within that directory
3. Download the zip with the tools and copy both folders into the "netmf build root folder"

And then point the user to the Wiki for details. Or It could be done using a PowerShell script or a usual installer to install everything that is needed, execute git, unzip the folders, open a command prompt and such. OR simply and Azure-VM that could be used to setup a ready-to-go VM :)

from netmf-interpreter.

Ok, here is the build-log after putting the tools into the right directory. Still does not complete, but looks much better:

https://onedrive.live.com/redir?resid=e11170f8ecc6005c!27817&authkey=!AHPaxWoragbMIQs&ithint=file%2ctxt

from netmf-interpreter.

What the.... 😕 You wouldn't perchance have setup the Roslyn compiler as your compiler for VS2013 would you?

from netmf-interpreter.

I don't think so. I had the Roslyn Preview installed long time ago, the Roslyn SDK Project Templates and the Roslyn Syntax vizualizer. All disabled in VS.

from netmf-interpreter.

Might be a bug in their setup where it's still using the compiler. Can you uninstall it? The number of compiler warnings etc.. on code that builds on multiple installations for us and has nothing to do with any dependencies hints at something funny going on with the compiler...

from netmf-interpreter.

Yes. Will do that now. Just a second.

from netmf-interpreter.

Even after removing it, it uses:

Microsoft\VisualStudio\12.0\Extensions\ce0qbks5.bng\rcsc.exe /noconfig

within Visual Studio.

Will check that and let you know about the solution.

from netmf-interpreter.

Ok. After the extensions (Roslyn) are uninstalled and the machine rebooted, the tools copied into the right directories, The build will complete. Here is the build log:

https://onedrive.live.com/redir?resid=e11170f8ecc6005c!27818&authkey=!AH1aRfv4-2AXKUc&ithint=file%2ctxt

I will check this log further, to see if there are other issues with my system. Thanks for your patience. Changing the directory name AFTER a build and then trying to rebuild is also not a good idea. Fixed that as well on my machine. See only green and yellow now :)

from netmf-interpreter.

looks good. You should see the MSI and VSIX packages in the build output folder. (Which reminds me I should probably add that little detail to the getting started guide 😃 )

from netmf-interpreter.

Yepp, here you go

:) And a good idea to describe the output folder a bit.

from netmf-interpreter.

To suppress MSB3644: The reference assemblies for framework ".NETMicroFramework,Version=vX.Y" were not found warnings, create FrameworkList.xml in "C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework.NETMicroFramework\vX.Y\RedistList" with the following content:

<FileList Name=".NET Micro Framework X.Y.0.0" Redist="Microsoft-Windows-CLRCoreComp-MicroFramework-X.Y.0.0" ToolsVersion="4.0"/>

Where X.Y is the desired version.

Edit: Fixed the directory path.

from netmf-interpreter.

Hi! @cw2 Thanks for the hint :) Will do that as soon as I am at home. Currently at work.

from netmf-interpreter.

Did you see my guide about building the vNext from sources here? It might be helpful. It worked for Codeplex sources, but I didn't test it with current github sources.

from netmf-interpreter.

@Savvkin Thanks for the link :) +1 and sharing it on Twitter :) Never to late to learn something.

from netmf-interpreter.