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

HWDEF: allow all build targets for non-integrated boards #26660

Merged
merged 1 commit into from
Apr 1, 2024

Conversation

Hwurzburg
Copy link
Collaborator

No description provided.

Copy link
Collaborator

@andyp1per andyp1per left a comment

Choose a reason for hiding this comment

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

I'm not sure this really works - these were done because of flash limitations. At a minimum we should make sure they have the fpv include and then look at the remaining flash on plane - my guess is that the F745's will be really tight. These are really not designed for plane targets either so not sure whether its really worth compromising everyone else for the few people that need it.

@Hwurzburg
Copy link
Collaborator Author

BlitzF745AIO has 28K free when built for plane , SpeedybeeF405Mini has 85K,so your space argument is invalid....without a std build target to get define defaults its impossible for a normal user to create another vehicle version using the custom build server since it will use Copter/Dronecan defaults and many sensorsare copter only....no way for average user to know what to uncheck

@tridge tridge dismissed andyp1per’s stale review April 1, 2024 23:17

discussed on dev call, it will fit

@tridge tridge merged commit b83a895 into ArduPilot:master Apr 1, 2024
40 checks passed
@Hwurzburg Hwurzburg deleted the autobuild branch April 4, 2024 13:19
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.

4 participants