What is different with this compiler that it needs a separate entry?
Can't it be made as a copy of the original gcc compiler?
Probably we should modify this dialog to make users add compilers in the list and not stick them by default there... but this is a bit more complex task...
Any, ideas on the short list of compiler to have installed?The list should be empty if the autodetector hasn't found a compiler.
These two "null" and "gcc" are needed in the list; but, what others should default to being checked.
And, what is the name to be used to name this list? I feel compiler list is misleading.Why do you think it should be a list? It should be in a new dialog hidden behind an Add button in just below the selected compiler combo box we have now.
Any, ideas on the short list of compiler to have installed?The list should be empty if the autodetector hasn't found a compiler.
These two "null" and "gcc" are needed in the list; but, what others should default to being checked.And, what is the name to be used to name this list? I feel compiler list is misleading.Why do you think it should be a list? It should be in a new dialog hidden behind an Add button in just below the selected compiler combo box we have now.
How about another check box on the "Global Compiler Setting" "Other Settings" ?
Right above or below the "Enable non-platform compilers".
Tim S.
How about another check box on the "Global Compiler Setting" "Other Settings" ?
Right above or below the "Enable non-platform compilers".
Tim S.
Why do you want to introduce this complexity instead of just adding a field if the compiler is enabled? You'll have to add such field anyway. And then add the simple dialog where the user can select the needed compilers. And lastly add some logic to show this dialog if C::B detects if the user has old config.
Is the default GCC compiler user-defined using your logic? Will it be removed from everybody's list of compilers if this change is added to C::B?
Why do you want to introduce this complexity instead of just adding a field if the compiler is enabled? You'll have to add such field anyway. And then add the simple dialog where the user can select the needed compilers. And lastly add some logic to show this dialog if C::B detects if the user has old config.
Is the default GCC compiler user-defined using your logic? Will it be removed from everybody's list of compilers if this change is added to C::B?
user-defined is what the auto detect window calls it; me I would throw out the auto detect and just add a field like you suggest. But, that does NOT seem to match the autodetect windows that is displayed on startup when it detects new/missing compilers.
Tim S.
1. How do I enable not found compiler? I've installed one in non-default location and want to use it for example.
2. How do I disable found compiler I don't care for?
3. Why are you mixing addition of msys2-mingw and the autodetection changes in this patch?
4. Can you install this new compiler on linux? I doubt, but just want to ask.
5. Default parameter values is better to not be used.
It should be in a new dialog hidden behind an Add button in just below the selected compiler combo box we have now.
It should be in a new dialog hidden behind an Add button in just below the selected compiler combo box we have now.
Adding a Dialog is beyond what I feel up to doing at this time; but, it does make more sense than an "Disable" button like I was thinking of doing.
I am a C Programming who does almost no GUI programming.
I will see if any of the wx Dialogs I know about can be adapted to do what you want; but, I will NOT have time for a few weeks.
Tim S.
WX_DEFINE_ARRAY(Compiler*, CompilersArray);