pkg.cflags from a dependency might be required by dependent packages #267
Comments
|
I think newt's handling of
I understand the issue you raise and I do think it is a real problem. I don't know the best solution though. I'm nervous about having dependent packages inherit cflags from the packages they depend on because I think this could have some unintended consequences. Specifically, the same cflag may do different things to different packages (e.g., We could have a separate field in I feel like there as to be a good solution to the problem, but I can't think of one. Any ideas? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When building mcuboot with RSA, the mbedtls package itself defines and is built with extra cflags (
-DMBEDTLS_USER_CONFIG_FILE=...). While this builds mbedtls correctly other packages that only depend on include files from mbedtls don't seem to import those cflags.My particular case is that I am trying to override mbedtls SW AES implementation with a HW one, in this case I defined
MBEDTLS_AES_ALTand defined what I needed inaes_alt.hfrom my package (just follows mbedtls override method). But for bootutil to not fail building I have to add a similarpkg.cflagsto its package as the one existing in mbedtls.Not sure it's a bug or design decision, or maybe there's a more "correct" way of doing this. I also tried with a few older versions that still work with core
masterbut had the same issues...The text was updated successfully, but these errors were encountered: