build and fortran

[Ian Roxborough]

On Thu, 5 Oct 2000, Matt Challacombe wrote:
> I also tried the binaries and Ian's advice:                              
>      
> 
> "Two ways to add a rule for fortran, one is using
> sn_add_simple_ide_rule in .../etc/sn_prop.cfg
> 
> sn_add_simple_ide_rule Fortran \
>         -suffix-list {.o.f90} \
>         -action "$<" \
>         -tool fortran \
>         -description "Compile a Fortran file." \
>         -file-type Fortran
> 
> replace "-tool fortran" with whatever fortran compiler you are using. "
> 
> I did this, with the approporiate suffixes compiler etc, but 
> SNavigator does not recognice my *.F90 files.  Is their something more
> like a reboot?

What platform are you using?

Note that you say your files have a .F90 extension and the build rule
is looking for .f90 files.  This might cause the problem you are seeing.

Simply change the -suffix-list arguement to {.o.F90} so that it will
pick up your .F90 files.

Also look for:
sn_add_parser fortran \
	-suffix {*.f *.for *.FOR} \
	-brow_cmd $sn_path(bindir)/fbrowser \
	-high_cmd $sn_path(bindir)/fbrowser \
	-brow_switch "" \
	-high_switch "-h" \
	-case 1

You can add .F90 to the -suffix arguement list so they are add to
the SN project, but as BJE says, the fortran parsers don't support
F90.

Assume the fortran parser chokes on the F90 files you can add
them under "others" (files without parsers).  Look for:

 sn_add_parser others -suffix $other_ext

and add *.F90 to the $other_ext variable set just above that line.
(This is all inside the .../etc/sn_prop.cfg file).

Ian.