[Nexus] More NAPI stuff

[Campbell, Stuart I.]

The real reason for 2.8.12 is that we had a cmake course and the instructor (who is one of the main authors of cmake) told us to never use a version older than 2.8.12!  The version number doesn’t represent how much improved it is! 




On 8/18/15, 2:20 AM, "NeXus on behalf of Eugen Wintersberger" <nexus-bounces at nexusformat.org on behalf of eugen.wintersberger at desy.de> wrote:

>Hi folks,
>
>On 08/18/15 01:21, Herbert J. Bernstein wrote:
>> I think moving up to 2.8.12 would be reasonable -- Herbert
>> 
>> On Mon, Aug 17, 2015 at 5:04 PM, Peterson, Peter F. <petersonpf at ornl.gov> wrote:
>>> After some searching I found a way to find hdf4 on my system.
>>>
>>> What do people think of moving the minimum cmake version to 2.8.12? This
>>> would give a lot more functionality to cmake.
>
>The reason why there is 2.8.8 as the minimum required version is simple:
>it is the CMake version I have at hand on my Wheezy box in my office. On
>my private boxes with Jessie I could go for 3.0.2 ;).
>
>I guess you are suggesting 2.8.12 because it is the version shipped with
>Ubuntu 14.04 ;). Now, being to lazy to compare the docs between 2.8.8
>and 2.8.12, can anyone tell me what would be the additional
>functionality that 2.8.12 provides over 2.8.8?
>
>regards
>  Eugen
>
>
>>>
>>> On 8/17/15, 10:23 AM, "NeXus on behalf of Tobias Richter"
>>> <nexus-bounces at nexusformat.org on behalf of Tobias.Richter at esss.se> wrote:
>>>
>>>>
>>>>> On 17 Aug 2015, at 15:42, Koennecke Mark (PSI) <mark.koennecke at psi.ch>
>>>>> wrote:
>>>>>> I have already recognized this WITH_XXX stuff. There is a bit chaos
>>>>>> concerning the configuration headers. Sometimes the code uses
>>>>>> nxconfig.h
>>>>>> and on other places napiconfig.h. I'am not really sure if this has
>>>>>> historical reasons or if this is done intentionally.
>>>>>> In the former case I would suggest to clean this up and go for a single
>>>>>> configuration header.
>>>>>>
>>>>>
>>>>> I think that this is historical. I never dealt with those config.h
>>>>> files, they came with whatever
>>>>> build system we are using. I think cleaning this up is the right
>>>>> solution. Or do you object, Freddie?
>>>>
>>>> Well, apparently nxconfig.h is generated from scratch by autotools and
>>>> napiconfig.h includes nxconfig.h plus stdint and inttypes, if available
>>>> as determined by the nxconfig.h defines. (It also does some VMS and
>>>> Windows magic that I am not interested in.) But napiconfig.h is the
>>>> fronted file to look at.
>>>>
>>>> That looks like a reasonable thing to do in the autotools world. I cannot
>>>> see nxconfig.h included directly anywhere, but is (correctly) mentioned
>>>> in Makefiles as a dependency.
>>>>
>>>> If there is a way to combine those files (napiconfig.h and nxconfig.h)
>>>> with cmake, that obviously makes things simpler, though. Go for it.
>>>>
>>>> Tobias
>>>> _______________________________________________
>>>> NeXus mailing list
>>>> NeXus at nexusformat.org
>>>> http://lists.nexusformat.org/mailman/listinfo/nexus
>>>>
>>>
>>>
>>> _______________________________________________
>>> NeXus mailing list
>>> NeXus at nexusformat.org
>>> http://lists.nexusformat.org/mailman/listinfo/nexus
>>>
>> _______________________________________________
>> NeXus mailing list
>> NeXus at nexusformat.org
>> http://lists.nexusformat.org/mailman/listinfo/nexus
>> 
>
>-- 
>------------------------------------
>DI. Dr. Eugen Wintersberger
>
>FS-EC
>DESY
>Notkestrasse 85
>D-22607 Hamburg
>Germany
>
>E-Mail: eugen.wintersberger at desy.de
>Telefon: +49-40-8998-1917
>-----------------------------------
>