Apologies for the late reply. What I want to do is to build in a
separate branch on OBS V8 with your changes and then to see how
Chromium reacts on it. From the past I know that chromium is quite
reacting on changes within V8. However I don't think that your request
should make such a big difference.
I will let you know the result.
On Thu, Oct 13, 2011 at 1:22 PM, Michal Vyskocil <mvyskocil(a)suse.cz> wrote:
I have packaged the PyV8  as python-pyv8 . It is a python wrapper
for Google's V8 engine. To be sane and allow the future commit into the
openSUSE Factory, I built the svn version (r414 ), which can be built
against v8 126.96.36.199 we have in Factory. As the v8's API is changing very
fast and PyV8 did not have any release during more than a year, one can
only find a working version from svn, as the API changes are reflected,
just not released.
But there is a big issue atm - PyV8 needs to have RTTI and Exceptions
enabled in libv8.so, which is disabled by default. From that reason my
current incarnation rebuilds v8 from scratch without --fno-rtti and
exceptions and the _PyV8.so is statically linked with libv8.so.
So this has to be solved somehow. I see following three opinions sorted
from the less effort (at least for me ;-) to the most one
1.) build system wide v8 with exceptions and rtti
2.) create v8-source package and build python-pyv8 agains it
3.) build it with rtti and exceptions and install it to different
directory and use rpath during linking
The most prefferable would be 1.), just I don't know if this version of
v8 will be compatible with Chromium. Number 2.) can be achieved easyly,
but solves the problem only partially. Number 3.) seems to be the most
complex solution, but expect more work from us.
What do you thinkg about?
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org