package config file for windows

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?
  

Thanks in advance


Christophe
	[[alternative HTML version deleted]]

  
------------------------------------------------------------------------

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]]

  
------------------------------------------------------------------------

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?

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]]

  
------------------------------------------------------------------------