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
@mvgianel, I have seen many issues when cross compiling QT applications on x86 machine. Can you please try to compile the same on your Kria board directly. KRS does support your application compilation on board.
@jasvinderkhurana thank you for your reply. I have compiled the application on the KV260, and it works correctly. The issue is that I would like to make an accelerator for the package, and I understood that I couldn't do that on the KV260 since it will require Vitis. That is the reason why I am trying to cross-compile to create the binaries and accelerator to run on the board. Is there another way I should be doing this?
In that case you are right, if you want to build any accelerator you must use the cross compilation flow on x86 machine. Is there any way that you can decouple your accelerator from QT5? Or you may try hacks that you can copy the built files on KV260 to your x86 machine and then try to resolve all QT5 dependencies.
I am encountering the same error as the one explained here: #94. I am using Ubuntu 22, but working with the KV260 board -firmware https://github.com/ros-acceleration/acceleration_firmware_kv260/releases/download/v1.1.1/acceleration_firmware_kv260.zip- and I am trying to compile the slam_toolbox package (https://github.com/SteveMacenski/slam_toolbox.git).
![Screenshot from 2023-10-11 14-57-24](https://private-user-images.githubusercontent.com/23347523/276030524-7b9aa2a7-4a4d-44e3-9f12-9e21ea68bf65.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNDgzODQsIm5iZiI6MTcyNjE0ODA4NCwicGF0aCI6Ii8yMzM0NzUyMy8yNzYwMzA1MjQtN2I5YWEyYTctNGE0ZC00NGUzLTlmMTItOWUyMWVhNjhiZjY1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA5MTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwOTEyVDEzMzQ0NFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTU0YWIwMTNmNzkyMmNhMThjM2I5ZWQzMTlhN2QzNWY0ZTA3NDA3ZTFlMzgyMzc4Mjk0OThlYzRkZDdlNjRmN2EmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.ngCLj2SOe91bRhBKpssK7Nxv2HmWS6lWXLoVSzbhlTk)
However, after trying the accepted solution of the previously mentioned issue I still got the same error.
The text was updated successfully, but these errors were encountered: