Running on Windows
leoheck opened this issue · 7 comments
Hi @jnavila , there are some users trying to install plotkicadsch on Windows. From your Readme it looks a little bit experimental.
Could you check the output of the installer, here, to give us some directions?
leoheck/kiri#1 (comment)
Here is the same text but formatted.
[ERROR] The compilation of plotkicadsch failed at
"C:\OCaml64\home\Stanley\.opam\4.09.1+mingw64c\bin\dune.exe
build -p plotkicadsch -j 5".
=== ERROR while compiling plotkicadsch.0.8.0 ==
===============================#
context 2.0.8 | win32/x86_64 | ocaml-variants.4.09.1+min
gw64c | pinned(file://C:/Users/Stanley/Desktop/ELEC)
path ~/.opam/4.09.1+mingw64c/.opam-switch/build/plotk
icadsch.0.8.0
command C:\OCaml64\home\Stanley.opam\4.09.1+mingw64c\bi
n\dune.exe build -p plotkicadsch -j 5
exit-code 1
env-file ~/.opam/log/plotkicadsch-21024-42bb52.env
output-file ~/.opam/log/plotkicadsch-21024-42bb52.out
output
File "plotkicadsch/plotkicadsch/src/dune", line 7, characters 6-1
4:
7 | kicadsch
^^^^^^^^
Error: Library "kicadsch" not found.
Hint: try:
dune external-lib-deps --missing -p plotkicadsch -j 5 @installplotgitsch.exe version 0.8.0 is downloadable from the release page: https://github.com/jnavila/plotkicadsch/releases/download/v0.8.0/plotgitsch.exe
Are you trying to compile the master branch? I haven't compiled on windows for a while and it's still a difficult task as I only rely on an external build pipeline.
Did you opam pin add kicadsch . ?
You don't really need to use the opam command. Try make build and get the binary in "_build/default/plotkicadsch/src/plotgitsch.exe`
Did you
opam pin add kicadsch .?You don't really need to use the opam command. Try
make buildand get the binary in "_build/default/plotkicadsch/src/plotgitsch.exe`
Hi there, so I am trying to get this on windows so thanks for your help!
the opam pin add kicadsch . and opam pin add plotkicadsch . worked and now both packages are installed. Going through your tutorial on the user guide I hit another roadblock. I run the following command within the kicad_playground directory and get the following
$plotgitsch
fatal: ambiguous argument 'HEAD^commit': unknown revision or path not in the wor king tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' use compare (ImageMagick) between bitmaps between Git rev HEAD and file system .
If you could lend a hand that would be great!
The argument should be HEAD^{commit}. So the curly braces have been removed... Are you using PowerShell? Curly braces have a special meaning in PowerShell and they are removed when passed to the program.
If you have another shell (bash, cmd.com), could you try with it?
I have tried this with git bash as well as cygdrive (bash and a unix based terminal). this is the following output out of cygdrive
$ plotgitsch schematic/kicad_playground.kicad_pcb
fatal: ambiguous argument 'schematic/kicad_playground.kicad_pcb^commit': unknown
revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
use compare (ImageMagick) between bitmaps between Git rev schematic/kicad_playgr
ound.kicad_pcb and file system .
Git Exception: cannot parse rev schematic/kicad_playground.kicad_pcb
and this is the one out of bash
$ plotgitsch schematic/kicad_playground.kicad_pcb
fatal: ambiguous argument 'schematic/kicad_playground.kicad_pcb^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
use compare (ImageMagick) between bitmaps between Git rev schematic/kicad_playground.kicad_pcb and file system .
Git Exception: cannot parse rev schematic/kicad_playground.kicad_pcb
I'm not sure if this is any help? Seems like the same error.
Hello,
The command is not plotgitsch schematic/kicad_playground.kicad_pcb . This utility compares schematics, not PCB. As stated in the small tutorial, plotgitsch only accepts revisions as parameters. Comparing specific files can only work if you specify a *.sch file with the -f option.