Skip to content

fix(win): oiiotool --buildinfo misreported platform on MSVS - #5027

Merged
lgritz merged 1 commit into
AcademySoftwareFoundation:mainfrom
lgritz:lg-win
Feb 2, 2026
Merged

fix(win): oiiotool --buildinfo misreported platform on MSVS#5027
lgritz merged 1 commit into
AcademySoftwareFoundation:mainfrom
lgritz:lg-win

Conversation

@lgritz

@lgritz lgritz commented Feb 1, 2026

Copy link
Copy Markdown
Collaborator

Need to test some MSVS-specific macros to determine what architecture to report.

And especially, if it doesn't know the processor architecture, it still should be appending that to the platform, not replacing it! This caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Need to test some MSVS-specific macros to determine what architecture
to report.

And especially, if it doesn't know the processor architecture, it
still should be *appending* that to the platform, not replacing it!
This caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>

@jessey-git jessey-git left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed fixed on my side.

Before: OIIO 3.2.0.0dev | unknown arch?
After: OIIO 3.2.0.0dev | Windows/x86_64

@lgritz
lgritz merged commit e1575d2 into AcademySoftwareFoundation:main Feb 2, 2026
29 checks passed
lgritz added a commit to lgritz/OpenImageIO that referenced this pull request Feb 6, 2026
…ySoftwareFoundation#5027)

Need to test some MSVS-specific macros to determine what architecture to
report.

And especially, if it doesn't know the processor architecture, it still
should be *appending* that to the platform, not replacing it! This
caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>
lgritz added a commit to lgritz/OpenImageIO that referenced this pull request Feb 6, 2026
…ySoftwareFoundation#5027)

Need to test some MSVS-specific macros to determine what architecture to
report.

And especially, if it doesn't know the processor architecture, it still
should be *appending* that to the platform, not replacing it! This
caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>
@lgritz
lgritz deleted the lg-win branch February 7, 2026 06:13
ssh4net pushed a commit to ssh4net/OpenImageIO that referenced this pull request Feb 24, 2026
…ySoftwareFoundation#5027)

Need to test some MSVS-specific macros to determine what architecture to
report.

And especially, if it doesn't know the processor architecture, it still
should be *appending* that to the platform, not replacing it! This
caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>
Signed-off-by: Vlad (Kuzmin) Erium <libalias@gmail.com>
ssh4net pushed a commit to ssh4net/OpenImageIO that referenced this pull request Apr 1, 2026
…ySoftwareFoundation#5027)

Need to test some MSVS-specific macros to determine what architecture to
report.

And especially, if it doesn't know the processor architecture, it still
should be *appending* that to the platform, not replacing it! This
caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>
Signed-off-by: Vlad <shaamaan@gmail.com>
ssh4net pushed a commit to ssh4net/OpenImageIO that referenced this pull request Apr 2, 2026
…ySoftwareFoundation#5027)

Need to test some MSVS-specific macros to determine what architecture to
report.

And especially, if it doesn't know the processor architecture, it still
should be *appending* that to the platform, not replacing it! This
caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>
Signed-off-by: Vlad (Kuzmin) Erium <libalias@gmail.com>
ssh4net pushed a commit to ssh4net/OpenImageIO that referenced this pull request Apr 2, 2026
…ySoftwareFoundation#5027)

Need to test some MSVS-specific macros to determine what architecture to
report.

And especially, if it doesn't know the processor architecture, it still
should be *appending* that to the platform, not replacing it! This
caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>
Signed-off-by: Vlad (Kuzmin) Erium <libalias@gmail.com>
ssh4net pushed a commit to ssh4net/OpenImageIO that referenced this pull request Apr 2, 2026
…ySoftwareFoundation#5027)

Need to test some MSVS-specific macros to determine what architecture to
report.

And especially, if it doesn't know the processor architecture, it still
should be *appending* that to the platform, not replacing it! This
caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>
Signed-off-by: Vlad (Kuzmin) Erium <libalias@gmail.com>
Signed-off-by: Vlad <shaamaan@gmail.com>
ssh4net pushed a commit to ssh4net/OpenImageIO that referenced this pull request Apr 2, 2026
…ySoftwareFoundation#5027)

Need to test some MSVS-specific macros to determine what architecture to
report.

And especially, if it doesn't know the processor architecture, it still
should be *appending* that to the platform, not replacing it! This
caused MSVS-compiled OIIO on Windows to report "unknown arch?"

Signed-off-by: Larry Gritz <lg@larrygritz.com>
Signed-off-by: Vlad (Kuzmin) Erium <libalias@gmail.com>
Signed-off-by: Vlad <shaamaan@gmail.com>
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

Successfully merging this pull request may close these issues.

2 participants