-
Notifications
You must be signed in to change notification settings - Fork 991
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
Update _meson_cpu_family_map to support arm64ec #15812
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Hi @crstzh Thanks a lot for the PR. Only one question. Have you checked that you're not getting errors after adding that line? |
Thank you, I will not merge this to the base branch until I verify it locally. |
The easiest is to install the project as editable, check the README in: https://github.com/conan-io/conan
With that you can run the conan application from code Then, to run the tests:
|
Thanks for your help, I followed this and found it does not work. With the change, the conan_meson_cross.ini turns into and it seems good as expected.
But it still reports an error:
Is there any way to make the lib.exe get the option /machine:arm64ec rather than /MACHINE:ARM64 ? I tried like this in my conanfile but it did not take effect.
Thanks for your help. |
Hi @crstzh Thanks for your feedback. Could you please provide the profiles used for the host context |
It would actually be great to reproduce it with the Because it might be something very specific to the |
@memsharded, ======== Input profiles ======== Profile build: |
Quick feedback. The syntax with "ors" like
Are you sure it works? I don't think that is supported at all, so it probably won't do what you intend |
You can ignore that. I am sure it works. |
More update, the error happens in the package(). ERROR: lcms/2.16: Error in package() method, line 102 |
If that is kind of a logical "OR" of package names, I'd say it doesn't work. At least Conan doesn't have any management of it, and up to my knowledge
Can you please try with the |
Yes, I can try that, but it might need some time. Could you just try with the existing package lcms, it's already in cci. For the [tool_requires] section, ======== Input profiles ======== [settings] |
More update:
|
@crstzh Could we check that it's not an error introduced by the 2.1.0 version? Please, let's check a previous version of Conan:
This is only to discard that this could be happening due to some changes introduced in Conan 2.1.0. |
I am trying to reproduce this with the
And it makes sense, the I keep having a look. |
This was expected, I am using this profile:
I think we still need a minimal reproducible example, with full details, like an exact profile we can use to reproduce. Once I forced the |
I cleaned p all local cache and try again: In lcms, I am using meson1.3.1
and error is:
Then I made some changes in conan-io:
the output is:
|
Ok, thanks a lot for the feedback, that clarifies a lot, specifically I was confused about missing your step 2.) With those 2 changes and the following command:
with profile:
Then it works fine and finish correctly:
The only problem I see is the 2 modal dialog with the error of the "sanitycheck", but if I click and dismiss them, the build succeed. Could you please try to reproduce the above, with the same command and the same profile and see if it still fails? |
Without any change, if I run:
But If I run BY the way, I don't know how to set
to
Is that OK? |
But you are still running with a lot of packages and tool-requires that I don't have, so I cannot reproduce the same.
Yes, this would be equivalent |
It succeeed as expected and I can see below putput:
Then I tried below command: got below results:
Seems I need to make some change avoid run test. I did: Then it succeeded.
I am sure my local VS supportARM64EC. Thanks for your help. |
@memsharded Can I merge this to conan-io:develop2 now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, lets merge this then. Thanks very much for your contribution.
It is important to highlight that the Meson integration is not working 100% correctly for this setup yet, I am still getting 2 modal dialog pop ups about sanitycheck.exe
not being able to run for the architecture. But at least these definitions of architecture seems correct and a step in the right direction.
Changelog: Feature: Update
_meson_cpu_family_map
to supportarm64ec
.Docs: Omit
Close #15809
develop
branch, documenting this one.building lcms/2.16 with below command:
It always get below error: