First thing you should consider when shipping third party components is if repackaging is allowed or not. I would suggest you read up the license agreement for berkeley db and see if re-packaging is allowed or not.
I would suggest you have a custom installer. Complete and Custom. This way the novice user can install everything that is required. I feel, that for an end user to worry about finding the installer for Berkelely DB and installing is unfair. Not to forget version incompatibilities.
In case of an experienced user, he can choose the custom and decide to install the other libraries.


hth
Gangadhar
Giorgos Zervas wrote:

Hi everyone,

I am developing a firefox extension which makes use of Berkeley DB. I
would like to know what the best approach is for packing and distributing
my extension on a variety of platforms (initially, windows and linux):

1. dynamically link my component and leave it to the user to download and
install Berkeley DB?

or

2. statically link with Berkeley DB?

Also, can I pack both a .so and .dll version of my extension in the same
.xpi and let firefox load the appropriate one according to the platform
its running on?

Thanks,
Giorgos

PS: I asked this before (but got no response) so apologies for posting
again, I just thought I'd try one more time.

_______________________________________________
Mozilla-xpcom mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-xpcom

Reply via email to