Here are what I know:
1. The FRUIT itself is pure FORTRAN. So it should compile in Windows.
If you don't use Rake to build.
You just put the 2 modules into your source directory, and compile it.
2. Ruby and Rake should work on Windows.
However, I think I had something that is not compatible with Windows in the fruit processor, such as making file links. That can be changed to file copy.
Please give it a try, and let me know if anything more I can help.
Thanks
~Andrew Chen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can someone give me a hint how to get fruit running under windows?
Or does a free fortran test framework exist for windows?
As compiler we use openwatcom.
Kind regards,
Sören
I have not tested it on Windows.
Here are what I know:
1. The FRUIT itself is pure FORTRAN. So it should compile in Windows.
If you don't use Rake to build.
You just put the 2 modules into your source directory, and compile it.
2. Ruby and Rake should work on Windows.
However, I think I had something that is not compatible with Windows in the fruit processor, such as making file links. That can be changed to file copy.
Please give it a try, and let me know if anything more I can help.
Thanks
~Andrew Chen
Unfortunatly open watcom does not complitly support f90.
I tried Eclise with gfortran which works quite nice, after changinng some line according to:
http://coding.derkeiler.com/Archive/Fortran/comp.lang.fortran/2008-02/msg00170.html
The rake part does not work at all under windows. I installed ruby and rake but I am not able to install the fruit_processor_gem.
I always get undefined method 'exitstatus' for nil:NilClass.
Regards,
Sören
use fruit_util
comes from a helper FORTRAN module src/fruit_util.f90
You can do the following commands:
groucho: /users/chena/prj/fruit >cd src
groucho: /users/chena/prj/fruit/src >ls
CVS/ fruit.f90 fruit_util.f90* Makefile.obsolete* rakefile*
groucho: /users/chena/prj/fruit/src >ifort -c fruit_util.f90
groucho: /users/chena/prj/fruit/src >ifort -c fruit.f90
groucho: /users/chena/prj/fruit/src >ar cr libfruit.a fruit.o fruit_util.o
groucho: /users/chena/prj/fruit/src >ls
CVS/ fruit.mod fruit_util.f90* fruit_util.o Makefile.obsolete*
fruit.f90 fruit.o fruit_util.mod libfruit.a rakefile*
You can replace ifort with your compiler.
Then the easiest way is to make libfruit.a available in your other codes.
~Andrew Chen
I really don't have much experience on Windows. As I know gem and rake should all run on Windows.
Anyone can make it run on Windows, please let me know.
Here is doing the same thing above with rake on Linux:
groucho: /users/chena/prj/fruit/src >ls
CVS/ fruit.o fruit_util.o Makefile.obsolete*
fruit.f90 fruit_util.f90* libfruit.a rakefile*
groucho: /users/chena/prj/fruit/src >rake clean
(in /develop/unix/products/prj/fruit/src)
build_dir on lib_base_files is obsolete
groucho: /users/chena/prj/fruit/src >ls
CVS/ fruit.f90 fruit_util.f90* Makefile.obsolete* rakefile*
groucho: /users/chena/prj/fruit/src >rake
(in /develop/unix/products/prj/fruit/src)
build_dir on lib_base_files is obsolete
ifort -c -o fruit_util.o fruit_util.f90 -module /develop/unix/products/prj/fruit/build
/users/chena/opt/gem-repository/gems/rake-0.8.1/lib/rake.rb:905: warning: Insecure world writable dir /opt/lsf in PATH, mode 040777
ifort -c -o fruit.o fruit.f90 -module /develop/unix/products/prj/fruit/build
ar cr libfruit.a fruit.o fruit_util.o
groucho: /users/chena/prj/fruit/src >ls
CVS/ fruit.o fruit_util.o Makefile.obsolete*
fruit.f90 fruit_util.f90* libfruit.a rakefile*
groucho: /users/chena/prj/fruit/src >
Five years passed.
FRUIT is working on
windows 7 + FTN95
windows 7 + cygwin gfortran
windows 7 + TDM-gcc gfortran