-
Notifications
You must be signed in to change notification settings - Fork 27
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
add include-qt-plugins #26
Conversation
You are doing well. By none of your faults, the Qt plugin option will override its value entirely, rather than expanding it. So the looping is wrong. Instead the input list should be condensed to a single use of I need to think a bit, if we want to have it that way. Commonly, people fall into the trap of thinking, that they do not replace the default of Since no other option is like this, it's kind of indicative of a bug in Nuitka. I would ask you to allow for me to make a change to this option for say 1.6.2 in behavior. You would then just do the same as you did, but with --no as well, as it would be better. I do not think, we should not cater to this kind of UI bug in Nuitka, effectively making it harder to change. |
One thing that would be nice, if these options that pertain to plugins, could be namespaced in some way, and make sure the plugin is actually enabled. I think I can take that on, once I find the time. The ordering in the schema is kind of weird for now as well. |
A simpler change would be to just make an |
I can follow your thoughts just partially. Is there anything I should/could do? |
@JaegerStephan no, I am just going to make code's your assumption that you can specify --include-qt-plugins multiple times work, right now it's not the case. We missed the boat for 1.6.2, but I am going it right now, the small version, that is just going to be incrememtal rather than replacing, and then we can merge as is. |
You can run your instance of the action against current |
Thank your for your proposal but I think I'll wait until it is on the main branch since I'm working in enterprise environment and have to request for any action (as well as new branches and versions). So far I'll work with my own fork. But I'll be happy to use it soon from a new version :-) |
Ok, going to merge it even before 1.7, so it can be used with develop already, once my change hits there. |
@@ -176,6 +180,12 @@ runs: | |||
$args += @("--enable-plugin=$plugin"); | |||
} | |||
} | |||
if ("${{ inputs.include-qt-plugins }}" -ne ''){ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is bound to create an options usage that will not work for Nuitka 1.6 yet, but for 1.7 and current develop it will do the right thing, even if the input is a list, it will no longer override, but amend values to the plugin.
Hi!
It's my first pull request. I hope I'm doing well.
I implemented the
include-qt-plugins
which is related to #15 and used it successfully for compiling on windows runner.I strongly aligned the code to
enable-plugins
.I would ask you to test the implementation (best with linux oder macos) and approve the pull request.
Bests,
Stephan