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

[openimageio] "/utf-8 is required on Windows" error returns with version v3.0.0.3 #42327

Open
crgnam opened this issue Nov 22, 2024 · 0 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@crgnam
Copy link

crgnam commented Nov 22, 2024

Is your feature request related to a problem? Please describe.

When using Visual Studio 2022, if you include headers from OpenImageIO (such as OpenImageIO/imagebuf.h) you get the following compilation error:

C:<foo>\out\build\x64-Release\vcpkg_installed\x64-windows\include\OpenImageIO\detail\fmt\base.h(458): error C2338: static_assert failed: 'Unicode support requires compiling with /utf-8'

This appears to be related to #41405, which was resolved by #41429. However looking at the portfile, the change (adding -DINTERNALIZE_FMT=OFF to the portfile.cmake) is still present in the most recent port for version v3.0.0.3, so I am unsure how related it is.

I do not get the issue when compiling with g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, which I do using the following commands:

mkdir build;
cd build;
cmake ../ -DCMAKE_BUILD_TYPE=Release -DCMAKE_TOOLCHAIN_FILE=<path/to/my/vcpkg>/scripts/buildsystems/vcpkg.cmake
cmake --build .

Proposed solution

Unsure?

Describe alternatives you've considered

Unsure of alternatives (for time being, I am continuing to use a previous version of OpenImageIO, which works without issue)

Additional context

This public repo contains a minimal working example to reproduce the error.

@JonLiu1993 JonLiu1993 self-assigned this Nov 25, 2024
@JonLiu1993 JonLiu1993 added the category:port-bug The issue is with a library, which is something the port should already support label Nov 25, 2024
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

No branches or pull requests

2 participants