From: "Brian Gladman" <brg@gladman.plus.com>
To: <gsl-discuss@sources.redhat.com>
Subject: GSL for Windows with Visual Studio 2005
Date: Tue, 17 Apr 2007 12:13:00 -0000 [thread overview]
Message-ID: <92981E909F1842FFAD6763082181214F@Slave> (raw)
I have just updated my files for building GSL 1.9 using Visual Studio 2005
here:
http://fp.gladman.plus.com/computing/gnu_scientific_library.htm
to provide some improvements in the build processes.
The build project can build static libraries and DLLs for 32-bit and 64-bit
versions of WIndows and all of the tests. Sadly they do not work with
Visual Studio Express (because of Microsoft's braindead decision to limit
some facilities in Express) but I can offer built static libraries and DLLs
for win32 that will allow GSL applications to be built with VC++ Express if
anyone is willing to host them.
The only problem is with the Microsoft build (as far as I know) is with the
file fft.c when optimisation is turned on (it is turned off in the build).
Otherwise all the tests pass on all the GSl versions.
The build also works with the Intel compiler although in this case some of
then tests fail for reasons that I have not yet tracked down (IEEE only
fails on denormals).
It is worth noting that Windows DLLs and applications do not share the same
FILE handles and this means that applications that attempt to pass FILE*
parameters to GSL functions within DLLs will fail. To overcome this problem
I have added functions (e.g. gsl_fopen) to the Windows GSL DLLs that yield
FILE* objects that GSL DLLs process correctly.
I would appreciate feedback from users, especially so, if anyone tracks down
why some of the Intel projects fail (it's possible my function to set the
floating point context for Windows is wrong).
My thanks to all contributors to GSL for a truly first class library.
Brian Gladman
reply other threads:[~2007-04-17 12:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=92981E909F1842FFAD6763082181214F@Slave \
--to=brg@gladman.plus.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).