Sat 20 Mar 2010 10:51:50 PM UTC, comment #10:
We've dropped xpcom
|
Tue 07 Oct 2008 03:09:34 PM UTC, comment #9:
The error message is still kind of bogus as it suggests the wrong packages. On Debian it's iceape-dev-bin and probably iceape-dev being needed, while the libxpcom-dev contain glue version 1.9 which we do NOT want to use...
The automatic "finder" for the libs can't use pkg-config as
it wasn't available for 1.8, so we're looking manually, currently
only in /usr/lib/iceape. You may have it somewhere else, try
using --with-xpcom-sdk-dir configure switch with a few dirs, and check that it builds and gets loaded, then let me know.
|
Tue 07 Oct 2008 11:26:32 AM UTC, comment #8:
Now I get "ERROR: No XPCOM development package is installed.", although both lib64xulrunner-devel and (now) lib64xulrunner-unstable-devel are installed.
I admit I prefer it to getting no error and then failing in the build, but it's still not correct.
|
Tue 07 Oct 2008 10:16:55 AM UTC, comment #7:
So I committed a patch to look for libxpcomglue_s.a w/ou using pkg-config. Will just scan /usr/lib/iceape for now, and you can use --with-xpcom-sdk-dir to set to another dir.
There's currently NO check for version (1.8 vs. 1.9) but TODO ocmments in the xpcom.m4 will remind us. THere are other TODO there too.
|
Tue 07 Oct 2008 08:52:12 AM UTC, comment #6:
if you want to use the plugin in 1.8 and 1.9 you should link against 1.8 (e.g. iceape).
Most likely iceape doesnt provide a proper .pc file.
Look at the XPCOM_Glue page on mdc for the flags required:
-lxpcomglue_s -lxpcom -lnspr4
http://developer.mozilla.org/en/XPCOM_Glue
|
Mon 06 Oct 2008 07:26:13 PM UTC, comment #5:
pkg-config doesn't specify the extensions directory for xulrunner, so that is the correct path for the headers. The only way to get the path to the extensions is with the recently added xpcom support.
|
Mon 06 Oct 2008 07:11:46 PM UTC, comment #4:
pkgconfig only comes up with -I/usr/include/xulrunner-sdk-1.9/stable -I/usr/include/nspr4, but not the extensions directory where that single file is.
|
Mon 06 Oct 2008 01:10:34 PM UTC, comment #3:
bwy, does pkg-config work for you ?
I'd keep this a blocker due to the cookie support, which require xpcom. Beside, I belive we want to use libxpcom when available, so default to enabled. See bug #23437.
|
Mon 06 Oct 2008 01:01:34 PM UTC, comment #2:
Sorry, ./configure does indeed suggest to ask a -dev package,
just the name didn't match (xulrunner-1.9-dev vs. xulrunner-dev).
It's common for debian to have a non-versioned -dev... dunno
if xulrunner makes an exception for someone.
|
Mon 06 Oct 2008 12:59:40 PM UTC, comment #1:
Reading the xpcom.m4 macro there seems to be NO attempt at finding the headers manually. It either trust --with-xpcom-incl/--with-xpcom-lib or pkg_config (when available).
I don't even know which headers we needs as the macro doesn't look for any...
Marking as blocker because ./configure complains about that
but its suggested way to fix (install xulrunner-1.9) doesn't
fix it. Note that once I installed apt package 'xulrunner-dev'
(this is debian lenny) ./configure was fixed (thanks to
pkg-config).
$ pkg-config --exists libxul && echo yes
$ apt-get install xulrunner-dev
$ pkg-config --exists libxul && echo yes
yes
$
|
Fri 03 Oct 2008 10:52:13 AM UTC, original submission:
Here, nsIExtensionsManager.h is in /usr/include/xulrunner-sdk-1.9/extensions/, and it's not found.
|