-
Notifications
You must be signed in to change notification settings - Fork 608
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
meson test failure on MSVC #3379
Comments
The option should be available, unless somehow it is using an |
The command being run (minus reported environment variables) is:
I do not have any clue why it would be missing the option, though. :( |
The binary path is relative while the others are absolute, would the current directory by any chance be other than harfbuzz build directory? |
No, because:
|
Hi @eli-schwartz, Can I know what compiler (i.e. Visual Studio version) you are using to build HarfBuzz? For me, it seemed that Visual Studio 2015 silently ate away the options in
Edit: It looks like the code compiled by Visual Studio 2015 called the Let's see whether we have a way to work around this... ugh :| Seems that the compiler mixed up the
with the actual struct type With blessings, and cheers! |
Rename text_option_t in the templatized implementation of main_font_text_t so that we won't confuse between the text_option_t template with the actual struct type that inherits from the actual text_option_t structure, which will fix running on Visual Studio 2015. This will fix harfbuzz#3379.
Rename text_option_t in the templatized implementation of main_font_text_t so that we won't confuse between the text_option_t template with the actual struct type that inherits from the actual text_option_t structure, which will fix running on Visual Studio 2015. This will fix harfbuzz#3379.
Rename text_option_t in the templatized implementation of main_font_text_t so that we won't confuse between the text_option_t template with the actual struct type that inherits from the actual text_option_t structure, which will fix running on Visual Studio 2015. This will fix harfbuzz#3379.
Hi @eli-schwartz, I saw that you are running Visual Studio 2019 Enterprise, sorry for missing that. Can I know what is the exact version of it you were running, since I can't reproduce your issue on my Visual Studio 2019 Community installation (16.11.10). As a test, can you do the following:
Hi @behdad, As a follow up to your points in #3448 on the
caused only the With blessings, thank you! |
I added a copy of that file as a WrapDB overlay, modified it so that both functions begin with Here are the results: https://github.com/mesonbuild/wrapdb/runs/5242709463?check_suite_focus=true#step:7:4932
Whatever the cause of the issue (I know nothing about Visual Studio or its versions) your analysis seems to be correct: that second function is not being called. As for which version of Visual Studio I'm using, I'm using "whatever Github provides in the windows-latest image" and activated by https://github.com/ilammy/msvc-dev-cmd. According to the logs, that is:
plus numerous string references to My assumption is that whatever Github provides in "windows-latest" ought to be new enough that you definitely want to support it. I can only assume it is Visual Studio 2022, not Visual Studio 2015, 2017, or 2019. |
Running locally on Linux I see what you suggested I should see (in addition to passing tests):
|
Hi @eli-schwartz, Thanks for the info... Hmm, interesting, I couldn't reproduce this either with Visual Studio 2022 Community (17.1.0, cl version As another test, can you do the following, after restoring
Thanks a bunch! |
https://github.com/mesonbuild/wrapdb/runs/5242978350?check_suite_focus=true With this patch it passes the tests. (The CI run itself then fails because |
Thanks for the analysis. Fixed. |
In mesonbuild/wrapdb#285, attempting to add harfbuzz to the wrapdb, the following testsuite error occurs on the Visual Studio build, but not on the Ubuntu build.
Apparently it is somehow missing a CLI option altogether and that doesn't trigger a skip?
The text was updated successfully, but these errors were encountered: