The modes being displayed are the default modes.
This is incorrect.
The modes being selected should be displayed.
This is a bug only with the messages being printed and does not affect the actual build process.
The build process appears to be operating correctly.
if (build_arguments->used > 1) {
modes_custom.used = build_arguments->used - 1;
}
- else if (data_build.setting.modes.used) {
- modes_custom.used = data_build.setting.modes.used;
- }
}
f_string_static_t modes_custom_array[modes_custom.used];
modes_custom.array[i] = build_arguments->array[i + 1];
} // for
}
- else if (data_build.setting.modes.used) {
- for (; i < data_build.setting.modes.used; ++i) {
- modes_custom.array[i] = data_build.setting.modes.array[i];
- } // for
- }
}
// Custom modes are always used if provided, otherwise fallback to the passed modes or the default modes.