If you define XPCONNECT_STANDALONE in your environment before building then xpconnect will not use the caps module (unless someone broke this since last I tried it).

John.

Aleksey wrote:
Hello,
I'm a newbie in the mozilla infrastructure and I am trying to use
XPCOM, JSEngine and XPConnect in standalone versions. Everything looks
very good, but when I was building those, I found out that XPConnect
depends on 'caps'(a package that seems to be quite heavyweight), and
later I found the confirmation in all.dot and
../mozilla/build/unix/modules.mk
xpconnect -> js;
xpconnect -> caps; // ???
xpconnect -> string;
xpconnect -> xpcom;

caps -> necko;
caps -> dom;
...
caps -> plugin;

And then I found the opened bug 183321 on the same problem.

Is there any particularly reason why the dependency exists, and does anybody know a workaround or an easy way to get rid of it?

Thanks.
AC



Reply via email to