hello
i have installed IDE on a Raspberry Pi 4b!
for a Board with LoRa i got a zip folder with the needed libraries.
where should i entpack and move this folder?
another question
i have on my folder /home/pi/
a folder called
arudino and
arduino-1.8.10
so the end question when compiling and uploading the file i go a error
this error TimeLib.h: No such file or directory is s
strange because it is on the same folder then the ino file too
ESP-sc-gway:47:69: error: TimeLib.h: No such file or directory
compilation terminated.
Multiple libraries were found for "SPI.h"
Used: /home/pi/.arduino15/packages/esp32/hardware/esp32/1.0.5/libraries/SPI
exit status 1
TimeLib.h: No such file or directory
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
thanks for your help and feedback
have a nice day
vinc
vinc14:
for a Board with LoRa i got a zip folder with the needed libraries.
where should i entpack and move this folder?
Unzip the downloaded file.
From the unzipped folder, move the contents of the libraries subfolder to the libraries subfolder of your sketchbook folder. You can find the location of the sketchbook folder in the Arduino IDE at File > Preferences > Sketchbook location (default is ~/Arduino).
The other folder in that .zip (ESP-sc-gway) is an Arduino sketch. You can store Arduino sketches anywhere you like and open them via the Arduino IDE's File > Open.
However, you may find it convenient to store the sketch under the sketchbook folder (but don't put it in the libraries folder, because it's not a library!). The reason is that sketches located under the sketchbook folder are accessible via the Arduino IDE's File > Sketchbook menu. But this is only a convenience feature. The accessibility via the menu is the only benefit of using the sketchbook for your sketches.
vinc14:
so the end question when compiling and uploading the file i go a error
this error TimeLib.h: No such file or directory is s
strange because it is on the same folder then the ino file too
That's not the correct way to install a library. You can learn the three ways to install Arduino libraries here:
I recommend always using Library Manager when possible because this makes sure the library is always correctly installed and also makes it very easy to get updates. However, in some cases, such as this Gateway project, the libraries might not be available from Library Manager, so it is also very useful to learn the other library installation techniques.
@pert
this helped thanks a lot, i mean i have other Protblems now but this part is now accepted!
just another question pop-up , as soon i have copied the libraries - the IDE wish to update theme!
i am not sure if it is save to let it happen?
vinc14:
this helped thanks a lot, i mean i have other Protblems now but this part is now accepted!
You're welcome. I'm glad if I was able to be of assistance.
vinc14:
as soon i have copied the libraries - the IDE wish to update theme!
i am not sure if it is save to let it happen?
This is a tricky question. The sketch author was using the versions of the libraries in the .zip file when they wrote the code, so you know the code is compatible with those libraries. Since that time, it's possible that breaking changes were made to the libraries that cause them to no longer be compatible with the sketch. On the other hand, it's very possible that the library authors have fixed bugs or made useful improvements that don't impact the compatibility. Ideally, we will do a careful evaluation of the changes made to a dependency before updating. There is actually a standardized system for communicating this via the version number called "semver":
If a developer is faithfull following semver, you can be confident in upgrading from 1.0.0 to 1.0.1. You will also know that upgrading from 1.0.1 to 1.1.0 is safe, but that you might want to check the changelog to see whether there was a useful new feature. You will also know that you should set aside some time to carefully check the changelog and test when upgrading from 1.1.0 to 2.0.0 because there was a breaking change that might cause your program to stop working.
Unfortunately, not all developers follow semver faithfully, and many don't bother to clearly document their development work. So updating dependencies can be a bit of a risky business.