Include compiler version in build hash #1430
Conversation
mosteo
force-pushed
the
feat/hash-compiler
branch
from
81b6a5b
to
fcf11d1
Compare
| @@ -147,6 +147,15 @@ package body Alire.Builds.Hashes is | |||
| -- Configuration variables | |||
| -- TBD | |||
|
|
|||
| -- Compiler version. Changing compiler will result in incompatible | |||
| -- ALI files and produce rebuilds, so it must be part of the hash. | |||
| -- Incidentally, this serves to separate by cross-target too. | |||
There was a problem hiding this comment.
The compiler is able to detect incompatible build artifact, but it's probably better to avoid the error message.
Also note that this will not handle all case for cross-target since a given cross compiler can support multiple instruction sets. For instance arm-elf can do Arm Cortex-M0, Cortex-M7, etc.
There was a problem hiding this comment.
Also note that this will not handle all case for cross-target since a given cross compiler can support multiple instruction sets. For instance
arm-elfcan do Arm Cortex-M0, Cortex-M7, etc.
Right; for those I understood that we're not going to do anything directly, but that the project file will separate the objects into folders?
I guess at some point we can use libgpr to extract the necessary info from the project file?
No description provided.