[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[Libevent-users] Something to consider for future
- To: Libevent Users <libevent-users@xxxxxxxx>
- Subject: [Libevent-users] Something to consider for future
- From: Ralph Castain <rhc@xxxxxxxxxxxx>
- Date: Tue, 7 Sep 2010 09:04:46 -0600
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Tue, 07 Sep 2010 11:04:57 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=JLqj91vWBVqc/0OLECupSp7t6JjRWiRbpYnAh9BpjYY=; b=BCeJBQmg40niSs8e/rzFKn+qBrDArFg6bd0rqmnSgC7+YmBKAhiD38ohhhLzRVWnLk X+jdRZZ/fa2BWZFmb1xkH9CdXd1AHJm7Nixh6QuCXXNWyqVnaqYOoX5OMIa/R9uVkaeP PGBLJwrQf775wRh0C4dGkgHqPnDM7gl9DyqYA=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:content-type:content-transfer-encoding:subject:date :message-id:to:mime-version:x-mailer; b=qr3Nplt2Kt6PVkB58KC0ng230x2OWoi36RmUjP4bA7iAGCEDWP4igZmXou5ascVlAf jMr2YCbLKcw4rDYfsJEkpaRRUCNlLgoN7nK4nN0Rk162bTvSAMkPjhC9vfwD6LROrp6n MqtcLjqHDy0IgAtwtHu/adMIcGFasj73RI9l4=
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
Hi folks
As stated in a prior note, I'm working on integrating libevent 2.0 with Open MPI. We actually carry a copy of your code as part of our distribution (respecting all copyright requirements) for two reasons: (a) portability (to ensure that someone building OMPI on their machine has the same version installed), and (b) we need to modify it somewhat to get things working correctly across the broad range of our installed base.
What this necessitates (among other things) is that we "hide" your symbols so that an app that links directly against an installed libevent won't generate conflicts. This is the crux of my current note.
Rather than only having public APIs as public symbols, libevent 2.0 has literally hundreds of public symbols, almost all of which are only intended to be internally accessed. So embedding libevent now requires a rather arduous task of creating hundreds of #define's by hand.
It is my understanding that quite a few software packages also embed libevent in their distributions, so this is a fairly common problem. It would make life much easier, therefore, if you only declared the true public APIs as public symbols, defining all internal-only functions as "static".
Just something to consider as you move forward.
Ralph
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users in the body.