On Friday, 11 de November de 2011 11.03.13, Olivier Goffart wrote:
> The problem of submodule will be the same within QtDeclarative.
>
> How about making v8 its own module.
That's what I suggested. Having a submodule inside the module you're working
on makes it very hard to keep a handful of cha
On Friday 11 November 2011 08:02:38 Kent Hansen wrote:
> Thiago, I missed the previous discussion on V8's location. Since
> everyone seems to agree that QtCore shouldn't depend on V8, I guess
> we're free to move it around again. One idea from Lars is that we move
> it back to qtdeclarative and bui
One thing we just remembered is that we want to have v8 snapshot support
when cross-compiling.
So we'll have a mkv8snapshot tool that must run on the host.
How can that be achieved if we move v8 out of qtbase? Currently
makefiles for host tool are handled in configure, see this line:
*
Absolutely, that dependency is fine for WebKit.
Simon
--
Sent from my Nokia N911.11.11 08:10 skrev Hansen Kent (Nokia-MP-Qt/Oslo):
Hi,
bcd16f9453e543ba819385d87bd7061a4caeb325 bumps the sha1 for the V8
submodule, and introduces some build changes to src/v8. You'll need to
do "git submodule up
Hi,
bcd16f9453e543ba819385d87bd7061a4caeb325 bumps the sha1 for the V8
submodule, and introduces some build changes to src/v8. You'll need to
do "git submodule update" to be able to build libQtV8 again.
Thiago, I missed the previous discussion on V8's location. Since
everyone seems to agree tha
