Skip to content
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

re-generated files from qm #3

Closed
wants to merge 1 commit into from

Conversation

dev-pmallapp
Copy link

No description provided.

Copy link
Author

@dev-pmallapp dev-pmallapp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@vChavezB
Copy link
Owner

vChavezB commented Oct 5, 2024

Thanks for your PR. Could you specify the changes you made ? From the branch name and the commit it seems this PR addresses updating the Port for v7.3.0 ?

In addition please mention for which version of the Arduino Core ESP32 this works.

Last version I ported was for ESP32 Core v2.0.11. Now the latest version is 3.0.5.

@vChavezB
Copy link
Owner

vChavezB commented Oct 5, 2024

Unfortunately I have tested your code via github action and it does not compile. Neither for esp32 core version 2.0.17 nor for version 3.0.5. I made a test branch to check your changes as I cannot fork your fork.

https://github.com/vChavezB/qpcpp_esp32/blob/test_7.3.0/

From what I can see you have a separate folder for include headers. This does not work out of the box for arduino. All your code has to be in the src folder. This is ugly, but it is the way Arduino works. See arduino/arduino-cli#501

The specific errors I got for the build are located in the github action runner:

https://github.com/vChavezB/qpcpp_esp32/actions/runs/11194440949/job/31120920028

My solution was to put all the headers and source files in a flat structure in src.

Please add my github actions workflow in your branch so you can automatically test if your PR can be compiled.

https://github.com/vChavezB/qpcpp_esp32/blob/test_7.3.0/.github/workflows/build.yml

@dev-pmallapp
Copy link
Author

dev-pmallapp commented Oct 6, 2024 via email

@vChavezB vChavezB closed this Oct 7, 2024
@vChavezB
Copy link
Owner

vChavezB commented Oct 7, 2024

Yes, I think this happens by default. If you merge from your fork it will suggest that the merge be done to the default branch of the original repo.

No problem, PR closed !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants