Skip to content

Don't define MODULE_NAME as a string literal #268

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

Merged
merged 1 commit into from
Feb 25, 2024

Conversation

chrisnovakovic
Copy link
Contributor

The MODULE_NAME macro is used in contexts where a string literal is not valid, but the fallback value set in src/common.h defines it as such; this differs from how it is defined in setup.py. Define MODULE_NAME in src/common.h as it is defined in setup.py.

Fixes #267.

The `MODULE_NAME` macro is used in contexts where a string literal is
not valid, but the fallback value set in `src/common.h` defines it as
such; this differs from how it is defined in `setup.py`. Define
`MODULE_NAME` in `src/common.h` as it is defined in `setup.py`.

Fixes xmlsec#267.
@chrisnovakovic
Copy link
Contributor Author

The CI failure seems to be unrelated to this change:

              RuntimeError: The Poetry configuration is invalid:
                - [extras.pipfile_deprecated_finder.2] 'pip-shims<=0.3.4' does not match '^[a-zA-Z-_.0-9]+$'

@bgaifullin bgaifullin merged commit abe56d0 into xmlsec:master Feb 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Compilation failure when building C extension standalone
2 participants