LPC824: export to LPCXpresso does not include TOOLCHAIN files

[JojoS62]

Description

• Type: Bug

---

Bug

Target
LPC824, LPCXpresso824-MAX

Toolchain:
GCC_CR

Toolchain version:
Online Compiler Export

meed-os sha:
mbed lib 127

Actual behavior

• directory 'TOOLCHAIN_GCC_CR' is missing in exported archive

Steps to reproduce
create mbed_blinky for target LPCXpresso824-MAX, export to LPCXpresso

[JojoS62]

This issue applies only to the online compiler.
The exporter in mbed-os works:
python project.py -m LPC824 -i lpcxpresso -n MBED_BLINKY

Only the size of the compiled binary is too large and the nano libs must be used. Is there an option for this?

[JojoS62]

I'm still struggeling with the exporters.
python project.py -m LPC824 -i lpcxpresso -n MBED_BLINKY
does not work in the current master branch. It creates a project but the TOOLCHAIN dir is still missing. Also the mbed sources should be created in a 'mbed' folder which does not exist.
Trying other toolchains I get the following error:

D:\Projects\Sn\LocalGit\mbed-os\tools>python project.py -m LPC1768 -n MBED_BLINKY -i gcc_arm
Scan: blinky
Scan: env
Scan: hal
Traceback (most recent call last):
  File "project.py", line 234, in <module>
    main()
  File "project.py", line 230, in main
    zip_proj=zip_proj, build_profile=profile)
  File "project.py", line 93, in export
    build_profile=build_profile, silent=silent)
  File "D:\Projects\Sn\LocalGit\mbed-os\tools\project_api.py", line 229, in export_project
    macros=macros)
  File "D:\Projects\Sn\LocalGit\mbed-os\tools\project_api.py", line 90, in generate_project_files
    exporter.generate()
  File "D:\Projects\Sn\LocalGit\mbed-os\tools\export\makefile\__init__.py", line 80, in generate
    ctx[key] = ctx['vpath'][0] + "/" + ctx[key]
TypeError: cannot concatenate 'str' and 'NoneType' objects

[JojoS62]

@theotherjimmy
I think I've got it now. The outdated docs/building.md is misleading. As far as I understand now the mbed-os/tools are now not intended for stand-alone usage. Instead the command should be invoked via mbed (mbed-cli install necessary). That is different from the older mbed-master behaviour.
If this is right, I suggest to throw an error if the tools are not inoked via mbed to avoid this confusion.