On Tuesday, 3 November 2026 23:52:19 Pacific Standard Time Eskil Abrahamsen Blomfeldt via Development wrote: > I can definitely make it a compile-time option if that is the convention, > but we're not consistent about this in Qt. The usual reason for using > environment variables for developer options for me has been that the > evaluation happens inside the Qt library, and many users do not build Qt > themselves (they either get it from the installer, from the distro or some > other system integrator). Therefore, I usually prefer environment variables > in cases where I know we are likely to get a lot of reports looking to opt > back into the old behavior because they have a release next week etc. and > compile-time options in cases where we think the defaults will be perfectly > fint for 99% but there might be 1% with very special customization needs.
A compile-time choice but at the time of compiling the application/plugin/ library, not Qt itself. That is, an #if in the header that selects one overload or another, or instead the value of a default parameter. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal Engineer - Intel DCG - Platform & Sys. Eng.
smime.p7s
Description: S/MIME cryptographic signature
-- Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
