You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in a couple of issues (see #311 and #279 in particular), much of the MBED-OS core code is stored in a static library. This is convenient in general, but it also makes it more difficult to perform core MBED-OS changes (enabling some flags, tweaking build etc).
My question is: would it be possible to add a "raw MBED-OS core" option to the board variants, in which case the core MBED-OS is recompiled against the code at a known location, so that users can just tweak things without the need to figure out the build process and link process by hand each time?
The text was updated successfully, but these errors were encountered:
I'll look into this. We originally dismissed this idea because of the very large compile time that would come with this kind of solution. However, if it were simply an option or an advanced feature it could make more sense. I will look into including it as a supplemental solution.
I will file this away as a potential enhancement and note it fore the future. Don't expect movement on this right away, I am focusing on bug fixes right now.
An 'expert feature' for doing that would be amazing :) . No hurry, no worries! :) Let me you if / when you have something in place so that I can give it a try.
As discussed in a couple of issues (see #311 and #279 in particular), much of the MBED-OS core code is stored in a static library. This is convenient in general, but it also makes it more difficult to perform core MBED-OS changes (enabling some flags, tweaking build etc).
My question is: would it be possible to add a "raw MBED-OS core" option to the board variants, in which case the core MBED-OS is recompiled against the code at a known location, so that users can just tweak things without the need to figure out the build process and link process by hand each time?
The text was updated successfully, but these errors were encountered: