[Expoters] Export broken after reorganization

[sarahmarshy]

Description

• Type: Bug
• Priority: Major

---

Bug

meed-os sha:
765fbbb Merge pull request #2842 from svastm/sw4stm32_use_targets_json

Actual behavior
Import errors. Resolving those, name errors. Resolving that, linking errors at build time.
mbed export -m k64f -i gcc_arm
1.

  File "C:\Repos\mbed-os-example-blinky\mbed-os\tools\project.py", line 13, in <module>
    from tools.paths import EXPORT_DIR, MBED_DRIVERS, MBED_PLATFORM, \
ImportError: cannot import name MBED_BASE

Resolving (1) brings:
2.

    _, toolchain_name = get_exporter_toolchain(options.ide)
NameError: global name 'get_exporter_toolchain' is not defined

Trying to run python tools/test/export/build_test.py instead of mbed export (which the following file is unrelated and unused in that script):

 File "C:\Repos\mbed-os-example-blinky\mbed-os\tools\export\sw4stm32.py", line 21, in <module>
    from targets import Target

Resolving that..
All uvision builds fail at the linking stage for all targets like so:

.\build\uvision5\basic.axf: Error: L6218E: Undefined symbol setUp (referred from unity.o).
.\build\uvision5\basic.axf: Error: L6218E: Undefined symbol tearDown (referred from unity.o).

Steps to reproduce
Use mbed export command

@theotherjimmy @0xc0170 @screamerbg @sg-

[0xc0170]

The referenced sha did not break it but reorganization ? Because that SHA above is not related to the changed structure. It's not clear

Import errors. Resolving those, name errors. Resolving that, linking errors at build time.

Can you paste some error so others can reproduce and fix (or they might see different errors) ?

[sarahmarshy]

I am just posting the SHA on top of my local mbed-os. Not the SHA of the culprit. Sorry, was in the middle of pasting the errors. They are above now.

[theotherjimmy]

We got this resolved.