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

opencolorio and openimageio - cycle detected within graph at opencolorio:x64-windows #9851

Closed
ghost opened this issue Jan 30, 2020 · 4 comments · Fixed by #12420
Closed

opencolorio and openimageio - cycle detected within graph at opencolorio:x64-windows #9851

ghost opened this issue Jan 30, 2020 · 4 comments · Fixed by #12420
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@ghost
Copy link

ghost commented Jan 30, 2020

Describe the bug
opencolorio and openimageio - cycle detected within graph at opencolorio:x64-windows

Environment

  • OS: [Windows 10 Pro x64 Version 1909 18363.628]
  • Compiler: VS2017 v15.9.19 VCToolsVersion=14.16.27023
    VS2019 v16.4.3 VCToolsVersion=14.24.28314

To Reproduce
Steps to reproduce the behavior:
1. ->vcpkg install opencolorio[applications,core] openimageio[libraw,opencolorio,ffmpeg,freetype,opencv,gif,openjpeg,webp,tools]

2. See error
Cycle detected within graph at opencolorio:x64-windows:
opencolorio:x64-windows
openimageio:x64-windows

Expected behavior
Should install opencolorio and openimageio with selected features

Failure logs
No logs produced

Additional context
It appears opencolorio package with applications feature depends on openimageio to be installed first, but openimageio with opencolorio feature requires opencolorio to be installed first - another catch-22 scenario where neither can exist without the other being installed first.

@JackBoosY JackBoosY self-assigned this Jan 31, 2020
@JackBoosY JackBoosY added the category:port-bug The issue is with a library, which is something the port should already support label Jan 31, 2020
@JackBoosY
Copy link
Contributor

Hi @timautry, thanks for pointing this out!

@ghost
Copy link
Author

ghost commented Jan 31, 2020

You are most welcome!

@ghost ghost closed this as completed Mar 12, 2020
@JackBoosY
Copy link
Contributor

Please keep this issue open before we resolve it.

@JackBoosY JackBoosY reopened this Mar 16, 2020
@ghost
Copy link
Author

ghost commented Jul 14, 2020

I close, I no longer use product.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant