public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jose Miguel Buenaposada <jmbuena@dcs.qmw.ac.uk>
To: Emmanuel Chomarat <Emmanuel.Chomarat@bigfoot.com>,
	gsl-discuss@sources.redhat.com
Subject: Re: compile pb
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <3B6BC9C5.53755203@dcs.qmw.ac.uk> (raw)
In-Reply-To: <5288446980.20010803215222@bigfoot.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2325 bytes --]

Emmanuel Chomarat wrote:

>   Can any1 help me to compile GSL, or give some way to investigate in
>   the compilation. In the dist you use automake that is  a great
>   product under unix like system, but i'm not sur that this format is
>   human easy understandable. I'have some problems to make a makefile
>   that will be good with borland c++, and i don't know how to generate
>   makefile(except with cygwin but i think it contains some
>   POSIX particularities that i don't have under borland) .

Hello, I started to make the MSVC projects looking into the Makefile.am files.

And yes those files are human readables ...

I can give you some hints in order to proceed:

- First you have to look into the gsl sources root Makefile.am
    The SUBDIRS variable give you the subdirs to be processed and the order
(from left to right).
    So in every Makefile.am file you can find a SUBDIRS variable or not (in
which case you are in
    a leaf dir).

- GSL is built from leafs to root directory and in every leaf dir is built a
pseudo library,
    and all this leaf libraries are linked together in the root dir (or in gsl
dir I can not remember
    now).

- In every Makefile.am in a leaf dir for building a test program you have
something like:

    bin_PROGRAMS= program1

    program1_SOURCES= source1.c source1.h source2.c source2.h
    program1_LDADD=-llibrary1 -llibrary2

So you can just follow more or less the Makefile.am files in order to now how
to proceed.

On the other hand you can just follow the structure of the Visual C++ projects
files and
use it to construct the borland c++ projects files and then export them to
makefiles (is
this possible?).

I hope to be of any help and not to confuse you more ;-).

Jose Miguel.

--
-------------------------------------------------------------------
Jose Miguel Buenaposada Biencinto
Facultad de Informática                  | Computer Science School
Universidad Politécnica de Madrid  (UPM) | Madrid Tech. University.
Campus de Montegancedo s/n
28660 Boadilla del Monte, Madrid (ESPAÑA)| (SPAIN)
Voice    +34 91 336 69 47
Fax      +34 91 352 48 19
e-mail:  jmbuena@dia.fi.upm.es
web   :  http://www.dia.fi.upm.es/~jmbuena
-------------------------------------------------------------------
Yo soy Precario FPU, ¿ y tu ?: http://www.precarios.org



  parent reply	other threads:[~2001-12-19 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Emmanuel Chomarat
2001-12-19 13:20 ` Brian Gough
2001-12-19 13:20 ` Jose Miguel Buenaposada [this message]
2001-12-19 13:20   ` Re[2]: " Emmanuel Chomarat
2001-12-19 13:20     ` Jose Miguel Buenaposada
2001-12-19 13:20       ` Re[2]: " Emmanuel Chomarat
2001-12-19 13:20         ` Brian Gough

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=3B6BC9C5.53755203@dcs.qmw.ac.uk \
    --to=jmbuena@dcs.qmw.ac.uk \
    --cc=Emmanuel.Chomarat@bigfoot.com \
    --cc=gsl-discuss@sources.redhat.com \
    /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).