Skip to content

SrcWrapper.h: No such file or directory - It still persists: "locked as resolved" #1538

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

Closed
rtek1000 opened this issue Dec 26, 2022 · 1 comment
Labels
status: usage error Op expectation of behaviour of Sloeber is not i line with the actual behaviour.

Comments

@rtek1000
Copy link

    @rtek1000 please do not resurrect old issues.

Originally posted by @jantje in #1143 (comment)

"locked as resolved and limited conversation to collaborators"

    It still persists:

Arduino.h:33:12: fatal error: SrcWrapper.h: No such file or directory

(eclipse/embedcpp-2022-03/eclipse/arduinoPlugin/packages/STMicroelectronics/hardware/stm32/2.4.0)

P.S.: Since it failed to automatically install the STM32 core, so I copied the STM32 functional installation folder in the Arduino IDE to the eclipse folder.

Originally posted by @rtek1000 in #1143 (comment)

@jantje
Copy link
Member

jantje commented Dec 26, 2022

so I copied the STM32 functional installation folder in the Arduino IDE to the eclipse folder.

Do not do so unless you are a experienced user and understand about the Arduino framework or have detailed instructions of how to do it.
STM32 can be installed the normal way.

SrcWrapper.h is a library that should be auto magically included but that inclusion is based on the indexer working properly #1491 and #1534 both degrade the indexer working
You can manually add the library to the project (using the Sloeber menu) but for a reasonable Sloeber experience with STM32 you will need

  1. the nightly release or at least anything since Indexer in V4.4.0 is Seriously Flakey with ESP32 Code #1491
  2. the workaround described in STM32 opt file makes code analizer to fail #1534

And no the problem fixed in #1143 does not persist.

@jantje jantje added the status: usage error Op expectation of behaviour of Sloeber is not i line with the actual behaviour. label Jan 16, 2023
@jantje jantje closed this as completed Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: usage error Op expectation of behaviour of Sloeber is not i line with the actual behaviour.
Projects
None yet
Development

No branches or pull requests

2 participants