public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Dima Sorkin" <dima.sorkin@gmail.com>
To: john@keays.com.au
Cc: gcc-help@gcc.gnu.org
Subject: Re: getting started
Date: Fri, 01 Aug 2008 14:45:00 -0000	[thread overview]
Message-ID: <e40293600808010745i590f985ajf47040d4d6422f47@mail.gmail.com> (raw)
In-Reply-To: <13765.124.171.130.82.1217562681.squirrel@ensim.smartydns25.com>

> We ended up modifying some of the libraries and got the "C" code to work
> under Visual Studio 6.  We had special libraries for the GNU C and for the
> "C" component of the graphics libraries. All I want is the old fortran to
> work under Visual Studio and call the old graphics library.  The Fortran
> is pure F77.  I got a FTN95 compiler but its a totally new system with a
> long learning curve.

1) -- F2C --
The F2C (from http://www.netlib.org/f2c, both libf2c.a and the executable)
passes compilation on GCC 4.1.2 (that I have) without even one warning,
simply by typing "GNUmake -f makefile.u".
You can add -fPIC option and produce shared library.

2)  -- Your special libs --
If you can compile and use your "special" C code on GCC, then you can work
on any platform GCC is installed on. Otherwise you will be bound to
Visual Studio,
of which I have little knowledge. MinGW project should ensure interoperability
with libraries compiled on Visual Studio. DJGPP (http://www.delorie.com/djgpp/)
should too... Last time I compiled anything on Windows was in 2004, I had to :)

Regards,
  Dima.

      parent reply	other threads:[~2008-08-01 14:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  7:17 John Keays
     [not found] ` <e40293600807311514y14c14a67sdf2aaae0e70cb883@mail.gmail.com>
     [not found]   ` <13765.124.171.130.82.1217562681.squirrel@ensim.smartydns25.com>
2008-08-01 14:45     ` Dima Sorkin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e40293600808010745i590f985ajf47040d4d6422f47@mail.gmail.com \
    --to=dima.sorkin@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=john@keays.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).