-
Notifications
You must be signed in to change notification settings - Fork 61
Build script dependency problem #38
Comments
I'm also having this problem under Ubuntu 17.04, with the same error: |
related? |
@thomasjm You can use the Dockerfile created by @3Dcube. You can find it here https://github.com/3Dcube/docker-jupyter-icsharp I just tried it and it works and I see that is using the same solution mentioned in the travis issue pointed by @denfromufa. |
Travis-ci has hid their issues. What's the solution? |
i am also facing the same issue in Mac, while trying to build in terminal with following command (base) $ bash ./build.sh brew mozroots --import --sync --quiet |
I'm building it on Windows 10, but today I got the same error. There is a solution for this problem:
Go the Re the second |
There seems to be a problem with building ICSharp from scratch in a Docker container, using Ubuntu 16.04.
I've been doing it like this:
However, this fails when running
Engine/build.sh
with the following error:The ScriptCS submodule comes with a
.nuget/NuGet.exe
at version2.8.60318.667
, which is kind of old. In the past, I've worked around the problem by runningbash -c "cd Engine; mono ./.nuget/NuGet.exe update -self
to update to a newer version of NuGet, which for some reason resolved the problem. However, the latest version of NuGet (4.3.0
ish) is now so new that it fails with a different error, saying "the assembly name is invalid" forScriptCs.sln
-- it doesn't seem able to parse the file anymore.I'm able to get things to work by picking a medium-old
NuGet.exe
version--I inserted this line into my Dockerfile to use version3.3.0
:Anyway, long story short: something is weird and fragile about NuGet.exe/package dependencies in the current version of ICSharp.
The text was updated successfully, but these errors were encountered: