Windows Build Instructions Not Working - Missing Steps?

[nat42]

I don't really want to build CoreRT, I just wanted to try a pre-built version of the ILCompiler on a project I am working on, but there doesn't seem to be a pre-built version for download so I tried following the instructions to build.

First issue, compiling on the commandline using build.cmd, the path to the project can not contain spaces; moved project to root of the drive as suggested. Second issue, my system's command interpreter doesn't like the batch files, spitting out errors like -

Could Not Find C:\corert-master\bin\Logs*_Windows_NT__x64__Release.*
Checking pre-requisites...

'&' is not recognized as an internal or external command,
operable program or batch file.
'C:\corert-master\src\Native\probe-win.ps1 is not digitally signed. You cannot run this script on the current system. ' is not recognized as an internal or external command,
operable program or batch file.
'For' is not recognized as an internal or external command,
operable program or batch file.
'http:' is not recognized as an internal or external command,
operable program or batch file.
The AT command has been deprecated. Please use schtasks.exe instead.

Invalid command.

The AT command schedules commands and programs to run on a computer at
a specified time and date. The Schedule service must be running to use
the AT command.
...

That first error pertaining to the ampersand seems to come from the following line, which sets it's own execution policy so my attempts to change the execution policy for the system for the error following it do nothing:

for /f "delims=" %%a in ('powershell -NoProfile -ExecutionPolicy RemoteSigned "& ""%__SourceDir%\Native\probe-win.ps1"""') do %%a

Third issue, so I give up building from the command line and try following the build instructions pertaining to loading a solution in Visual Studio 2015. None of the projects load, all show "(load failed)" after the project names in the Solution Explorer. VS's output pane shows a series of errors like:

The imported project "C:\corert-master\Tools\net45\roslyn\build\Microsoft.Net.Compilers.props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk. C:\corert-master\dir.props

I check and I don't have a Tools directory.

I realise I am probably making some stupid mistakes, but maybe it is valuable to share my failure given building the project seems to be the only way to try the CoreRT tooling for now.

[jkotas]

Could you please share some details about your system? Windows OS version, any unusual configuration settings?

I check and I don't have a Tools directory.

The Visual Studio solutions work only once the repo is built successfully.

[nat42]

Win10 Home 64bit, nothing unusual that comes to mind.... hmm, I'm not especially setup for Dotnet Core builds, just used whatever came with the VS2015 tooling for the project I wanted to try CoreRT on, oh and I chose CMake's recommended option of not adding itself to the PATH environment variable...

And, I did download the project from GitHub as a zip file (lazy) rather than using a git client...

Oh course none of that should explain my system's command interpreter differing apparently from others in it's parsing of the batch file/s... (Oh I should add: I did see the files in question had been split up less than two weeks ago, and tried a version from before this, only to get the same issues)

[jkotas]

I did download the project from GitHub as a zip file (lazy) rather than using a git client...

This is the problem. I am able to reproduce the same error when I download the zip. Windows has some kind of feature that prevents scripts download from internet to be executed.

There was similar issue opened in CoreCLR a while ago https://github.com/dotnet/coreclr/issues/1172. The suggestion was to use -ExecutionPolicy bypass, but the fix was not actually made.

[jkotas]

@nat42 Please give it a try - I have verified that the zip builds fine now.