Mbed-cli: separate build subdir for each build profile

Created on 13 Jun 2018  路  5Comments  路  Source: ARMmbed/mbed-cli

Feature/behavior request: make the default build dir for mbed compile a subdir under BUILD/. Name the subdir the same as the name of the build profile file, without extension.

[EDIT: revised paths in table.]

e.g.

| Command | Build Dir |
| ------------------------------------------------------------- | -------------------------------------------------- |
| mbed compile | BUILD/<target>/<toolchain>/develop/ |
| mbed compile --profile debug | BUILD/<target>/<toolchain>/debug/ |
| mbed compile --profile=myprofiles/superoptimized-cpp11.json | BUILD/<target>/<toolchain>/superoptimized-cpp11/ |

This way users can switch between build profiles without having to rebuild everything, and without having to specify custom build dirs.

(Re: the first example, mbed-os/tools/profiles/develop.json is the default build profile, right?)

closed_in_jira enhancement mirrored

Most helpful comment

I think this is similar to the one #615 (might be duplicate)

All 5 comments

I suggest parsing from the build profile filename once it is found on the file system, not from the command line. That way, on a case-insensitive filesystem, e.g. mbed compile --profile debug and mbed compile --profile DEBUG don't create duplicates.

ARM Internal Ref: MBOTRIAGE-679

This way users can switch between build profiles without having to rebuild everything, and without having to specify custom build dirs.

I believe this is how some IDE are handling what they call "targets" (=release/debug + flash/ram).

I think this is similar to the one #615 (might be duplicate)

Closed as dupe of #615.

Was this page helpful?
0 / 5 - 0 ratings