corwin-of-amber on v8.12
[doc] Updated README. Misc thi… (compare)
corwin-of-amber on v8.12
[gfx] Icon enhancement. Fav ic… [port] Upgrade to Coq 8.12.1, a… [bugfix] Significant slowdown i… (compare)
corwin-of-amber on v8.12
[bugfix] Avoid static member in… (compare)
dependabot[bot] on npm_and_yarn
corwin-of-amber on v8.12
Bump ini from 1.3.5 to 1.3.8 B… Merge pull request #214 from js… (compare)
npm install
them individually
./etc/toolchain-setup.sh
. See https://github.com/jscoq/jscoq/blob/v8.12/docs/build.md for detailed instructions.
gcc -m32 hello.c
.)gcc-multilib
. Alternatively you can choose the 64-bit route:% ./etc/toolchain-setup.sh --64
OK, I tried 64bit-way. «./etc/toolchain-setup.sh --64» → OK.
But
«««
make jscoq
dune build @jscoq --workspace=/home/stas/projects/blockchain/jscoq//dune-workspace-64
make: execvp: dune: Permission denied
»»»
I see, that it tried to run «./dune», which does not look like executable, but as like DSL for building system.
What else I missed?
toolchain-setup.sh
; perhaps your path is not set up for opam? try eval $(opam env)
the program called dune, which is like GNU make for OCaml (and @ejgallego would add: for everything else too)
Indeed it is a general-purpose build engine, a bit incomparable with make; if you follow the classification from "Build systems à la carte", Dune sits in an interesting spot; once the rule engine is declared stable and people use the API we will see how it works for other use cases; shake has been pretty popular for example.
IIANM most large projects have migrated from make long time ago, indeed make works really bad for one of the use cases Dune was designed for: build of large set of independent packages.
It is a bit of a bore to use during development, since it pulls the source from Github
I was thinking of actually using the image with the dev tools, but before the actual build is, and login into the dev env this way, I'll see.