This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
On 12/22/2010 02:36 AM, Brice Goglin wrote:
> I'll backport this in 1.1 later, in case somebody wants to fix the
> English speaking.
For the benefit of the Perl and Python bindings efforts, it would be good if
we could query the runtime library for it's API version.
> Le 22/12/2010 09:28, bgoglin_at_[hidden] a écrit :
>> Author: bgoglin
>> Date: 2010-12-22 03:28:55 EST (Wed, 22 Dec 2010)
>> New Revision: 2975
>> URL: https://svn.open-mpi.org/trac/hwloc/changeset/2975
>> Add a FAQ entry about HWLOC_API_VERSION
>> Text files modified:
>> trunk/doc/hwloc.doxy | 36 ++++++++++++++++++++++++++++++++++++
>> 1 files changed, 36 insertions(+), 0 deletions(-)
>> Modified: trunk/doc/hwloc.doxy
>> --- trunk/doc/hwloc.doxy (original)
>> +++ trunk/doc/hwloc.doxy 2010-12-22 03:28:55 EST (Wed, 22 Dec 2010)
>> @@ -1294,5 +1294,41 @@
>> (that may for instance be transmitted between applications through a socket).
>> +\section faq_upgrade How do I handle API upgrades?
>> +The hwloc interface is extended with every new major release.
>> +Any application using the hwloc API should be prepared to check at
>> +compile-time whether some features are available in the currently
>> +installed hwloc distribution.
>> +To check whether hwloc is at least 1.1, you should use:
>> +#if HWLOC_API_VERSION>= 0x00010100