-
Notifications
You must be signed in to change notification settings - Fork 131
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
CI: Build on CircleCI with XC16 1.36B and MPLABX 5.10 #118
base: master
Are you sure you want to change the base?
Conversation
Can someone test the following on Windows and paste the output? I have tried it in wine (because I do not have a Windows machine, but encountered weird behaviour (changes in header-files did not make the project rebuild properly).
|
This may be a bug in MPLAB X 5: https://www.microchip.com/forums/m1061336.aspx |
Use 'git describe --tags --always --dirty' to generate a version string which gets included in every binary. The --tags is necessary, because the latest tag 'v7.0' is not an annotated tag. If the git-describe-output changes, make will rebuild the required files automatically. Unfortunately, this is broken on Windows due to a bug in Microchip's toolchain: https://www.microchip.com/forums/m1061336.aspx Until that is fixed, a full rebuild is always done on Windows platforms, because builds that are a bit slower are better than hard to debug situations due to inconsistent builds.
I have worked around the Windows-only-bug in the Makefile. From my perspective, this PR is ready. It is a first step. In the future one could think of:
|
This adds automatic building of both the firmware and the bootloader for BPv4 and BPv3 via CircleCI.
Example build here: https://circleci.com/workflow-run/2a0843b0-7009-4b1b-a3bd-6c6d7ac33b40
To enable it for this repository, one of the owners has to set it up at CircleCI.
Let's discuss this first before merging.
Ideas:
Add git-describe-output into the built firmware