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

Provide own flavor of special directive for new projects #46

Open
boris-kolpackov opened this issue Sep 4, 2022 · 0 comments
Open

Provide own flavor of special directive for new projects #46

boris-kolpackov opened this issue Sep 4, 2022 · 0 comments

Comments

@boris-kolpackov
Copy link
Member

It's possible that new projects will want to use this module, which brings the "what flavor to use" questions. Autoconf seems the most natural but the problem with Autoconf's #undef is that it prevents having genuine #undef directives, for example, if we need to tweak some auto-defined macros. We could use either #cmakedefine or #mesondefine but them having a different build system hardcoded in their makes the idea feel inelegant.

So perhaps we should provide our own flavor and a special directive (#autodefine)? We could also switch to the strict substitution mode in this flavor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant