On segunda-feira, 22 de outubro de 2012 13.57.36, Lincoln Ramsay wrote: > Though, I'm not sure we need QT_SELECT. If you can change an environment > variable, you can modify PATH.
Changing one variable to a specific value is considerably easier than changing PATH. > > Additionally, this tool may support options like -add-qt and > > -set-default-qt. I'm also open to adding an option -run-tool= (e.g., > > qmake -qt=5 -run- tool=qmlplugindump) if that's of interest to people. This can also be used for symlinking if it detects argv[0]. > > I guess -add-qt is more for developer convenience? Under normal > operation, I'd expect distros to install Qt + > /etc/xdg/qmake/something.conf for this tool to find. Yes. > I suppose set-default-qt is necessarily user-specific. Yes. > I'm going to respond here to people asking for directory-specific qmake > binding: > > Just set PATH. Setup a cdrc thing in your shell if you want to automate > this. As I said, modifying PATH isn't easy and it can have adverse consequences. But it is an option available to you. > > I haven't decided whether this tool should be a shell script, a perl > > script or another bootstrapped executable. > > If this replaces the Qt 4 qmake, it might be problematic to have it > built from Qt 5 sources. It would need to be statically built and split > off during packaging so that it had no dependencies on Qt 5. If you can > achieve that, go ahead and write it in Qt. Yup. -- 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 Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
