I manually ran make for the base, logictools, etc for each board in the PYNQ/boards directories. When I ran PYNQ/sdbuild/make BOARDDIR=<my_board_dir> BOARDS=<my_board> it once again had to re-build all the base, logictools, etc for each board. Is there a way to have the build process use all the pre-built overlays from the PYNQ/boards directories ? I assume the PYNQ/sdbuild/build/PYNQ/boards/* are copied from the PYNQ/boards/* directories however they do not copy the pre-built base overlays etc.
Iād recommend you use the fature @patocarr suggested and avoid building the bistreams yourself altogether. I also suggest you to use the prebuilt rootfs so you will save even more time.
To use a board-agnostic image to build a board-specific image you can pass the PREBUILT variable:
make PREBUILT=<image path> BOARDS=<board>
To use a previously built PYNQ source distribution tarball you can pass the PYNQ_SDIST variable. This will also avoid having to rebuild bitstreams (except for external boards) and MicroBlazesā bsps and binaries.
I used the two options mentioned, however it is still trying to re-build the bitstreams
for the boards.
When PYNQ/sdbuild/build/PYNQ/sdbuild/packages/pynq/pre.sh reaches
line 41 overlays=find . -maxdepth 2 -iname 'makefile' -printf '%h\n' | cut -f2 -d"/"
it will not find any overlays since the āmakefilesā are not present in the untarred pynq-2.5.tar.gz
I am sorry, you are totally right! During testing, I happened to use an sdist that had the makefile in it so I introduced this bug. Iāll immediately file a PR to fix it.
In the meantime, I suggest you change the incriminated line with what the PR will look like
Iām not sure if this will affect anyone else but I am using a vmware virtual machine and after patching the overlay line as suggested and restarting the build, I received the following error:
rm -rf base *.jou *.log NA
make[1]: Leaving directory ā/home/user/local/git/PYNQ/sdbuild/build/PYNQ/boards/ZCU104/baseā
cd /home/user/local/git/PYNQ/sdbuild/build/PYNQ
python3 setup.py sdist
Traceback (most recent call last):
File āsetup.pyā, line 34, in
from setuptools import setup, Extension, find_packages, Distribution
ImportError: No module named āsetuptoolsā
So this should not be a problem. Perhaps I am assuming you built the VM before I did the PR to fix the imagebuild (thatās when I added that line in setup_host)