-
Notifications
You must be signed in to change notification settings - Fork 132
problems using stm32duino in sloeber 4.4 #1378
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
SrcWrapper.h is a library that should be included in the libraries folder. By the way ... If you think it is a mess why are you using Sloeber?. |
Hi jantje, oh my dear, I some how used ambiguous wording in my initial post. I very much appreciate sloeber, your work and help here, and think it is a very good tool. back to the initial problem: Again, many thanks for helping :) |
Thanks for the clarification. |
Since this is quite a generic title, I hope it is OK to reopen this issue as I ran into further problems trying to switch my project from AVR to STM32. It seems to me that the variant.h is not included properly, which leads to many many consecutive errors here is part of the console output:
this repeats several times, and then follows some errors about undefined symbols, which I think relate to this initial error |
Plerase provide the command line that leads to this error and a screenshot of project properties->arduino |
Hi jantje, I'm not sure what you mean with "command line" (well, this clearly shows my noob status, I guess...)
I could also post the entire console output, but it is quite a lot... Properties screenshots: [edited because of wrong formatting] |
Don't know if its related, but there seems to be a general issue when switching platforms....
|
Sloeber does not delete all libraries when swapping platform. In your case sloeber does not find an alternative for SrcWrapper and keeps using the stm32 provided library. |
I see that the command |
Hi jantje, thank you for the advice to use multiple configurations (will have to figure out how this works) or different projects with shard code. I have two platform.sloeber.txt files.
and one in a subdirectory of
both have v1.01.test 20 version Upgrade to the nightly build resulted in a java/registry error:
is there a way to downgrade again? |
http://eclipse.baeyens.it/how_to.shtml#/n You can also download the nightly from the actions option at the top of this page.
I don't know |
Latest nightly did the trick! And thanks as well for the backup reminder, I sometimes still forget it ;-) [maybe unrelated] |
Cool
Sloeber does not come with any gcc/platform. So the time you start using sloeber decides on the default arduino avr platform that gets installed (the latest ). Other platforms can be installed with json files and other hardware and are completely up to you. One thing to note is that if you install with json it can be the download only partially succeeded and the you have a consistent incomplete gcc/core/library. |
Hi,
I am using a fresh install of sloeber 4.4 and I even cleared the workspace and created a new project in which I copied my old source files because of issues during update - but that is not the concern.
I am evaluating whether I can switch my project over to STM32 and therefore downloaded the platform from https://github.com/stm32duino/BoardManagerFiles/raw/master/package_stmicroelectronics_index.json
When I build (after clean or incremental) I get several times the same error in the console:
C:\Sloeber\arduinoPlugin\packages\STMicroelectronics\hardware\stm32\2.0.0\cores\arduino/Arduino.h:33:12: fatal error: SrcWrapper.h: No such file or directory 33 | #include "SrcWrapper.h" | ^~~~~~~~~~~~~~
which is present in the folder
C:\Sloeber\arduinoPlugin\packages\STMicroelectronics\hardware\stm32\2.0.0\libraries\SrcWrapper\src
I guess that I somehow have to tell eclipse / sloeber / gcc where to find SrcWrapper.h but have no clue on how to do that...
Recalling the last issue I had with paths and sloeber I recall that this can be a mess...
Cheers,
Bob
The text was updated successfully, but these errors were encountered: