[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 20000218: Re: add CYGWIN to cfortran.h?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: Re: 20000218: Re: add CYGWIN to cfortran.h?
  • Date: Fri, 18 Feb 2000 09:47:48 -0700
John,

>Date: Fri, 18 Feb 2000 09:42:52 -0700
>From: "John Huddleston" <address@hidden>
>Organization: USDA
>To: "Steve Emmerson" <address@hidden>
>Subject: Re: 20000218: Re: add CYGWIN to cfortran.h? 
>Keywords: 200002181643.JAA04935

In the above message, you wrote:

> For the build of the CFortran interface:
> Modify the cfortran.h file to include the define check
> for the __CYGWIN__  twice.

Why twice?  I created the following

    #if defined(CLIPPERFortran) || defined(__CYGWIN32__)
    #ifndef f2cFortran
    #define f2cFortran
    #endif
    #endif

Where's the other place?

> For the test to work correctly:
> Add the -Dunix and -Df2cFortran definitions to the
> INCLUDES line in the Makefiles in the fortran
> and the nf_test directories.

The above change to the cfortran.h file obviates the need for the
"-Df2cFortran" option.

> For the install to work:
> Edit the rules.make file and add the .exe to the
> BINDIR line for both the destination and the target.

I'm afraid that's one change we won't make because the makefile would
then be useless on true Unix systems.

Regards,
Steve Emmerson   <http://www.unidata.ucar.edu>