From murdoch at stats.uwo.ca  Sun Sep 14 14:41:40 2008
From: murdoch at stats.uwo.ca (Duncan Murdoch)
Date: Sun, 14 Sep 2008 08:41:40 -0400
Subject: [Rd] package config file for windows
In-Reply-To: <6F0C127F-2354-49E8-B627-4ED6CEA1D5E3@gmail.com>
References: <6A994D5B-AA3B-4C2A-A3DF-2BF82E1D442F@gmail.com>
	<48CC489B.8090904@stats.uwo.ca>
	<6F0C127F-2354-49E8-B627-4ED6CEA1D5E3@gmail.com>
Message-ID: <48CD0684.5060607@stats.uwo.ca>

On 14/09/2008 5:26 AM, Christophe Dutang wrote:
> Thanks for your answer.
> 
> You confirm what I fear, it is not easily possible to test for SSE2  
> support on windows.

> Can I assume there exists inttypes.h on windows platform?

I think you misunderstood.  The test scripts produced by autoconf won't 
necessarily work on Windows, but it's still worth trying.  Just extract 
the tests for SSE2 and inttypes.h from your script on some other 
platform, and adapt them to Windows.  They can probably be shortened, 
because there's less variability.

You can count on Windows using gcc 4.x for current and future versions, 
probably until 5.x becomes commonly used.  I don't know if inttypes.h is 
guaranteed in all of those, but it is currently present.

Duncan Murdoch

> 
> Thanks again
> 
> Christophe
> 
> Le 14 sept. 08 ? 01:11, Duncan Murdoch a ?crit :
> 
>> Christophe Dutang wrote:
>>> Hi,
>>>
>>> I'm maintaining randtoolbox package on CRAN and I wonder how to do  
>>> a  windows config file? I need to test SSE2 instructions support as  
>>> well  as inttypes.h library check.
>>>
>>> Currently I use the trick of 'foreign' package, i.e. I have  
>>> config.win  file with
>>> cp -p src/config.h.win src/config.h
>>> and config.h.win was written manually from config.h.in. There is  
>>> no  test at all on windows.
>>>
>>> In 'writing r extension' on this topic, we find
>>> "
>>> You should bear in mind that the con?gure script may well not work  
>>> on  Windows systems
>>> (this seems normally to be the case for those generated by  
>>> Autoconf,  although simple shell scripts
>>> do work). If your package is to be made publicly available, please   
>>> give enough information for a
>>> user on a non-Unix platform to con?gure it manually, or provide a   
>>> ?configure.win? script to be
>>> used on that platform. (Optionally, there can be a  
>>> ?cleanup.win?  script as well. Both should
>>> be shell scripts to be executed by ash, which is a minimal version  
>>> of  Bourne-style sh.)
>>> "
>>> Which tool do I need to write config script on windows? Do I need  
>>> an  autoconf-cygwin solution? ( http://sources.redhat.com/autobook/autobook/autobook_242.html#SEC242 
>>>    ) or just a port of autoconf available on sourceforge?
>>>
>> I think most configure scripts on Windows were written using a text  
>> editor, i.e. by hand. Windows systems are pretty consistent, so the  
>> kinds of tests and searches that you need to do on *nix aren't  
>> needed. You can assume that the Rtools are installed, but don't rely  
>> on anything else. We're unlikely to drop tools from that collection,  
>> so this advice should last quite a while.
>>
>> Duncan Murdoch
>>> Thanks in advance
>>>
>>>
>>> Christophe
>>> 	[[alternative HTML version deleted]]
>>>
>>>   
>>> ------------------------------------------------------------------------
>>>
>>> ______________________________________________
>>> R-devel at r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>>
>



[Rd] package config file for windows
Duncan Murdoch