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

Persist STRICT_APPLE_COMPATIBILITY in objc-config.h #314

Merged
merged 1 commit into from
Nov 19, 2024

Conversation

qmfrederik
Copy link
Collaborator

On Windows, the value of STRICT_APPLE_COMPATIBILITY determines whether BOOL is a char or an int. This value must be consistent across all libraries that use libobjc2. Rather than requiring all libraries to explicitly define STRICT_APPLE_COMPATIBILITY, persist the value of STRICT_APPLE_COMPATIBILITY in objc-config.h and include that in runtime.h.

@davidchisnall
Copy link
Member

Might be good to propagate the other build-time configuration things there.

@qmfrederik
Copy link
Collaborator Author

@davidchisnall Sure, which ones would you like? Some of them have generic names (e.g. LEGACY_COMPAT) so perhaps we should prefix them with OBJC_?

On Windows, the value of `STRICT_APPLE_COMPATIBILITY` determines whether `BOOL` is a char or an int.  This value must be consistent across all libraries that use libobjc2.  Rather than requiring all libraries to explicitly define `STRICT_APPLE_COMPATIBILITY`, persist the value of `STRICT_APPLE_COMPATIBILITY` in `objc-config.h` and include that in `runtime.h`.
@qmfrederik
Copy link
Collaborator Author

qmfrederik commented Nov 19, 2024

I'll merge as is but we can always add more configuration data later.

@qmfrederik qmfrederik merged commit 0c1a893 into gnustep:master Nov 19, 2024
89 checks passed
@qmfrederik qmfrederik deleted the config branch November 19, 2024 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants