Tavin wrote:
On Feb 22, 5:32 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
After taking a look at some of the xpcom makefiles, it would appear
the standalone build is possible. For the benefit of mankind, here is
the solution:
i would like to see a standalone xpcom project, slightly decoupled
from mozilla or at least the browser.
i'd want to be able to compile a lightweight interpreter for use on
servers, as well as a lightweight interpreter linked to Gecko & GTK or
whatever that you could just point at a XUL file. i know about
XULRunner but it is hardly lightweight..
i can't imagine why there wouldn't be a lot of community interest in
this.
i'd say with your post we have a good start on a HOWTO.
-tavin
I see an opportunity here to help the testing task. I am new to Mozilla
technologies but the XPCOM layer looks like a good place to stand and
reach down into other layers to test them.
I also see NSS and NSPR and it seems like having a component version,
READMEs that state the versions of dependencies relied on, and things
such as that could lead to some really good things.
If we ask what a well-defined standalone module looks like, what would
people say? My guess would be:
1) fetchability with client.mk with a MOZ_CO_PROJECT
2) buildability therefrom
3) some TLC for http://wiki.mozilla.org/XPCOM
Other things come to mind, but they can start from the wiki page.
- ray
_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom
