also be nice
Cheers
Marcin
On 3 September 2013 19:08, Brad King wrote:
> On 09/03/2013 01:57 PM, Marcin Wojdyr wrote:
>> On 3 September 2013 15:46, Brad King wrote:
>>> One way to do this is to tell CMake that the library uses C++
>>> using the IMPORTED_LINK_INTERFACE_L
On 3 September 2013 15:46, Brad King wrote:
>> I though that the recommended way to deal with it is:
>>
>> set_property(TARGET ${prog} PROPERTY LINKER_LANGUAGE CXX)
>
> This tells CMake that your "main" is provided by C++, but IIUC
> it is still Fortran. You should still be able to link with the
Hello,
What's the best practice for linking Fortran program with C++ library?
The library is external, built using autotools, either dynamic or static.
The problem is that runtime c++ library is not linked when the library
is static.
I though that the recommended way to deal with it is:
set_prope
he rest, we'd take it...
>
> :-)
>
>
> On Wed, Aug 15, 2012 at 11:27 AM, Marcin Wojdyr wrote:
>>
>> I was looking into git history of one file and just noticed this:
>>
>> commit 9db3116226cb99fcf54e936c833953abcde9b729
>> Author: Kitware Robot
>> Dat
I was looking into git history of one file and just noticed this:
commit 9db3116226cb99fcf54e936c833953abcde9b729
Author: Kitware Robot
Date: Mon Aug 13 13:50:14 2012 -0400
Remove CMake-language block-end command arguments
fyi: the script only removed single-line arguments.
A few multili
