(In reply to comment #23) > Sure, though clearly separate tarballs are better. The larger question is what > you do about the mozilla-js.pc file; in this case then, xulrunner-dev wouldn't > be providing it, right? Or do you have separate .pc files?
$ apt-file show libmozjs-dev | grep pkgconfig libmozjs-dev: /usr/lib/pkgconfig/mozilla-js.pc $ apt-file show xulrunner-dev | grep pkgconfig xulrunner-dev: /usr/lib/pkgconfig/libxul-embedding-unstable.pc xulrunner-dev: /usr/lib/pkgconfig/libxul-embedding.pc xulrunner-dev: /usr/lib/pkgconfig/libxul-unstable.pc xulrunner-dev: /usr/lib/pkgconfig/libxul.pc xulrunner-dev: /usr/lib/pkgconfig/mozilla-gtkmozembed-embedding.pc xulrunner-dev: /usr/lib/pkgconfig/mozilla-gtkmozembed.pc xulrunner-dev: /usr/lib/pkgconfig/mozilla-plugin.pc
(In reply to comment #23)
> Sure, though clearly separate tarballs are better. The larger question is what
> you do about the mozilla-js.pc file; in this case then, xulrunner-dev wouldn't
> be providing it, right? Or do you have separate .pc files?
$ apt-file show libmozjs-dev | grep pkgconfig pkgconfig/ mozilla- js.pc pkgconfig/ libxul- embedding- unstable. pc pkgconfig/ libxul- embedding. pc pkgconfig/ libxul- unstable. pc pkgconfig/ libxul. pc pkgconfig/ mozilla- gtkmozembed- embedding. pc pkgconfig/ mozilla- gtkmozembed. pc pkgconfig/ mozilla- plugin. pc
libmozjs-dev: /usr/lib/
$ apt-file show xulrunner-dev | grep pkgconfig
xulrunner-dev: /usr/lib/
xulrunner-dev: /usr/lib/
xulrunner-dev: /usr/lib/
xulrunner-dev: /usr/lib/
xulrunner-dev: /usr/lib/
xulrunner-dev: /usr/lib/
xulrunner-dev: /usr/lib/