Build directory should not be hidden

[jaustin]

At the moment after completing a build, the binary created lives in the hidden .build directory

This makes it hard for the user to find.

[MarceloSalazar]

Related to this #52

[sg-]

Agreed. build should be a special folder that is ignored by the build system. Exporters need update as well.

[theotherjimmy]

It would be a simple matter of passing the build_dir into scan_resources as an exclude_paths. This would ignore the build directory when scanning for resources, without needing special cases or hacks. Then we could change the default build directory willy-nilly without much fear of breaking anyone's builds.

[andcor02]

Any update on this?

While its clear we can choose another build directory using --build, if we look at the handbook for blinky example there isn't any mention of this. Had people commenting on windows without hidden folders viewed having no clue where their build files are. Viewing hidden folders on mac is even more cumbersome and reports of people thinking CLI is broken.

[sg-]

@theotherjimmy @sarahmarshy Can you update this for exporters and build tools?

[MarceloSalazar]

I have now hit this....
@theotherjimmy @sarahmarshy could you please update the tools and make the build directory visible?

[screamerbg]

It's a bit more complicated than just updating the tools. Will have this scheduled for the next round of changes (~2w)

[sarahmarshy]

Looks like this is the line in question: https://github.com/ARMmbed/mbed-os/blob/master/tools/toolchains/__init__.py#L543

(In addition to the steps that actually put files there).

We should decide on a name to be added to the ignore ('mbed_build'?)

[screamerbg]

Now merged and part of the mbed CLI 0.9.10 release. Please reopen if the issue persists.