> On Saturday November 11 2017 15:05:53 Konstantin Tokarev wrote:
>
>> Perhaps we could add "minimal" configuration for QtWebKit in Coin, with
>> disabled
>> QML API, multimedia features, and "extra" stuff like WebGL and geolocation.
>
> Meanwhile, what would be a proper combination of options
On sábado, 11 de novembro de 2017 06:25:43 PST Konstantin Tokarev wrote:
> Or use built-in HTTP server to avoid disk operations
One more reason to add an HTTP server framework.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
___
On sábado, 11 de novembro de 2017 05:01:53 PST René J.V. Bertin wrote:
> Am I doing something wrong or am I simply hitting a limitation?
it's a limitation of your environment. Static linking LTCG precompiled code
requires a special linker. It's not very well supported everywhere.
--
Thiago Maci
On Saturday November 11 2017 15:05:53 Konstantin Tokarev wrote:
>Perhaps we could add "minimal" configuration for QtWebKit in Coin, with
>disabled
>QML API, multimedia features, and "extra" stuff like WebGL and geolocation.
Meanwhile, what would be a proper combination of options to set to achie
On Saturday November 11 2017 17:47:14 Konstantin Tokarev wrote:
>Well, LTO and missing symbols go hand in hand, you should be ready to deal
>with such errors.
That shouldn't be the case IMHO, and most of the time it isn't at least not
when building Qt.
>What is your reason to use LTO? Can you
> On Saturday November 11 2017 15:05:53 Konstantin Tokarev wrote:
>
>> Of course it won't be nearly lean and mean as what you described above,
>> however
>> it requires virtually no extra maintenance and is unlikely to break on user
>> content.
>> And it will reduce binary size substantially a
On Saturday November 11 2017 15:05:53 Konstantin Tokarev wrote:
>Of course it won't be nearly lean and mean as what you described above, however
>it requires virtually no extra maintenance and is unlikely to break on user
>content.
>And it will reduce binary size substantially and cut off depende
> On Saturday November 11 2017 16:12:38 Konstantin Tokarev wrote:
>
>> Note that you should be able to build whole qttools module against any Qt
>> install. It should work without any modifications.
>
> That's what I'd expect but not really what I'm looking for here. I could try
> it once to
On Saturday November 11 2017 16:12:38 Konstantin Tokarev wrote:
>Note that you should be able to build whole qttools module against any Qt
>install. It should work without any modifications.
That's what I'd expect but not really what I'm looking for here. I could try it
once to see if I get the
>> But improving Assistant need not imply changing QtWidgets. There are two
>
>> solutions for this:
>
>>
>
>> 1) make qttools depend on qtwebengine
>
>> 2) make Assistant load a plugin that is provided by qtwebengine (and
>> qtwebkit)
>
> 3) Make assistant use the system browser.
>
> I've
> But improving Assistant need not imply changing QtWidgets. There are two
> solutions for this:
>
> 1) make qttools depend on qtwebengine
> 2) make Assistant load a plugin that is provided by qtwebengine (and qtwebkit)
3) Make assistant use the system browser.
I've been wondering since a whil
> Hi,
>
> I have made some tweaks to the qttools/src/assistant directories so that I
> can build the Assistant as a standalone application against any Qt install.
Note that you should be able to build whole qttools module against any Qt
install. It should work without any modifications.
>To
Hi,
I have made some tweaks to the qttools/src/assistant directories so that I can
build the Assistant as a standalone application against any Qt install. To do
that, I removed the qtNomakeTools(), load(qt_module) and load(qt_app)
statements from the relevant .pro files, set up QtHelp to build
> On Saturday November 11 2017 14:44:42 Konstantin Tokarev wrote:
>
>> Not yet. The closest thing that exists at downloads.qt.io for now is [1], so
>> far
>> all pre-releases were published at [2]
>>
>> [1] http://download.qt.io/snapshots/ci/qtwebkit/5.9/latest/src/submodules/
>> Note that "5.9
> On Fri, Nov 10, 2017 at 11:03:46PM +0100, René J.V. Bertin wrote:
>
>>> > are there plans to retire QtWebKit support, migrate to using QtWebEngine
>>> > or
>>> > to improve QTextBrowser's HTML support?
>>>
>>> WebEngine is plainly inacceptable as dependency for QTextBrowser which is
>>> part
On Saturday November 11 2017 14:44:42 Konstantin Tokarev wrote:
> Not yet. The closest thing that exists at downloads.qt.io for now is [1], so
> far
> all pre-releases were published at [2]
>
> [1] http://download.qt.io/snapshots/ci/qtwebkit/5.9/latest/src/submodules/
> Note that "5.9.2" means Q
> On Saturday November 11 2017 11:56:49 René J.V. Bertin wrote:
>
> And sorry for the rapid-firing, but how should one interpret 5.212 vs. 5.9 in
> the branch names on code.qt.io/.../qtwebkit ? Is the former less coupled to a
> specific Qt version, for instance?
Yes, exactly.
>
> Keep up th
On Saturday November 11 2017 13:32:41 Konstantin Tokarev wrote:
>No
>
>http://qtwebkit.blogspot.com/2016/08/qtwebkit-im-back.html
Now that's interesting! Do the tarballs available via Qt
(qtwebkit-opensource-src-*) follow these developments - basically, do they
contain snapshots of QtWebKit th
> On Saturday November 11 2017 02:57:01 Konstantin Tokarev wrote:
>
>>> Back to the topic of this discussion. We've recently switched to Qt WebKit
>>> 5.212
>
> What Qt version does that correspond to?
Any Qt version >= 5.4
>WebKit is just being maintained for compatibility with its Qt depe
On Saturday November 11 2017 02:57:01 Konstantin Tokarev wrote:
>> Back to the topic of this discussion. We've recently switched to Qt WebKit
>> 5.212
What Qt version does that correspond to? WebKit is just being maintained for
compatibility with its Qt dependencies, no?
>> , and sadly it didn
20 matches
Mail list logo
