Libraries and old time Mbed

[JohnK1987]

Hello,

I would like to do something with Mbed libraries but is necessary to create a space, so here are few options what i have in my mind.

1. Create a new organization only for libraries called MbedCE-Libraries. It will be separate from MbedCE but that allow let the MbedCE organization only for API examples and not so chaotic.
2. Use this organization (MbedCE) but when you use a repo for each library + example and potential examples for MbedOS APIs then there can be a chaos. Of course it can be solved by add readme to organization main page where we can put a list of libraries and MbedOS dependencies.
3. something else?

Another point is current state of old libraries. For MbedCE it will be around add CmakeLists but harder will be covert the code of all old libraries to MbedOS6+ version without testing because i am not able to buy and test everything.

BTW i did an analyze and i found that most of changes what were done in MbedOS in the past are possible to revert back without break current state.
For example:

• old functions wait(float sec) and wait_(int ms) is possible to take back like a wrapper of thread_sleep_for
• old serial APIs like Serial, RawSerial, UARTSerial seem to be possible to use because SerialBase is still same like in MbedOS 5
• FunctionPointr was raplaced by Callback so there can be ez make a wrapper again
• Probably also TCPServer is still possible to use

Most of these changes break backward use of old libraries. So when we put these all back covered by a macro OLDTIMEBED (enabled via mbed_app.json) then we are able to use old libararies withou any code conversion at this time (can be done in future). Of course for price of old code in source.

What do you think? @multiplemonomials
BR, Jan

[multiplemonomials]

I really like the idea of a separate organization for libraries. I think we need a place for users to find & contribute to libraries that have been updated for Mbed CE! Also that will help keep the Mbed CE github organization clear of clutter. Maybe we should also make a 3rd organization for examples? That way the mbed-ce org will be just the core 4-6 repos.

So when we put these all back covered by a macro OLDTIMEBED (enabled via mbed_app.json)

Hmmm... I don't love that. A lot of those functions were removed for a good reason, like wait() conflicting with OS function names and the old serial classes being literal cancer. So, I would like it to be obvious that the user shouldn't use these for anything but adapting old libraries. What if we made it a separate include file, like

#include <mbed-legacy-shims.h>

that you had to include, and it would implement the old functions using modern Mbed? I think that could work OK. It could exist either as a separate library, or as an optional header in Mbed.

[JohnK1987]

The separate library does have the point because you have to edit library anyway and that not avoid unnecessary questions from low experienced users. But I agree with you we do not go this way.

For examples can be applied different techniques. For example multiple main_xxx.cpp files in one project and select final file of requested example via top lvl CmakeLists.txt
It is good for maintaining because you do not have so many repos also in case when you split examples to diffrent examples. Like one repo for examples around Drivers, one around USB and so on.

./MbedCE_Driver_Examples/
│
├── mbed-os/
├── SPI/
│	├── mabed_app.json
│	└── main.cpp
├── I2C/
│	├── mabed_app.json
│	└── main.cpp
├── PwmOut/
│	├── mabed_app.json
│	└── main.cpp
│
├── cmake-variants.yaml
└── CMakeLists.txt

So may i create new github organization MbedCE-libraries? Or you want do it by your self?
I suppose we can use MbedCE logo with additional label which will contain word 'libraries'.

[multiplemonomials]

That looks right to me, what error are you getting?

[JohnK1987]

Ok, sorry my description was bad. With setup above it is working.
My point was about info on libraries-in-your-application

I had to add the content below for avoiding main.cpp:2:10: fatal error: DHT.h: No such file or directory

#[[ Include .h files]]
target_include_directories(${INTERNAL_LIBRARY_NAME}
    INTERFACE
        .
)

Should I update the wiki about this line?

[multiplemonomials]

Oh yeah, that should probably be in there too.

[JojoS62]

great, the

target_link_libraries(${INTERNAL_LIBRARY_NAME} PUBLIC mbed-core-flags)
was missing in my attempts to use a static lib.

[JohnK1987]

I made 5 repos with already ported libraries - https://github.com/mbed-ce-libraries-examples In few of them I did another modification or correction.

This is still missing

Also we should move this library from the mbed-ce org to the new org: https://github.com/mbed-ce/RemoteIR https://github.com/mbed-ce/RemoteIR-test-program

These libraries are also compatible with MbedOS6 and can be used in Keil Studio Cloud.
Maybe we can share this on forum.