This is the mail archive of the
gsl-discuss@sources.redhat.com
mailing list for the GSL project.
Bloodshed Dev-Cpp with GSL
- From: Adam Johansen <amj26 at hermes dot cam dot ac dot uk>
- To: GSL <gsl-discuss at sources dot redhat dot com>
- Date: Tue, 15 Jul 2003 17:53:14 +0100
- Subject: Bloodshed Dev-Cpp with GSL
Hello There,
Has anybody on this list managed to make use of the GSL with the
Bloodshed Dev-cpp compiler for Windows[1]?
I've tried using the pre-compiled Visual C++ version, which looks as
though its works by appears to die whenever a gsl function is called
with an "Access Violation (Segmentation Fault)" under Windows XP /
Devcpp 4.9.8.0 / GSL 1.3 although I've made minimal changes to the code
relative to the linux version which runs perfectly (and I don't /think/
any of these should matter, as they don't affect GSL except via the
occasional change of / to \). The first gsl routine which I'm calling is
rng_env_setup() followed by rngT = gsl_rng_default; gsl_rng_allloc(rngT);
Not really knowing that much about Windows programming these days, the
next obvious step appeared to be to try compiling the library from
source. I attempted to import the Visual C project files, changed the
project type from executable to DLL (this was incorrectly detected by
the compiler) and tried compiling. The GSL project doesn't make it very
far before failing with a stream of errors in the "block_source.c" file.
The first of these is a parse error before "FUNCTION" on line 21.
I know I haven't provided a huge amount of detail here, but I'm not sure
what's going to be useful and what's just going to clog up the list so
let me know if there's anything I can usefully tell you.
Thanks in advance for any help you can give,
Adam Johansen
[1] /I know/. I'm attempting to port a perfectly good linux
implementation for my boss.