-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker support #643
base: sasha_ubuntu
Are you sure you want to change the base?
Docker support #643
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -98,8 +98,12 @@ endif # Matches: ifdef _BSG_MANYCORE_DIR | |
# Undefine the temporary variable to prevent its use | ||
undefine _BSG_MANYCORE_DIR | ||
|
||
# If we're in the docker container, verilator is installed in /usr/bin/verilator | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this because Verilator is installed through a package manager? It is best to use the one provided/compiled by bladerunner for parity. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. No, when building the Docker image it builds Verilator from source and installs it there. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do we have to install it there? Can we just leave it? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would rather be explicit that we're using the one in bladerunner, than install it in /usr/bin and be implicit. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Well the point is to not have the user build Verilator themselves - they just download the image and it'll be preinstalled. We could just not install it and keep the binary in |
||
ifdef BSG_DOCKER | ||
VERILATOR_ROOT = /verilator | ||
VERILATOR = /usr/bin/verilator | ||
# If we're inside bladerunner, check for verilator and define variables | ||
ifneq ("$(wildcard $(BLADERUNNER_ROOT)/verilator/bin/verilator)","") | ||
else ifneq ("$(wildcard $(BLADERUNNER_ROOT)/verilator/bin/verilator)","") | ||
VERILATOR_ROOT = $(BLADERUNNER_ROOT)/verilator | ||
VERILATOR = $(BLADERUNNER_ROOT)/verilator/bin/verilator | ||
else | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -38,7 +38,7 @@ endif | |
|
||
# To switch machines, simply switch the path of BSG_MACHINE_PATH to | ||
# another directory with a Makefile.machine.include file. | ||
BSG_MACHINE_PATH ?= $(BSG_F1_DIR)/machines/baseline_v0_32_16 | ||
BSG_MACHINE_PATH ?= $(BSG_F1_DIR)/machines/4x4_fast_n_fake | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Revert |
||
|
||
# Convert the machine path to an abspath | ||
override BSG_MACHINE_PATH := $(abspath $(BSG_MACHINE_PATH)) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same for RISC-V Tools. I would rather use BSG_MANYCORE as the path, than use /usr/bin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as with Verilator, BSG_MANYCORE lives in the user's filesystem, so this would be a bit difficult. We could again keep the RISCV_BIN_DIR in something like
/riscv_install
or similar.