You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to compile it using the VS 2019 Preview on Windows 10, and am running into difficulties. For example, when I try to rebuild Hopac.Core I get...
Severity Code Description Project File Line Suppression State
Error MSB3075 The command ""E:\Reactive\Hopac\.paket\paket.exe" restore" exited with code 5. Please verify that you have sufficient rights to run this command. Hopac.Core E:\Reactive\Hopac\.paket\Paket.Restore.targets 81
Running fake.bat fails with some large error. Here it is.
e:\Reactive\Hopac>fake
e:\Reactive\Hopac>SET TOOL_PATH=.fake
e:\Reactive\Hopac>IF NOT EXIST ".fake\fake.exe" (dotnet tool install fake-cli --tool-path ./.fake )
You can invoke the tool using the following command: fake
Tool 'fake-cli' (version '5.20.0') was successfully installed.
e:\Reactive\Hopac>".fake/fake.exe"
Error while parsing command line, usage is:
General:
The Fake command line is divided into runtime and script arguments.
Runtime arguments control compilation and processing of the script,
while script arguments are specific for the script or provided by
a NuGet package.
In most use cases you use the "Fake.Core.Target"-Package and therefore
inherit the corresponding command line interface. While these arguments
are not strictly part of the runtime we still show both below to
make it easier for newcomers.
-- RUNTIME ARGUMENTS SECTION --
Usage:
fake.exe [fake_opts] run [run_opts] [<script.fsx>] [--] [<scriptargs>...]
fake.exe [fake_opts] build [build_opts] [--] [<scriptargs>...]
fake.exe --version
fake.exe --help | -h
Fake Options [fake_opts]:
-v, --verbose [*] Verbose (can be used multiple times)
Is ignored if -s is used.
* -v: Log verbose but only for FAKE
* -vv: Log verbose for Paket as well
-s, --silent Be silent, use this option if you need to pipe your output into another tool or need some additional processing.
Fake Run Options [run_opts]:
-d, --debug Debug the script.
-n, --nocache Disable fake cache for this run.
-p, --partial-restore
Only restore the required group instead of a full restore,
can be set globally by setting the environment variable FAKE_PARTIAL_RESTORE to true.
--fsiargs <fsiargs> [*] Arguments passed to the f# interactive.
Fake Build Options [build_opts]:
-d, --debug Debug the script.
-n, --nocache Disable fake cache for this run.
-p, --partial-restore
Only restore the required group instead of a full restore,
can be set globally by setting the environment variable FAKE_PARTIAL_RESTORE to true.
--fsiargs <fsiargs> [*] Arguments passed to the f# interactive.
-f, --script <script.fsx>
The script to execute (defaults to `build.fsx`).
-- SCRIPT ARGUMENTS SECTION --
THIS SECTION ONLY APPLIES IF YOU USE THE 'Fake.Core.Target' PACKAGE!
You can use the following arguments in place of `<scriptargs>`:
Usage:
fake-run --list
fake-run --write-info <file>
fake-run --version
fake-run --help | -h
fake-run [target_opts] [target <target>] [--] [<targetargs>...]
Target Module Options [target_opts]:
-t, --target <target>
Run the given target (ignored if positional
argument 'target' is given)
-e, --environment-variable <keyval> [*]
Set an environment variable. Use 'key=val'.
Consider using regular arguments, see https://fake.build/core-targets.html
-s, --single-target Run only the specified target.
-p, --parallel <num> Run parallel with the given number of tasks.
Example:
To use verbose mode (from [fake_opts]) and print all
targets use "fake -v build -- --list". Because "--list"
doesn't conflict with any of the [build_opts], you can use
"fake -v build --list"
-> DocoptException: errors Error: Error in Argument 1 ('<>')
Expecting: Command 'build', Command 'run', Flag '--help', Flag '--version' or
ShortFlag '-h'
And I am not sure how to even run the build.fsx. When I tried that, the following error is what I get.
e:\Reactive\Hopac>dotnet fsi
No executable found matching command "dotnet-fsi"
e:\Reactive\Hopac>dotnet fsi build.fsx
No executable found matching command "dotnet-fsi"
Perhaps it is looking for some nonexistent version of FSI because when I try to do the following it works.
e:\Reactive>dotnet fsi
Microsoft (R) F# Interactive version 11.0.0.0 for F# 5.0
Copyright (c) Microsoft Corporation. All Rights Reserved.
For help type #help;;
I did install the .NET Core 2.1.402 that the solution has specified in global.json. I had to just to get the project to open in VS. For reference, here is a list of them.
Most likely, the issue is that it seems to be setup for compilation on Linux, but I am not familiar with F#'s various build tools so I have no idea how to proceed from here. Since the project does not seem active, I'll start by creating a new C# project and adding the files by hand.
That said, I'm not a big fan of how it's set up, since it requires cygwin and is all custom shell scripts. I wouldn't mind merging a PR that has a .sln file pointing to https://github.com/Hopac/Hopac/tree/master/Libs as well as the examples, and then building that without much ado.
mrakgr
changed the title
How to get the build working?
How to get the build working on Windows?
May 19, 2020
I am trying to compile it using the VS 2019 Preview on Windows 10, and am running into difficulties. For example, when I try to rebuild
Hopac.Core
I get...Running
fake.bat
fails with some large error. Here it is.And I am not sure how to even run the
build.fsx
. When I tried that, the following error is what I get.Perhaps it is looking for some nonexistent version of FSI because when I try to do the following it works.
I did install the .NET Core 2.1.402 that the solution has specified in
global.json
. I had to just to get the project to open in VS. For reference, here is a list of them.One more thing, the
git clone
when it is done recursively for submodules has some errors. I deleted theHopac
folder before trying the following.The text was updated successfully, but these errors were encountered: