On 07/19/2010 08:43 PM, Brad King wrote:
Note that if you use the *shared* libblas.so and liblapack.so then
you do not need to list the implementation dependencies explicitly.
Another way to view this is that when you pointed Trilinos at the
blas and lapack libraries to use, you chose the static
On 07/20/2010 09:45 AM, Theodore Papadopoulo wrote:
On 07/19/2010 08:43 PM, Brad King wrote:
Note that if you use the *shared* libblas.so and liblapack.so then
you do not need to list the implementation dependencies explicitly.
This may not be true everywhere or forever...
Actually this
On 07/18/2010 09:10 PM, John Cary wrote:
Thanks for your help with this. I did
INCLUDE(FortranCInterface), but I did not
see in CMakeCache.txt any variables that
might contain the fortran libs needed by
the C/C++ linkers (e.g., libgfortran).
Did I miss something?
The FortranCInterface
So this is very cool.
Somehow it is not quite working for me. My project is entirely
C++ with C and C++ libraries, but it links to a system lapack
and blas that reference the fortran libraries, so my final link
has the errors,
start of long link line
trilinos/lib/libml.a
On 07/19/2010 09:37 AM, John Cary wrote:
So this is very cool.
Thanks!
Somehow it is not quite working for me. My project is entirely
C++ with C and C++ libraries
All the magic I just described is for projects that mix Fortran
and C++ themselves. It will not handle this case because the
Thanks for your response. More below.
On 7/19/2010 9:06 AM, Brad King wrote:
Can I force the addition of these libraries without referencing
them explicitly?
One workaround is to list a dummy .F file just to tell CMake that
Fortran will be involved at link time. I call it a
On 07/19/2010 11:46 AM, John R. Cary wrote:
So the lapack libraries are actually needed as a dependency of
Trilinos, another C++ library, which does the calling of the
symbols, and it must get those right, because if I add them to
the link line, then all links and runs.
Now I happen to know
Thanks very much again for your help. I now have enough
to fix my problem. Some more info below that might be of
general interest.
On 7/19/10 12:43 PM, Brad King wrote:
On 07/19/2010 11:46 AM, John R. Cary wrote:
and I passed the correct fortran, so I also know that what is
here:
--
Message: 4
Date: Thu, 15 Jul 2010 22:49:40 -0400
From: Bill Hoffmanbill.hoff...@kitware.com
Subject: Re: [CMake] Auxiliary fortran link libraries?
To: cmake@cmake.org
Message-ID:4c3fc8c4.4060...@kitware.com
Content-Type: text/plain; charset=ISO-8859-1; format
Is there some way in cmake to get the
auxiliary fortran link libraries? The
ones that one needs to link in if one is
building a C/C++ executable that uses a library
that was created with fortran?
Like libgfortran for gcc?
Thanks...John Cary
___
On 7/15/2010 5:40 PM, John Cary wrote:
Is there some way in cmake to get the
auxiliary fortran link libraries? The
ones that one needs to link in if one is
building a C/C++ executable that uses a library
that was created with fortran?
Like libgfortran for gcc?
Thanks...John Cary
See
11 matches
Mail list logo
