lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Bodewig <>
Subject Re: build script (was Re: [Vote] Apache Lucene.Net 4.8.0-beta00001)
Date Sat, 06 May 2017 15:44:08 GMT
On 2017-05-06, Shad Storhaug wrote:

> I figured as much. In Windows, the command looks like:

> powershell -ExecutionPolicy Bypass -Command "& { Import-Module .\build\psake.psm1;
Invoke-Psake .\build\build.ps1 -properties @{prepareForBuild='false';backup_files='false'}

> where the '.' indicates the current directory. I wasn't sure how to
> specify the current directory on Linux/Mac - is it a '.' as well?

Yes. I could have tried that myself.

Error: 06.05.17 17:36:23: 
At /devel/ASF/lucenenet/build/psake.psm1:193 char:9 +         throw ("Assert: " + $failureMessage)
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [<<==>>] Exception: Assert: No
.NET Framework installation directory found at \Microsoft.NET\Framework64\v4.0.30319\.

If the build requires .NET 4.x them I out of luck. .NET Core and Mono
4.x are installed. I'll try to free up some cycles to debug this myself.

> I know the slashes go the other way, though, and I am pretty sure that both dotnet.exe
and powershell.exe run on Linux.

They do. I've got .NET Core (still 1.1 with project.json instead of XML
project files) and Powershell installed.

> As for the "build" command, I have seen other projects double down by putting both a
"build.bat" (or "build.cmd") and "" launcher files into their build system (have a
look at

I can easily add a that does the same as your .bat - I can also
try to figure out the powershell stuff on my machine myself. I don't
expect to be the first one trying to run Powershell on .NET Core on


View raw message