-
Notifications
You must be signed in to change notification settings - Fork 932
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
Circular submodule dependency causes recursive clones or submodule updates to fail #301
Comments
To build EASTL as part of a CMake project, you also need to include most of the packages now, and also run a submodule update on them:
This is only somewhat related, but I hope it helps someone not waste as much time as I have on this. |
Some context, the change was introduced because we broke out our internal library dependencies into separate repos. So we can manage them seperate to EASTL in addition to having our unit tests running for the respective packages. I'm happy to add a comment in the readme.md. Please let me know if you have suggestions on how this could be implemented better. |
I'd just like to know what the correct workflow is. Am I supposed to manually run |
We don't use these repositories internally git and cmake are used only for the open source versions of the technologies. This gets you everything you need:
I'll add this to the docs. |
Yea, this was annoying |
Trying to use either of the following:
Results in an infinite loop:
Workaround for cloning:
Workaround for adding EASTL as submodule:
The
--recursive
option is used and recommended by practically everyone, as far as I can tell, so this is likely to trip a few people up. If you can't or won't fix this issue, you might want to consider placing a note about it in the README.The text was updated successfully, but these errors were encountered: