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.

Sign up for GitHub

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

Jump to bottom

KConfig Support for Updates via KIAUH #607

Closed
smbenson0712 opened this issue Dec 10, 2024 · 4 comments · Fixed by #621 or #628
Closed

KConfig Support for Updates via KIAUH #607

smbenson0712 opened this issue Dec 10, 2024 · 4 comments · Fixed by #621 or #628
Labels
Help wanted Scope: Components Status: Prepared Something is ready to be released Type: Feature Request New feature or request
Milestone
v6.0.0-alpha.14

Comments

@smbenson0712
Copy link

Is your feature request related to a problem? Please describe

No problem, just a convenience for multiple mcu's with different menuconfig settings.

Describe the solution you'd like

As many printers now are using multiple mcu's, it would be very nice to utilize KConfig via KIAUH. This would make updating easier when you have to compile 2-3 mcu firmwares with different menuconfig settings.

Describe alternatives you've considered

I usually update all the software with KIAUH and then use the command line to compile and flash the firmware of my mcu's using KConfig manually.

Additional information

No response
@dw-0 dw-0 added Type: Feature Request New feature or request Status: Available Something that was accepted and can be worked on Scope: Components Help wanted labels Dec 26, 2024
@CODeRUS
Copy link
Contributor

CODeRUS commented Jan 17, 2025

@smbenson0712 is that same with instructions provided by FYSETC for NIS?
https://github.com/FYSETC/Nozzle-Input-Shaper

I just encountered this problem myself.

@dw-0 what do you think about this, asking for a name for the file and then outputting a selection of .config files to build would be a sufficient solution?

@dw-0
Copy link
Owner

dw-0 commented Jan 18, 2025

@dw-0 what do you think about this, asking for a name for the file and then outputting a selection of .config files to build would be a sufficient solution?

@CODeRUS Im not 100% sure i understand your suggestion but maybe our ideas kind of match already?
I had some very rough ideas in the past how such a feature could be designed.
Lets say the user selected the following: 4) [Advanced] -> 1) [Build]

  • If no or only the default .config file exists, there could be a dialog at the end of the build process if the config should be saved as a custom config file.
  • If there are already available .config files, the user can select one of the files and the build process would start with that config
    • There could be an option to create a new config even if there are already available files to create a new config from scratch
    • There could also be an option to delete config files (maybe part of a second iteration of that feature)

Is it a good idea to save those configs in their dedicated directory? This may make checks for existing files easier?

@smbenson0712
Copy link
Author

In my opinion I think that would be a perfect solution. Easy to follow like all the other options in kiauh.

@CODeRUS
Copy link
Contributor

CODeRUS commented Jan 19, 2025

@dw-0 your explanation is totally correct

@dw-0 dw-0 added this to the v6.0.0-alpha.14 milestone Feb 8, 2025
@dw-0 dw-0 linked a pull request Feb 8, 2025 that will close this issue
feature: save and select kconfig #621
Merged
@dw-0 dw-0 mentioned this issue Feb 9, 2025
Merged
@dw-0 dw-0 added Status: Prepared Something is ready to be released and removed Status: Available Something that was accepted and can be worked on labels Feb 9, 2025
@dw-0 dw-0 closed this as completed in #628 Feb 9, 2025
dw-0 added a commit that referenced this issue Feb 9, 2025
@dw-0
Release v6.0.0-alpha.14
0becf9d 
fixes #607
fixes #615
fixes #618
fixes #619
fixes #620
fixes #623
fixes #627
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Help wanted Scope: Components Status: Prepared Something is ready to be released Type: Feature Request New feature or request
Projects
None yet
Milestone
v6.0.0-alpha.14
3 participants
@CODeRUS @dw-0 @smbenson0712