On segunda-feira, 22 de outubro de 2012 14.59.09, Ziller Eike wrote: > >> Just as a side note, that requires that Windows and Mac to also have this > >> tool, and e.g. on Windows to have that tool in the PATH and pointing to > >> the > >> corresponding Qt for the environment set up shell scripts. In the SDK, > >> the > >> tools/ directory might be a good place for it. > > > > > > > > It's easy to add a -qt5 ignored option to the regular qmake too. > > So that if you happen to have a "real" qmake instead of the wrapper in the > PATH on linux, you don't realize that when you are doing "qmake -qt5" to > force "most current qt5 version" (or whatever the semantics would be), you > actually execute a completely different qmake? I don't think that would be > a good idea.
It will do that too if it's in a separate build looking at a non-standard configuration path. That's mostly what's going to happen on Windows anyway, isn't it? -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
