I consider this as an important[*] bug. People should not
know about the low level LAPACK/ BLAS implementation.
That's right. I already checked back with the CMake crowd (the
critical lines are automatically created by CMake) and we might find
ourselves in a little bit of a tricky situation
Hi,
On Wed, Mar 26, 2014 at 10:12 AM, Nico Schlömer
nico.schloe...@gmail.com wrote:
I consider this as an important[*] bug. People should not
know about the low level LAPACK/ BLAS implementation.
That's right. I already checked back with the CMake crowd (the
critical lines are automatically
On Sat, Mar 22, 2014 at 1:31 PM, Nico Schlömer nico.schloe...@gmail.com wrote:
No, the 'linker' does not complain.
You're right, it is the CMake dependency checker. The linking is all
right, but there's something amiss with the CMake export files. I'll
investigate.
I think you should find
Thanks for the hints!
If you have access to upstream source, simply set the target properties with:
set_properties(target LINK_INTERFACE_LIBRARIES )
I might. The culprit right now are CMake property settings of the kind
```
set_target_properties(teuchosnumerics PROPERTIES
On Mon, Mar 24, 2014 at 11:18 AM, Nico Schlömer
nico.schloe...@gmail.com wrote:
Thanks for the hints!
If you have access to upstream source, simply set the target properties with:
set_properties(target LINK_INTERFACE_LIBRARIES )
I might. The culprit right now are CMake property settings of
No, the 'linker' does not complain.
You're right, it is the CMake dependency checker. The linking is all
right, but there's something amiss with the CMake export files. I'll
investigate.
Thanks for the comments!
--Nico
On Thu, Mar 20, 2014 at 3:31 PM, Mathieu Malaterre
Hi all,
I'm building a package for a library A that depends on another
library, libB.so (from its dev-version). When installing library A,
the package libb is installed, containing libB.so.7.2 and libB.so.7.
When linking an executable against libA.so, the linker rightfully
complains about a
Le 20/03/2014 13:22, Nico Schlömer a écrit :
Hi all,
I'm building a package for a library A that depends on another
library, libB.so (from its dev-version). When installing library A,
the package libb is installed, containing libB.so.7.2 and libB.so.7.
When linking an executable against
which must depend on libB-dev.
libB-dev is indeed not explicitly listed as a dependency of libA-dev,
mostly because I was under the impression that ${shlibs:Depends} takes
care of this, cf. https://wiki.debian.org/IntroDebianPackaging. Is
that not the case?
Cheers,
Nico
On Thu, Mar 20, 2014
Le 20/03/2014 14:06, Nico Schlömer a écrit :
which must depend on libB-dev.
libB-dev is indeed not explicitly listed as a dependency of libA-dev,
mostly because I was under the impression that ${shlibs:Depends} takes
care of this, cf. https://wiki.debian.org/IntroDebianPackaging. Is
that
Hi
On 3/20/14, Nico Schlömer nico.schloe...@gmail.com wrote:
I'm building a package for a library A that depends on another
library, libB.so (from its dev-version). When installing library A,
the package libb is installed, containing libB.so.7.2 and libB.so.7.
When linking an executable
11 matches
Mail list logo
