Skip to content

Third party board profiles in 1.5 #1423

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

projectgus
Copy link
Contributor

A couple of tweaks I noticed were useful when writing a v1.5-compliant board profile for the Freetronics LeoStick.

Will start a thread on the developer list as well.

…valid directories

This allows you to create hardware profiles that support both pre-1.5 and 1.5 onwards (boards.txt, cores, bootloader etc. in root for pre-1.5 and <architecture>/ directories containing 1.5 onward content.

Still prints a warning if a hardware folder doesn't contain anything 1.5 compatible.
@cmaglie cmaglie merged commit b8c795e into arduino:ide-1.5.x Jul 15, 2013
@cmaglie
Copy link
Member

cmaglie commented Jul 15, 2013

Merged (manually). Thank you!
C

@projectgus
Copy link
Contributor Author

Thank you, Cristian!

Around the same time there was some related discussion on the developers list about allowing third party board profiles to supply their own 'core', while still using arduino's platform.txt - as I understand it at present if you want to ship your own core, you have to ship a copy of platform.txt to match (as the core is used to look up the platform.)

My post to that thread with a suggestion is here:
https://groups.google.com/a/arduino.cc/d/msg/developers/RdDTXS6Z_Ow/mNX8D9_rzHwJ

Did you get a chance to think about this one? Still happy to send a pull request if the change would be acceptable (I think it would be very useful to avoid unnecessary duplication of platform.txt with the resulting divergence of content.)

Cheers,

Angus

@ghost ghost assigned cmaglie Sep 19, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants