Each toolchain with their file
aleixpol at kde.org
Wed Oct 28 15:33:56 UTC 2015
On Wed, Oct 28, 2015 at 3:37 PM, Aleix Pol <aleixpol at kde.org> wrote:
> On Wed, Oct 28, 2015 at 3:34 PM, Maximiliano Curia <maxy at debian.org> wrote:
>> On 28/10/15 13:01, Aleix Pol wrote:
>>> I'm unsure how to translate your answer into something that will solve
>>> the issue at hand:
>>> Installing libkf5coreaddons-dev installs the cmake file that points to
>>> the tooling in armhf, while what we want is the tooling for amd64 (or
>>> whatever we installed with libkf5coreaddons-bin-dev).
>> That's interesting, I guess that this needs that the lib-bin-dev as
>> Multi-Arch: foreign, and then, why not installing the tools in /usr/bin ?
> Because these tools are never called as suck, just triggered by the
> toolchain when compiling other projects.
Eh... *"as such"
More information about the kubuntu-devel