You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Building will automatically occur if you use the Makefile, however as these libraries are essential and problems can occur it is perhaps best to build them separately at the start
source yourpath/Xilinx/Vitis/2024.2/settings64.sh
cd src/adi
make
Notice that the way that the ADI libraries are built you will likely find that the initial build will fail because there is an incomplete dependency chain. If this does happen just call make again because the first build will build the library components and the second build will then find the new library components and complete the build.
If after the second attempt at building the ADI libraries there are still problems then look closely at the make output. This is hindered by ADI quiet.mk that avoids creating the excessive log artifacts needed to debug the build attempt. To sidestep the quiet make you can find the failing library component and build that on its own or simple comment out the quiet.mk file in the ADI Makefile:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The HDMI fpga depends upon the ADI libraries. A small set of these has been added to repository to avoid having to update and build all the ADI libraries from https://github.com/analogdevicesinc/hdl.git and matching the selected hdl with the linux drivers in https://github.com/analogdevicesinc/linux.git
Building will automatically occur if you use the Makefile, however as these libraries are essential and problems can occur it is perhaps best to build them separately at the start
Notice that the way that the ADI libraries are built you will likely find that the initial build will fail because there is an incomplete dependency chain. If this does happen just call make again because the first build will build the library components and the second build will then find the new library components and complete the build.
If after the second attempt at building the ADI libraries there are still problems then look closely at the make output. This is hindered by ADI quiet.mk that avoids creating the excessive log artifacts needed to debug the build attempt. To sidestep the quiet make you can find the failing library component and build that on its own or simple comment out the quiet.mk file in the ADI Makefile:
Beta Was this translation helpful? Give feedback.
All reactions