|
|
Ublas : |
From: Karl Meerbergen (Karl.Meerbergen_at_[hidden])
Date: 2007-04-25 02:54:31
Hi Georg,
This is indeed a good suggestion. It was something Toon, Kresimir and I
agreed upon that should change. I will put it in some time, but the next
month I am fully scheduled. There is actually some more bindings work
that should be (re)done.
Best,
Karl
Georg Baum wrote:
>Hi,
>
>this patch allows to manually override the naming scheme that is used for
>fortran functions in the bindings.
>
>This makes it possible to use fortran libs compiled by e.g. gcc with e.g.
>the MSVC compiler, but it would be useful for other (unknown) compiler
>pairs, too. It would be nice if someone could put this in.
>
>
>Georg
>
>
>------------------------------------------------------------------------
>
>--- boost/numeric/bindings/traits/fortran.h 2003-09-13 12:50:19.000000000 +0200
>+++ boost/numeric/bindings/traits/fortran.h 2007-04-13 10:51:05.000000000 +0200
>@@ -7,6 +7,10 @@
> #ifndef BOOST_NUMERIC_BINDINGS_TRAITS_FORTRAN_H
> #define BOOST_NUMERIC_BINDINGS_TRAITS_FORTRAN_H
>
>+#if defined(BIND_FORTRAN_LOWERCASE_UNDERSCORE) || defined(BIND_FORTRAN_LOWERCASE)
>+// Allow manual override of the defaults, e.g. if you want to use a fortran
>+// lib compiled with gcc from MSVC
>+#else
> // First we need to know what the conventions for linking
> // C with Fortran is on this platform/toolset
> #if defined(__GNUC__) || defined(__ICC) || defined(__sgi) || defined(__COMO__) || defined(__KCC)
>@@ -16,6 +20,7 @@
> #else
> #error do not know how to link with fortran for the given platform
> #endif
>+#endif
>
> // Next we define macro's to convert our symbols to
> // the current convention
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>ublas mailing list
>ublas_at_[hidden]
>http://lists.boost.org/mailman/listinfo.cgi/ublas
>
>