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

Need a one line build script: at least cheap build simplification? keyword: lazy #5225

Closed
rusefillc opened this issue Apr 7, 2023 · 7 comments

Comments

@rusefillc
Copy link
Contributor

rusefillc commented Apr 7, 2023

at the moment one cannot get a legit firmware by invoking just compile_proteus_f4.sh - for instance one has to manually invoke
./gen_config_board.sh config/boards/proteus proteus_f4 prior to invoking compile_proteus_f4.sh

./gen_config_board.sh config/boards/proteus proteus_f7

(that's due to custom Lua script area size specifically in proteus prepend.txt)

Similar command for another board would be ./gen_config_board.sh config/boards/hellen/small-can-board small-can-board

that's not nice

would it be trivial just to move gen_config_board.sh invocation into common_make.sh to get a more resilient single-click local build?

@rusefillc
Copy link
Contributor Author

cheaper gap implementation of #4302

@rusefillc rusefillc changed the title cheap build simplification? cheap build simplification? lazy Jun 12, 2023
@rusefillc
Copy link
Contributor Author

@chuckwagoncomputing I would like to beg for your help here, are you in a position to volunteer any resources?

@rusefillc rusefillc changed the title cheap build simplification? lazy Need a one line build script: at least cheap build simplification? keyword: lazy Jul 22, 2023
@rusefillc
Copy link
Contributor Author

@rusefillc
Copy link
Contributor Author

Depends on #5546

@rusefillc
Copy link
Contributor Author

cheaper gap implementation of #4302

@pchmura4 all this here is the general problem area

@rusefillc
Copy link
Contributor Author

#5817 has accidentally fixed this issue - compile_proteus_f4.sh produces a value firmware now (well, only if you do not need to actually change metadata)

A proper solution with automatic on-demand code generation is still needed

@chuckwagoncomputing
Copy link
Member

This is fixed, you can call firmware/bin/compile.sh and either pass it a meta-info file or pick one from a list.

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

No branches or pull requests

2 participants