Package versioning

zgoda · May 27, 2016, 2:26pm

Is there any place I can check upstream version that corresponds to specific package version?

Eg. framework-mbed is currently listed at version “13” but this is not the upstream version (currently 120, in PIO I guess is 117), and same for framework-arduinoavr which is listed as “30” but Arduino is currently at 1.6.9, installed version.txt in PIO reads 10608 and is described as 1.6 in package.json. Not to say this is confusing.

sstaub · May 27, 2016, 6:04pm

+1, this will help us to know on which ‘real’ version we work.

ivankravets · May 27, 2016, 7:03pm

I propose to forget about PlatformIO 2.0. We are working on the PlatformIO 3.0 and new decentralized architecture for development platforms. All platforms related code has been moved to separate repositories. You will be able to clone/modify or create own development platform in a few steps.

Now, each development platform defines own requirements, contains own build scripts, LD scripts, examples and etc. See:

Related GitHub issue from PlatformIO 3.0 roadmap:

github.com/platformio/platformio-core

"platform.json" manifest for development platform

opened 01:00PM - 27 Jan 16 UTC

closed 02:37PM - 11 Jun 16 UTC

ivankravets

feature

# Aims We are very happy that PlatformIO community is growing up extremely fast…. The last weeks have brought us a lot of requests to add new board or platform https://github.com/platformio/platformio/issues. This forces us to refactor PlatformIO 3.0 development platforms logic from the scratch. The main aim is to allow users, developers or even embedded vendors to create own "development platform" which can be easily installed using PlatformIO. # Requirements ## Platform developer Developer of "development platform" should provide the next information for PlatformIO Platform Manager: - Generic platform information (name, version, etc) - Package dependencies - Platform build script - Frameworks (supported by this platform) build scripts - Boards list (only for embedded platforms) **Package dependencies** should allow to use `semver` notation. For example, `"framework-mbed": "~1.2.0"`. In this case default PlatformIO Package Storage should be used. If package does not exist in PlatformIO Package Storage or developer wants to use own package, then allow to specify "direct download link" to it. ## PlatformIO Core ### PlatformIO Platforms Registry Need to implement public Platforms Registry where will be located information about existing "development platforms". They will by used by http://docs.platformio.org/en/latest/userguide/platforms/cmd_search.html # Using # Platform is registered in Platforms Registry It should look from the CLI as generic CLI for PlatformIO 2.0http://docs.platformio.org/en/latest/userguide/platforms/cmd_install.html # Platform is not registered in Platforms Registry Allow to install it directly using archive or folder which contains `platform.json` ``` platformio platform install file:///path/to/platform.zip platformio platform install https://github.com/path/to/platform.zip platformio platform install file:///path/to/platform/dir ``` Comments are welcome!

zgoda · May 30, 2016, 4:39pm

I see lot of development in 3.x area, is the code usable yet?

ivankravets · May 30, 2016, 5:00pm

Do you use PlatformIO IDE or only PlatformIO CLI?

massenz · June 12, 2016, 12:58am

On a related note, is there any way to update a package?
Currently, framework-mbed is “latest” at version 13 (which, looking into mbed.h means actually 117).

$ platformio platforms update

Platform nxplpc
--------
Updating framework-mbed package:
Versions: Current=13, Latest=13 	 [Up-to-date]
Updating toolchain-gccarmnoneeabi package:
Versions: Current=3, Latest=3 	 [Up-to-date]

Far as I can tell, this version has a bug in its implementation of Serial.printf() which prevents emitting floats - however, if I build my very same code in the mbed online IDE, (which links with revision 121 of framework-mbed) the code runs correctly.

How do we go about updating the framework?
(I’m using platformio 2.9.5 – let’s assume I’d rather not upgrade to 3.0, unless you tell me it’s stable and fully usable).

Many thanks!

ivankravets · June 12, 2016, 7:17am

@valeros please update ARM mbed framework. Thanks.

massenz · June 12, 2016, 7:45am

Thanks, guys - you’re heroes!

ivankravets · June 13, 2016, 5:04pm

The ARM mbed framework package has been updated today and released with new PlatformIO 2.10.0.

Please upgrade

massenz · June 14, 2016, 5:49am

Well, thanks for that - it didn’t work: it wasn’t a bug in mbed’s printf() library, but something in platformio.

I’ve posted a more detailed description here (here’s to hoping I can post the link here…)