Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
e2 studio exporter update #4959
This change removes legacy e2 studio IDE exporter and updated to inherit from gnuarmeclipse exporter. Only RZ-A1H .cproject template is updated.
The exported project wont build unless Cortex-A support is added to OS 5.5.
This is related to #4624.
This is headed in the right direction. For the best user experience, an exporter:
- Takes input from the resource scan.
- Uses the flags in the build profiles.
- Has a single template file for each file type they produce. For example, an eclipse CDT project would have one template for .project files and one for .cproject files.
- Does not call mbed CLI. It is possible to export from the website, which will not include mbed CLI in the resulting zip.
Looks great! I'm glad you were able to remove the duplication in this exporter. It looks like your .cproject project file template might be the same as the gnuarmeclipse exporter's template. Is that the case? If so, could you just use the gnuarmeclipse one?
I'm working on the MCUXpresso exporter, it uses also the gnuarmeclipse as a base. There is a build method that calls the IDE in 'headless' mode, which means the build process is started without gui. For MCUX, I had to change only the cmd name because its different than 'eclipse'. For e2 it may be also the only modification.
Many thanks for response and info.
I assume CI uses
@theotherjimmy The exported project on CI won't be built because latest CMSIS-RTOS mbed OS 5.5 doesn't support RZ-A1H (Cortex-A). Please let me know the status on this.
@phyokyaw You make a very good point. However, I would still like to make sure that if we enable support in the future, after turning on Cortex-A support, that it will "just work" in the sense that it will test this exporter in CI after that point forward.