Export - destination dir should no be root of the project?

This causes an issues, if project is exported to 2 various toolchains.

How to reproduce

# dir
/project
# export
neo export -t target -i IDE
# the exported project is in the root , for instance ./Makefile is here
# make will create build directory
make

# export to another toolchain
neo export -t target -i IDE2
# build now the project for different IDE
# this build can fail

A proposal can be that export dir is not root, could be a directory. And for each IDE, there should be separate directory, so they don’t build into one folder.

The exported dir could look like:

exported/Makefile/
exported/uvision/
exported/iar/

[ghost]

On 12 Apr 2016, at 23:16, Mihail Stoyanov [e-mail] wrote:

Agreed but what are the chances that someone will use multiple toolchains? Think this is similar to someone using more than 2 targets.

Given that we do:

1. Aspire to support multiple toolchains.
2. Already support many targets.

It is not unreasonable to expect that every developer in mbed-os will need convenient support for both multiple toolchains and multiple targets.

Also do you think it’s logical/convenient to have the IDE project files in a subdirectory rather than the root of the project?

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[screamerbg]

Please close this issue when your PR is accepted.