-
Notifications
You must be signed in to change notification settings - Fork 132
Getting NullPointerException parsing board.txt or platforms.txt #197
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
does it work to make and compile a sketch for arduino uno? |
Yes, or rather nearly. I had created a new Sketch, and the file for my code (test.ino) did not seem to get recognised and so main.cpp filed to link as it could not find setup() and loop(). If I rename test.ino to test.c it compiles cleanly. |
It seems like you did something wrong when creating your teensy environment. |
which warnings are you refering to? There are none from eclipse. If you mean in the install instructions I think I followed all that I noticed and seemed relevant to linux. |
the warnings generated by the compiler when compiling the ino project |
There are none apart from:- Starting combiner All the previous bits in the console are simply saying that the arduino components are being successfully compiled. There is no reference to test.ino at all (or anything derived from test) |
sorry it are errors not warning. ../.ino.cpp:8:2: error: #error the file: Demo_1.ino is not found in the indexer though it exists on the file system. |
Hi, I am the author of the installation instructions that I think you are referring to. Is it possible for that you've omitted to copy the boards.txt and platform.txt file as as described in the section that describes how to creat the teensy extension file ? Feel free to leave a comment on my blog or in the thread on the teensy forum.
|
@TrippyLighting |
There were no references to test.* (the file was test.ino) anywhere in the console. I have checked the file type associations, and both *.ico and *.pde were missing. I have entered them manually, and it made no difference. I did copy the boards.txt and platform.txt files, but I am don't recall the extension file bit - must have missed that, I will reread. |
Well I fixed it. It would appear that getting individual files from github - at least through the web interface - is problematic. When I cloned the repository and copied the files directly it works. |
I have finally been able to upgrade and it seems there are no changes to my instructions necessary.
|
Thanks for the positive feedback. |
I am trying to setup my eclipse teeny-3.1 development environment, and I keep getting this error. After I get this error if I try building my project (even a brand new one) I get all manner of errors because it tries using the avr-gcc compiler, not the arm-none-eabi one, but I suspect this is a symptom and not a cause.
I am using the latest nightly build of the plugin on Eclipse Luna on Debian Linux on an AMD-64 laptop. I am using the 1.5.5 version of the Arduino IDE with latest teensiduino code.
I also get the following top of a stack trace:-
java.lang.NullPointerException
at it.baeyens.arduino.toolchain.ArduinoLanguageProvider.getCompilerCommand(ArduinoLanguageProvider.java:144)
at org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.resolveCommand(AbstractBuiltinSpecsDetector.java:308)
at org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.calculateEnvHash(AbstractBuiltinSpecsDetector.java:422)
at org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.validateEnvironment(AbstractBuiltinSpecsDetector.java:466)
at org.eclipse.cdt.managedbuilder.language.settings.providers.AbstractBuiltinSpecsDetector.execute(AbstractBuiltinSpecsDetector.java:481)
which seems to be because a null value was returned a few lines earlier in:-
ICProjectDescription prjDesc = CoreModel.getDefault().getProjectDescription(currentProject);.
This according to the documentation for getProjectDescription means that this project does not have any CDT data associated with it.
I think I have followed all the installation instructions properly, although as most of them were for Mac or Windows I might have transcribed something wrongly.
David
The text was updated successfully, but these errors were encountered: