-
-
Notifications
You must be signed in to change notification settings - Fork 114
error running the builder : recipe.preproc.includes pattern is missing
#3
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
Comments
Every core out there misses that recipe. It's listed in a partial |
For the record, that |
And that recipe is not listed in platform.txt, but in |
That beta relase you linked to contains some code that looks for non portable settings.
|
Compiled the empty sketch with :
Result (The warning message
|
Given your IDE folder is
Pay attention to the differences between hardware and tools paths and to the additional attribute cpu which, for the nano, is mandatory |
Your are right, that line worked, thanks
|
Yes, but that would require duplicating almost entirely those board definitions, which was what we wanted to avoid when introducing additional properties such as cpu. On the Arduino IDE they result in easy to use menus, which help select whatever additional compilation flag |
@ffissore
but in the current avr Example But I can live with the current |
You should open an issue on https://github.com/arduino/Arduino/, as it's where avr core is developed. It's an improvement and it needs consensus and approval from @cmaglie and @facchinm |
even i had the same problem Arduino: 1.8.1 (Windows 10), Board: "ATtiny13 (internal 9.6 MHz clock)" The current selected board needs the core 'arduino:arduino' that is not installed. Error compiling for board ATtiny13 (internal 9.6 MHz clock). Do you have a comment? |
We're handling @AMKOSHESH's issue on the forum: |
Compile an empty sketch from the commandline :
Compile with
yields
grep
can't find a rulerecipe.preproc.includes
in an arduino-1.6.6 (or older ) distributionEberhard
The text was updated successfully, but these errors were encountered: