I've gotten a lot of feedback that the division of libraries into "private" and "public" is quite helpful.
>From what I've heard, there are currently applications using: - libopensm - libosmcomp - libosmvendor - libibcommon Now that it is well understood that these libraries are intended to be private, developers can move away from using them. But, in the meantime it would be helpful if any major planned changes in these could be posted to the list. I've also heard it suggested that it would be easier to avoid some issues with private libraries if they were not in the standard compiler search path. There are pros and cons to deciding to move them, but I thought I would mention the suggestion. Thanks for putting together and publishing the list. - Betsy On Thu, 2008-07-17 at 14:07 +0300, Tziporet Koren wrote: > This is a reminder to review the OFED public libraries. > Specific Qlogic requested to review it before I publish it on the web > > Thanks > Tziporet > > Public: > ======= > * libdat2 > * libdat > * libibcm > * libibverbs > * libibmad > * libibumad > * libsdp > * librdmacm > > Private: > ======== > * libcxgb3 > * libehca > * libipathverbs > * libmlx4 > * libmthca > * libnes > * libibdmcom > * libdaplcma > * libdaplofa > * libibdm > * libibis > * libibmscli > * libopensm > * libosmcomp > * libosmvendor > * libosmvendor_openib > * libumad2sim > * libibcommon > > _______________________________________________ ewg mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg
