Skip to content
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

Bootstrap with offline version? #105

Closed
traversaro opened this issue Nov 25, 2016 · 7 comments · Fixed by #402
Closed

Bootstrap with offline version? #105

traversaro opened this issue Nov 25, 2016 · 7 comments · Fixed by #402

Comments

@traversaro
Copy link
Member

traversaro commented Nov 25, 2016

The bootstrap feature is quite cool, but it renders any superbuild vulnerable to any shortage of any 3rd party repo referenced by YCM (see #103).
Could it make sense to bootstrap using the offline version of YCM ?

@drdanz
Copy link
Member

drdanz commented Nov 25, 2016

I need to think about this... The idea of the bootstrap phase is that together with the other repositories you can manage also YCM git repository.

On the other hand it makes sense to not make it break in case some repository is not reachable or changes location...

@traversaro
Copy link
Member Author

traversaro commented Feb 1, 2017

Related: #113 (even if in this case it was caused by a Gitlab downtime).

@traversaro
Copy link
Member Author

To anyone having the same problem: use the offline version of ycm available at https://github.com/robotology/ycm/releases .

@traversaro
Copy link
Member Author

Related issue: #172 .

@traversaro
Copy link
Member Author

I think the final solution of this will be #138 using the ycm-<ver>-offline.tar.gz tarball.

@drdanz
Copy link
Member

drdanz commented Mar 27, 2019

Starting from the next release, along with the -offline version that should be used for packaging, I will add a YCM-<ver>-all.tar.gz file that will contain the "binary" release, that can probably be used with FetchContent

@PeterBowman
Copy link
Member

PeterBowman commented May 5, 2019

The bootstrap feature is quite cool, but it renders any superbuild vulnerable to any shortage of any 3rd party repo referenced by YCM

This is particularly annoying since the 3rd-party UseLatex.cmake module was introduced in YCM v0.10. I managed to reproduce and inspect this error locally - the downloaded file is either incomplete or empty. Note that we don't bootstrap YCM itself, this happens on a cloned YCM repository, during the build phase.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants