Closed gabrielhdt closed 1 year ago
There seem to be a recurring malfunction: paths are (always?) prepended with ./, even when they should not. For instance, assume we have three files,
./
D/unit.dk
Unit: Type. unit: Unit.
D/unitLib.dk
#REQUIRE unit. id : unit.Unit -> unit.Unit.
foo.dk
#REQUIRE unit. #REQUIRE unitLib. def bar := unitLib.id unit.unit.
dk dep
Dependency computation returns a not-so-correct output:
$ cd D $ dk dep *.dk ./unit.dko : unit.dk ./unitLib.dko : unitLib.dk ./unit.dko
With these dependencies, make unitLib.dko just does not work (I assume it's because unitLib.dko is not the same as ./unitLib.dko for make).
make unitLib.dko
unitLib.dko
./unitLib.dko
dk check
Assuming D/unit.dko and D/unitLib.dko have been created, the command
D/unit.dko
D/unitLib.dko
$ dk check -I D/ foo.dk [SUCCESS] foo.dk was successfully checked.
works, but
$ dk check -I "$(realpath D)" foo.dk [ERROR CODE:902] ... No object file (.dko) found for module unit located at .//[...]/D/unit.dko
There seem to be a recurring malfunction: paths are (always?) prepended with
./
, even when they should not. For instance, assume we have three files,D/unit.dk
D/unitLib.dk
foo.dk
Symptom 1:
dk dep
Dependency computation returns a not-so-correct output:
With these dependencies,
make unitLib.dko
just does not work (I assume it's becauseunitLib.dko
is not the same as./unitLib.dko
for make).Symptom 2:
dk check
Assuming
D/unit.dko
andD/unitLib.dko
have been created, the commandworks, but