From: Jose Miguel Buenaposada <jmbuena@dcs.qmw.ac.uk>
To: Emmanuel Chomarat <Emmanuel.Chomarat@bigfoot.com>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: compile pb
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <3B6BECD7.AB35D124@dcs.qmw.ac.uk> (raw)
In-Reply-To: <105143841863.20010804131537@bigfoot.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 4633 bytes --]
Emmanuel Chomarat wrote:
> Hello Jose,
> Thanks for this help, i'll try to use your advises, but i saw that
> i have to declare some #define for the compiler:
> i saw WIN32;_NDEBUG;_MBCS;_LIB flags in the msvc libgsl.dsp
> Do you think this flags are good for a build with another win32
> compiler. What are they doing?
I think WIN32 must to be defined for every windows program. On
the other hand VisualC++ defines _MSC_VER, so code or pragmas
specific for this compiler can be added inf a #ifdef _MSC_VER.
Sorry but I don't know so much about the other defines.
Some thing I forgot to say is that we had to add the correct definitions to
the INF, NAN, and things related for the VisualC++, so maybe you have
to do the same for the Borland compiler. Sorry but I have not a gsl tree
here and I don't remember the name of the file in which this stuff is.
> Another question if i want to do a dll(that is different from
> those i can find in a gsl-bin*.zip), how to export all functions
> in the lib, i can be do with some comandline utilities but does a
> flag exist?
Sorry but I can not help in this point, I'm not a MS Windows programing
guru, so maybe somebody else can help here.
Hope that helps.
>
>
> Saturday, August 04, 2001, 12:09:09 PM, you wrote:
>
> JMB> 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) .
>
> JMB> Hello, I started to make the MSVC projects looking into the Makefile.am files.
>
> JMB> And yes those files are human readables ...
>
> JMB> I can give you some hints in order to proceed:
>
> JMB> - First you have to look into the gsl sources root Makefile.am
> JMB> The SUBDIRS variable give you the subdirs to be processed and the order
> JMB> (from left to right).
> JMB> So in every Makefile.am file you can find a SUBDIRS variable or not (in
> JMB> which case you are in
> JMB> a leaf dir).
>
> JMB> - GSL is built from leafs to root directory and in every leaf dir is built a
> JMB> pseudo library,
> JMB> and all this leaf libraries are linked together in the root dir (or in gsl
> JMB> dir I can not remember
> JMB> now).
>
> JMB> - In every Makefile.am in a leaf dir for building a test program you have
> JMB> something like:
>
> JMB> bin_PROGRAMS= program1
>
> JMB> program1_SOURCES= source1.c source1.h source2.c source2.h
> JMB> program1_LDADD=-llibrary1 -llibrary2
>
> JMB> So you can just follow more or less the Makefile.am files in order to now how
> JMB> to proceed.
>
> JMB> On the other hand you can just follow the structure of the Visual C++ projects
> JMB> files and
> JMB> use it to construct the borland c++ projects files and then export them to
> JMB> makefiles (is
> JMB> this possible?).
>
> JMB> I hope to be of any help and not to confuse you more ;-).
>
> JMB> Jose Miguel.
>
> JMB> --
> JMB> -------------------------------------------------------------------
> JMB> Jose Miguel Buenaposada Biencinto
> JMB> Facultad de Informática | Computer Science School
> JMB> Universidad Politécnica de Madrid (UPM) | Madrid Tech. University.
> JMB> Campus de Montegancedo s/n
> JMB> 28660 Boadilla del Monte, Madrid (ESPAÃA)| (SPAIN)
> JMB> Voice +34 91 336 69 47
> JMB> Fax +34 91 352 48 19
> JMB> e-mail: jmbuena@dia.fi.upm.es
> JMB> web : http://www.dia.fi.upm.es/~jmbuena
> JMB> -------------------------------------------------------------------
> JMB> Yo soy Precario FPU, ¿ y tu ?: http://www.precarios.org
>
> --
> Best regards,
> Emmanuel mailto:Emmanuel.Chomarat@bigfoot.com
--
-------------------------------------------------------------------
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
next prev 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
2001-12-19 13:20 ` Re[2]: " Emmanuel Chomarat
2001-12-19 13:20 ` Jose Miguel Buenaposada [this message]
2001-12-19 13:20 ` 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=3B6BECD7.AB35D124@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).