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

Issue in installing #3

Open
oguzhanmeteozturk opened this issue Feb 10, 2017 · 4 comments
Open

Issue in installing #3

oguzhanmeteozturk opened this issue Feb 10, 2017 · 4 comments

Comments

@oguzhanmeteozturk
Copy link

oguzhanmeteozturk commented Feb 10, 2017

Hey,

This might be a novice question but I'd like to explore your work. I'm trying to follow your installation instructions but I'm getting an error when I try to make the project. I have the latest opencv (with python) and boost libraries installed trough brew on a Mac OS X 10.10.

../stylit/src/utils.h:18:10: fatal error: 
      'cv_utils/cv_utils.h' file not found

Thanks for your support.

Note: CMake is successful

@antoinewdg
Copy link
Owner

Hi, did you by any chance forget to use the --recursive flag when cloning the repo ? cv-utils is a submodule so you need this.

@oguzhanmeteozturk
Copy link
Author

Small permission issue when cloning using the --recursive flag

Please make sure you have the correct access rights and the repository exists. fatal: clone of '[email protected]:antoinewdg/cv-utils.git' into submodule path '/Users/.../stylit/cv-utils' failed Failed to clone 'cv-utils'. Retry scheduled Cloning into '/Users/.../stylit/patch_match'... Permission denied (publickey). fatal: Could not read from remote repository.

Also tried git submodule update --init --recursive after cloning "sylit"

@antoinewdg
Copy link
Owner

This is odd. Can you clone do a regular git clone for the cv-utils repo ? (this would not fix the issue, but may give some insight about where the issue lies)

@antoinewdg
Copy link
Owner

For the record, this is because of this, this could be fixed by changing the .gitmodules files to use the public https urls instead of the current ones, my bad.

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

No branches or pull requests

2 participants