Not sure where to begin, I guess I'll put this out there and if more information is needed I'll be asked ;) Here is the relevant (I think anyhow) information:
-
Created a 250GB Windows 7 x64 VM.
-
Fully Windows OS updated.
-
Installed Sublime text editor (more about user-experience QoL than anything)
-
Installed Chrome (I feel vulnerable just browsing the web using IE to download Chrome)
-
Installed Visual Studio 2017 (instructions said 2015 Community or higher -- which is just as well because Microsoft can't seem to get their directory naming structure straight, some versions it's Visual Studio, some versions it's Microsoft Visual Studio, some versions it's in x86 Program Files, other times it's in just regular Program Files... don't even get me started on the Windows SDK lol)
-
Installed Git
-
Downloaded the zip-form (didn't want it screwing with any registry settings or path variables since I knew 3.3 was going to be my target version) binaries for CMake 3.14 (apparently they don't offer binaries for 3.3 anymore -- or maybe they never did?)
-
Downloaded the source for CMake 3.3
-
Set my env. path for system, temporarily, to CMake 3.14's bin directory so I could go into CMake 3.3's directory and run cmake ../ from the directory, that I created in CMake's 3.3 root, called Build.
Success.
- Started Visual Studio 2017, open CMake 3.3's newly generated (thanks to CMake 3.14) project / solution file. Right clicked on ALL_BUILD and clicked build.
Success.
So far so good...
- Installed ActiveState Perl
- Installed Wix toolset for VS 2017
Again, so far so good...
[ctrl]+[esc]
cmd
(right-clicked suggestion and clicked run as administrator)
cd\
git clone http://www.github.com/gnieboer/GNURadio_Windows_Build_Scripts
cd GNURadio_Windows_Build_Scripts
powershell
Set-ExecutionPolicy Unrestricted
Up to this point, everything's good...
Here's where things start to go awry...
./~RUNME_FIRST.ps1
The script starts by asking me the base directory, I accept the default, then immediately after it starts asking me for a BindingVariable. Looking into it, it appears the line (approximately) 308, has issues with the usage of the Import-LocalizedData cmdlet. Looking it up, I find the script seems to be missing -BindingVariable
(https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/import-localizeddata?view=powershell-6)
However, not staying down, I decide to attempt to modify the script and make the line that says:
$Config = Import-LocalizedData -BaseDirectory $mypath -FileName ConfigInfo.psd1
to:
Import-LocalizedData -BindingVariable "Config" -BaseDirectory $mypath -FileName ConfigInfo.psd1
Wonderful. Powershell is no longer yelling at me. Except now it's saying it has a hangup on line (approximately) 411 about not being able to set the Value parameter because it's Null.
Line 411 says:
Set-Alias git (Get-Command "git.exe").Source
Considering I used git to checkout the source for the project in the first place, that error is... interesting. So I ran the Get-Command cmdlet portion manually, and it came back as an empty line... So then I ran it again only this time without the .Source part and it came back with stuff.
Knowing git DOES exist on the system, and seeing that I CAN call it from PowerShell's command line, I decided to rem that and the if check out completely. Only then it started complaining about tar. I then decided to rem out every pre-requisite check. Now PowerShell is complaining about cl not being recognized.
I decide to try upgrading PowerShell to 3.0 thinking maybe these scripts were created using PS3 and the instructions just don't denote that. So I download Windows6.1-KB2506143-x64.msu (Windows Management Framework 3.0) from Microsoft and install that. One reboot later, I then try the process of going into Powershell, setting the execution policy... yadda yadda and re-running ./~RUNME_FIRST.ps1. I still get the cl error.
I chalk this up to not being in the Developer Command Prompt (the Installation & Build instructions do not delineate this). So I go ahead and do just that (that is, run the developer command prompt and run it as admin just to make sure), execute PowerShell, and type cl and hit enter to ensure the Dev prompt's setup carried over into PowerShell. It does. So I rerun ./~RUNME_FIRST.ps1 again, and now it's saying Split-Path : Cannot bind to parameter 'Path' because it is null. line 436 which has a Get-Command usage with the .Source member again.
At this point, I'm thinking I should stop (probably should have long ago) and post this in hopes that maybe I'm doing something wrong or there's an easy fix.