Re: [pyxpcom] XULRunner + PyXPCOM
by Mark Hammond other posts by this author
Jan 24 2008 6:26PM messages near this date
view in the new Beta List Site
Re: [pyxpcom] XULRunner + PyXPCOM
|
Re: [pyxpcom] XULRunner + PyXPCOM
> 1) When you say "Something capable of building a binary at one point, on
all
> 3 platforms, at the time of the bounty, would be enough" I'm still a
little
> confused.. Are we talking about pyxpcom building on the trunk on a
particular
> day or some branch or tag like 1.9b2? If one was to patch the heck out of
the
> trunk or some branch to get it to build, and supplied the diffs, would you
> push those patches and pay the bounty or would you expect the bounty
hunter
> to push the patches?Â
The trunk does not need a "massive" number of patches to make it build, and
I'll commit to checking in any patches needed for the trunk to build
"stand-alone" on any platform, on an ongoing basis.
> 2) I guess this is a question for everybody:Â I like the idea of a pyxpcom
> extension but have only explored this for Firefox.. So what is the
fundamental
> difference between a Firefox and Xulrunner extension where FF and
XulRunner are
> from the same codebase?
Think of firefox as simply a huge xulrunner based application - itÂ?s a
pre-written app which includes many components. xulrunner is more of a
skeleton for running such apps.
> Also, I'm wondering if we built the pyxpcom extension from some branch
like 1.9b2,
> what is the likelihood that it would work with an arbitrary nightly
xulrunner
> build? (ie - how isolated is the xpcom/python code from the rest of the
beast?)
"It depends" :) Once stuff builds on a branch, it should continue to do so
as the branch should be fairly stable, certainly wrt the things pyxpcom
cares about. The trunk really doesn't fail that often either - if the
compile error Paul referred to was the only error he saw, then it would
appear to remain very close today. Often trunk failure I see are unrelated
to pyxpcom
[Many hours later after an attempt to check]
As predicted, the trunk itself is defeating me. I get failure at:
creating toolkit/crashreporter/test/Makefile
Creating .deps
Creating ../../dist/include/crashreporter
make[6]: Entering directory
`/c/src/moz_trunk/mozilla/toolkit/crashreporter/google-breakpad/src/common/w
indows'
: No such file or directory/..
Makefile:51: *** commands commence before first target. Stop.
I'm retrying with --disable-tests built, but I fear it will not complete
before I have to leave for a long weekend. I'll catch up again on Monday.
Cheers,
Mark
_______________________________________________
pyxpcom mailing list
pyxpcom@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Thread:
Shane Caraveo
Paul Everitt
Jesus Cea
Shane Caraveo
Paul Everitt
Edward Baafi
Shane Caraveo
Paul Everitt
Paul Everitt
Mark Hammond
Todd Whiteman
Paul Everitt
Edward Baafi
Mark Hammond
Paul Everitt
Todd Whiteman
Mark Hammond
Shane Caraveo
Todd Whiteman
Edward Baafi
Todd Whiteman
Mark Hammond
Todd Whiteman
Edward Baafi
Todd Whiteman
Shane Caraveo
|