-
Notifications
You must be signed in to change notification settings - Fork 0
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
bazel build issue #1
Comments
Hi, thanks for reaching out. I am currently not sure what exactly is happening there. Could you provide all the versions you are using for the build. Furthermore there appears to be a similar Issue on the nvidia forums: https://forums.developer.nvidia.com/t/error-on-build-example/167914 |
Hi! I would suggest that you try to modify the 'WORKSPACE' file in the root folder of this git-repository and change line 32 to the path of the ISAAC SDK that you are using, with the subtle change (since version 2020.2) of adding ./sdk, so in total: Let us know if this worked out for you |
Thank you for your help and time specially given it is an old project. @puck-fzi Here is what I have: $ bazel --version Isaac SDK - 2021.1 @uahic I have tried those suggestions mentioned here --> https://forums.developer.nvidia.com/t/error-on-build-example/167914 I have been using the Isaac SDK 2021.1 since it came out and it is working okay with their examples. Again, your help/comments/suggestions highly appreciated. |
@puck-fzi @uahic |
Thanks for providing us with your system setup. Did you try the approach from the NVIDIA Forums? If yes, did this help or resolve some of the issues? We will have a look into it as well, it might take some time though until we can provide a solution |
@RoboticsIntelligence I adjusted all our Bazel files according to Isaac 2021.1 Currently I am able to compile the main app but not websight (missing shared object files for websight), not sure where the issue there resides at the moment, I need to check more in detail. Beyond compiling the main app I am currently not able to test the migrated code on a real sensor as I need to request it first and it might take a while (home office) Step 1: Adjust the WORKSPACE file again in the main folder, you need to change 2 paths in line 32 and 37, respectively. Please check out the following new branch and let us know if the sensor app runs correctly |
Sorry for the late reply. Good news is that I am able to build the package. I will report back after test run on the live Sick NanoScan3. Thank you for your help. |
I was able to successfully run on the live Sick NanoScan3 the bazel run //packages/sick/apps:sick_safetyscanner_test command. But received the following errors when ran the bazel run //packages/sick/apps:sick_safetyscanner_websight x@alien:~/sick_safetyscanners_isaac$ bazel run //packages/sick/apps:sick_safetyscanner_websight 2021-08-04 11:25:26.046 WARN external/com_nvidia_isaac_engine/engine/alice/backend/backend.cpp@200: This application does not have an execution group configuration. One will be autogenerated to the best of the systems abilities if possible.
|
@RoboticsIntelligence It seems that the shared object for the web-sight module is incorrectly referenced (likely my mistake)
I will come back at you and take a look into this issue |
@uahic Did you find the time to get the issue resolve? |
New with the Isaac and bazel.
Following the direction, after changing the path to "/home/user/isaac-sdk" and to ran the "bazel build" command from the package as instructed, I got the following error:
-----------Error
WARNING: Usage: bazel build .
Invoke
bazel help build
for full description of usage and options.Your request is correct, but requested an empty set of targets. Nothing will be built.
ERROR: no such package '@com_nvidia_isaac//third_party': No WORKSPACE file found in /home/user/.cache/bazel/_bazel_x/df27c2fbab5c087887dcfca680e7380b/external/com_nvidia_isaac
INFO: Elapsed time: 0.059s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded)
Any help would be appreciated.
Thanks.
The text was updated successfully, but these errors were encountered: