Re: build and fortran

Re: 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.

Re: build and fortran

[Ben Elliston]

Hi,

   I've grabbed the SN4.5.2 tarball, and when I ./configure I get the following:
   Configuring for a i686-pc-linux-gnu host.
   *** Cannot configure in source tree.
   *** Make a parallel directory and configure there.   

You need to build in a separate tree to the source tree:

 $ mkdir build && cd build
 $ ../sn-src/configure [options]

   "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. "

This is for building, not parsing.  Look in S-N's project preferences for
the extensions that it recognises as Fortran files (and not that the Fortran
parser doesn't handle F90 yet).

   I did this, with the approporiate suffixes compiler etc, but
   SNavigator does not recognice my *.F90 files.  Is their something more
   like a reboot?

I should hope not!

Hope this helps,

Ben

build and fortran

[Matt Challacombe]

Hi,

I'm trying to get SNavigator to work with fortran90 (I have *.F90s
and they get ccp'ed to *.f90s then compiled) and I'm
having a few problems I'm hoping the list can help me with.  

I've grabbed the SN4.5.2 tarball, and when I ./configure I get the following:

Configuring for a i686-pc-linux-gnu host.
*** Cannot configure in source tree.
*** Make a parallel directory and configure there.   

How to avoid this?  I see an option for suffixes etc with --help,
so this is promising.

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?

Thanks,  Matt