vtr-verilog-to-routing
vtr-verilog-to-routing copied to clipboard
Published
20 hours ago •
verilog-to-routing
verilog-to-routing
`DESTDIR=/opt/vtr cmake --build ./ --target install` writes content in `/opt/vtr/tmp/vtr/build/*/yosys`
The following procedure: https://github.com/hdl/containers/blob/442f15fd80ee5d2935602880c59b6b8ff2077f22/debian-bullseye/vtr.dockerfile#L47-L52
git clone https://github.com/verilog-to-routing/vtr-verilog-to-routing.git /tmp/vtr
mkdir -p /tmp/vtr/build
cd /tmp/vtr/build
cmake -G "Ninja" -DCMAKE_INSTALL_PREFIX="/usr/local" ..
cmake --build ./
DESTDIR=/opt/vtr cmake --build ./ --target install
Writes content to /opt/vtr/usr/local, which is expected, but also to /opt/vtr/tmp/vtr/build/bin/yosys/ and /opt/vtr/tmp/vtr/build/share/yosys/, which is unexpected. See https://github.com/hdl/containers/actions/runs/4813590487/jobs/8570312480#step:3:6489:
#7 3.937 /opt/vtr
#7 3.937 |-- tmp
#7 3.937 | `-- vtr
#7 3.937 | `-- build
#7 3.937 | |-- bin
#7 3.937 | | |-- yosys
#7 3.937 | | |-- yosys-config
#7 3.937 | | |-- yosys-filterlib
#7 3.937 | | |-- yosys-smtbmc
#7 3.937 | | `-- yosys-witness
#7 3.937 | `-- share
#7 3.937 | `-- yosys
#7 3.937 | |-- abc9_map.v
#7 3.937 | |-- abc9_model.v
#7 3.937 | |-- abc9_unmap.v
#7 3.937 | |-- achronix
#7 3.937 | | `-- speedster22i
#7 3.937 | | |-- cells_map.v
#7 3.937 | | `-- cells_sim.v
#7 3.937 | |-- adff2dff.v
#7 3.937 | |-- anlogic
#7 3.937 | | |-- arith_map.v
#7 3.937 | | |-- brams.txt
#7 3.937 | | |-- brams_map.v
#7 3.937 | | |-- cells_map.v
#7 3.937 | | |-- cells_sim.v
#7 3.937 | | |-- eagle_bb.v
#7 3.937 | | |-- lutrams.txt
#7 3.937 | | `-- lutrams_map.v
#7 3.937 | |-- cells.lib
#7 3.937 | |-- cmp2lcu.v
#7 3.937 | |-- cmp2lut.v
#7 3.937 | |-- coolrunner2
#7 3.937 | | |-- cells_counter_map.v
...
As a result, when a "tarball" generated from /opt/vtr is installed in a different system (container), it overwrites the /tmp, which is unexpected.
