ivankravets
commented
9 years ago If a library can be used for more platforms than specified, how do we react? We can either create an issue with the repository of the library owner or create a pull-request.
We shouldn't react. library.json owns to developer, not to us. He decides which platforms/frameworks are compatible with that library. What we can do, that to create script which test (using examples) all arduino-based libs for teensy, timsp430 and titiva platforms. Then, generate updated library configs. However, I'm not sire that we should spend this time now. mbed has more higher priority, because it is more interesting for community.
If two libraries exist with the same name but for different platforms, does the library manager know which library to use depending on the platform?
I got you. PlatformIO Library Dependency Finder scans just includes and doesn't analyse that information. However, I've just opened an issue for it https://github.com/platformio/platformio/issues/148.
Thanks a lot for idea!
I am currently looking into the teensy platform that is supported by arduinoteensy. Most arduino libraries should work out of the box, even with the arm based teensy3 board. Needless to say, none of the libs I use with PlatformIO list the teensy platform. Luckily, it still works, but that got me thinking: Which consequences does/should this specification have? If a library can be used for more platforms than specified, how do we react? We can either create an issue with the repository of the library owner or create a pull-request.
If two libraries exist with the same name but for different platforms, does the library manager know which library to use depending on the platform?
Maybe this discussion really belongs to plaformio repository