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

bebop_autonomy not compiling #46

Closed
anuppari opened this Issue Apr 30, 2016 · 2 comments

Comments

Projects
None yet
3 participants
@anuppari
Contributor

anuppari commented Apr 30, 2016

I've tried following the instructions here for building the package on a new computer, but the package does not compile. At some point during the bebop_driver compilation, an xterm window pops up and says

Can't execvp ./build.sh: No such file or directory

Seems like during the process of downloading the ARDroneSDK, the build script doesn't get downloaded. I see that in the CMakeLists of bebop_driver, a certain commit of the arsdk_manifest is pulled, which has a release.xml that links to a certain commit of arsdk_package that has the build.sh in the correct place, but for some reason the file is not pulled down.

The repo sync command spits out a number of 404 Not Found, but at the end says that fetching and syncing were completed 100%, so I'm not sure what the issue is.

@mani-monaj mani-monaj added the bug label May 2, 2016

@mani-monaj

This comment has been minimized.

Show comment
Hide comment
@mani-monaj

mani-monaj May 2, 2016

Member

Thanks for reporting this. I will work on releasing a fix as soon as possible.

Member

mani-monaj commented May 2, 2016

Thanks for reporting this. I will work on releasing a fix as soon as possible.

@grigisf

This comment has been minimized.

Show comment
Hide comment
@grigisf

grigisf May 2, 2016

Here's a work around:

I forked an earlier version of the arsdk (3.8 release) and made the following changes to the CMakeLists.txt file of bebop_driver package:

line 67: COMMAND echo "y" | ./repo init -u https://github.com/grigisf/arsdk_manifests.git
line 70: COMMAND ./build.sh -p arsdk-native -t build-sdk || xterm -e ./build.sh -p arsdk-native -t build-sdk

This way the build is successful (I get a lot of warnings though).

(catkin build fails to build but with catkin build --force-cmake the build is successful)

grigisf commented May 2, 2016

Here's a work around:

I forked an earlier version of the arsdk (3.8 release) and made the following changes to the CMakeLists.txt file of bebop_driver package:

line 67: COMMAND echo "y" | ./repo init -u https://github.com/grigisf/arsdk_manifests.git
line 70: COMMAND ./build.sh -p arsdk-native -t build-sdk || xterm -e ./build.sh -p arsdk-native -t build-sdk

This way the build is successful (I get a lot of warnings though).

(catkin build fails to build but with catkin build --force-cmake the build is successful)

mani-monaj added a commit that referenced this issue May 4, 2016

Fix inline build of arsdk to use the freezed manifest (fixes #46)
- Prior to this release, the build script would always compile the
development branch of ARSDK. This fix ensures that instead of
`default.xml` manifest file - which represents the dev version of ARSDK
package - `release.xml` is used by `repo`. This manifest file includes a
certain hash for each ARSDK package that enforces a consistent build for
ARSDK.

@mani-monaj mani-monaj closed this in c7edd80 May 4, 2016

mani-monaj added a commit that referenced this issue May 4, 2016

Merge pull request #47 from AutonomyLab/46-fix-arsdk-build
Fix inline build of arsdk to use the frozen manifest (fixes #46)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment