On Wed, Mar 30, 2016 at 3:19 AM, Aleix Pol wrote:
> On Tue, Mar 29, 2016 at 11:07 AM, Ben Cooksley wrote:
>> On Tue, Mar 29, 2016 at 7:03 PM, Martin Graesslin wrote:
>>> On Tuesday, March 29, 2016 10:13:02 AM CEST Ben Cooksley wrote:
On Tue, Mar 29, 2016 at 11:07 AM, Ben Cooksley wrote:
> On Tue, Mar 29, 2016 at 7:03 PM, Martin Graesslin wrote:
>> On Tuesday, March 29, 2016 10:13:02 AM CEST Ben Cooksley wrote:
>>> Hi Plasma Devs,
>>>
>>> It would appear Plasma Workspace is improperly
On Tue, Mar 29, 2016 at 7:03 PM, Martin Graesslin wrote:
> On Tuesday, March 29, 2016 10:13:02 AM CEST Ben Cooksley wrote:
>> Hi Plasma Devs,
>>
>> It would appear Plasma Workspace is improperly exporting it's targets,
>> leading to build failures. This particularly affects
On Tuesday, March 29, 2016 10:13:02 AM CEST Ben Cooksley wrote:
> Hi Plasma Devs,
>
> It would appear Plasma Workspace is improperly exporting it's targets,
> leading to build failures. This particularly affects Apper, which is
> unable to build on the CI system as a result. Please ensure when
>
On Tue, Mar 29, 2016 at 10:59 AM, Stephen Kelly wrote:
> Ben Cooksley wrote:
>
>> Hi Plasma Devs,
>>
>> It would appear Plasma Workspace is improperly exporting it's targets,
>> leading to build failures. This particularly affects Apper, which is
>> unable to build on the CI
Hi Plasma Devs,
It would appear Plasma Workspace is improperly exporting it's targets,
leading to build failures. This particularly affects Apper, which is
unable to build on the CI system as a result. Please ensure when
exporting targets / finding libraries that the full path to the
library is