[Development] Proposal: installation of QtWebkit helper processes

[Thiago Macieira]

Some other thoughts from IRC:

the helper process should be installed to libexec, regardless of the outcome 
of the tool renaming discussion. This is an executable run by a library and 
that doesn't make sense being run standalone, so it's the textbook example of 
libexec.

Adding the QtWebKit version number to the process's name is nice, but not 
necessary. Installing two Qt5WebKit to the same prefix is not supported. The 
other thread is about co-installation with Qt 4. The libexec path already 
contains "qt5", so it will not conflict with Qt 4.

If QtWebKit supports being installed to a different prefix than QtCore, it will 
need to keep its own libexec path. This might be useful for having two 
QtWebKit compiled against the same QtCore. Up to the webkit guys to decide 
whether they support this or not.

On segunda-feira, 22 de outubro de 2012 17.35.32, Hausmann Simon wrote:
> Adding webkit-qt list to Cc.
> 
> The proposal sounds good to me. Any other opinions?
> 
> Simon
> 
> --
> Sendt fra min Nokia N922.10.12 19:05 skrev shane.kearns at accenture.com:
> Background:
> QtWebkit in Qt 5 requires two helper processes:
> QtWebProcess & QtWebPluginProcess
> 
> Applications using a web view component will not work if these executables
> are not in the path.
> 
> These processes are an implementation detail of Webkit, and the interfaces
> may not be compatible between versions.
> 
> Proposal:
> Include the version in the executable name, either the Webkit version or the
> Qt version will do. - to prevent running an incompatible version
> 
> Install to the libexec path, e.g. $(libexecdir)/qt5 on linux
> I expect on windows each application will carry it's private copy, and on
> mac it will be inside the framework package.
> 
> Use QLibraryInfo to locate the helper executable at runtime. (see Thiago's
> proposal on tools) Assumed that for developer builds this points to the
> right place in the build tree.
> 
> --
> 
> 
> 
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise private information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited.
> 
> Where allowed by local law, electronic communications with Accenture and its
> affiliates, including e-mail and instant messaging (including content), may
> be scanned by our systems for the purposes of information security and
> assessment of internal compliance with Accenture policy.
> 
> ____________________________________________________________________________
> __________
> 
> www.accenture.com
> 
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20121022/a7b26523/attachment.sig>