summaryrefslogtreecommitdiff
path: root/docs/9 - How is a toolchain constructed.txt
diff options
context:
space:
mode:
authorYann E. MORIN" <yann.morin.1998@free.fr>2012-12-27 11:45:22 (GMT)
committerYann E. MORIN" <yann.morin.1998@free.fr>2012-12-27 11:45:22 (GMT)
commitae91413aee0b6901ce5a08b86a9c2207217252eb (patch)
tree6e2a2ddb1b04497001bed3b47a8dacff61050f98 /docs/9 - How is a toolchain constructed.txt
parentd565297b97ee51c8e25325c0a860e3744220c55e (diff)
scripts/addToolsVersion: properly handle .in vs. .in.2
While most components have their version in the .in file, some have it in the .in.2 (eg. elf2flt). Currently, to handle this case, we indiscriminately munge both files, but this is wrong: in the elf2flt case, if we add a binutils version, we do not want it to be added to elf2flt, and conversely. So, for each tool, we need to explicitly know what file to munge. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
Diffstat (limited to 'docs/9 - How is a toolchain constructed.txt')
0 files changed, 0 insertions, 0 deletions