-
Notifications
You must be signed in to change notification settings - Fork 444
Expose 'ocamlc -config' parameter 'ox' #12236
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Jon Ludlam <[email protected]>
Signed-off-by: Jon Ludlam <[email protected]>
For reference, do you have the corresponding PR that introduced this change? |
We already have the |
|
This seems a bit more robust to me than matching the version number to 'jst' or 'ox', and fitted in nicely with the other ocaml-config variables. I think there's a reasonable argument to expose the rest of the values provided by (I should probably also mention that the |
I agree. Why don't we change the implementation of oxcaml_supported then as well?
That would be welcome as well. |
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.
I agree that the goal was to have this to replace the +ox
lookup functions. We should update these functions to also check for the ocaml_config
. This way we would make oxcaml_supported
use it.
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.
My suggestion would be for the test cases to be in the test-cases/oxcaml
repository as it is related to it.
@jonludlam do you mind adding a CHANGES entry? |
This is to allow for easy access to whether a compiler is an oxcaml one or not.
I initially exposed this as the parameter 'ocaml-config:oxcaml' but then decided to stick precisely with what the output of
ocamlc -config
gives. This makes it hard to change the name of that value, so it's worth confirming this constraint is OK with the oxcaml devs.