Simplify the build process using git submodules #25
Conversation
…to set up the build environment. Assumes that nextpnr-xilinx and prjxray are submodules.
…ng the PATH is not required.
…irectly from the install location.
…t locations used to run fasm2frames and xc7frames2bit.
… (but easily overridable) cable.
…ts to the correct digilent cable configuration automatically.
…Ds can be supported in a single project directory.
Setup target
|
I suppose if you are calling out a special compiler under Darwin you should also add the recipe for installing that compiler (neither home-brew nor macports have a target called clang) |
| @@ -1,3 +1,6 @@ | |||
| [submodule "nextpnr-xilinx"] | |||
| path = nextpnr-xilinx | |||
| url = git@github.com:kintex-chatter/nextpnr-xilinx.git | |||
| [submodule "prjxray"] | |||
| path = prjxray | |||
| url = git@github.com:kintex-chatter/prjxray.git | |||
There was a problem hiding this comment.
Replace by upstream, i.e. url = git@github.com:f4pga/prjxray.git?
There was a problem hiding this comment.
prjxray in kintex-chatter is ahead of jrrk2:prjxray, which is not aligned with f4pga:prjxray, so I'm hesitant to make this change without comment from the maintainers of the kintex-chatter:prjxray repo.
There was a problem hiding this comment.
Got it. We can move this to a separate issue.
|
Looks good to me and be willing to merge. I propose to handle instructions to install a compiler on Darwin in a separate issue, e.g. #16. |
Yes, my next pull request is to add targets to install all the dependencies on each platform. "brew install llvm" in this case for macOS. |
|
@rwhitby: Thank you for restructuring and sorting! |
With these changes, the build instructions simplify to:
git clone --recurse https://github.com/kintex-chatter/xc7k325t-blinky-nextpnr.git
cd xc7k325t-blinky-nextpnr
make BOARD=qmtech setup
make BOARD=qmtech all
It also works for BOARD=genesys2, and both boards can be built and flashed from the same directory.
I will do a separate pull request with a target to install the prerequisite distribution packages for various platforms.
Why add prjxray as a submodule? The main reason to add prjxray as a submodule is so that XRAY_UTILS_DIR can be automatically set to a default value based on this known relative location for prjxray.
There is a related discussion from 2020 at f4pga/prjxray#1384 that resulted in an independent repo for fasm2frames: https://github.com/SymbiFlow/f4pga-xc-fasm.
@unbtorsten opened an issue for further clarification at chipsalliance/f4pga-xc-fasm#19
Note: this closes #18 and provides a foundation for #21