Hi all,
On Wed, 27 Jun 2018 at 13:50, Emil Velikov wrote:
> On 27 June 2018 at 12:12, Emil Velikov wrote:
> > On 27 June 2018 at 12:01, Michael Tretter wrote:
> >> On Fri, 25 May 2018 08:46:16 +0200, Michael Tretter wrote:
> >>> On Thu, 24 May 2018 17:08:47 +0200, Emre Ucan wrote:
> >>> > The
On 27 June 2018 at 12:12, Emil Velikov wrote:
> On 27 June 2018 at 12:01, Michael Tretter wrote:
>> Hi,
>>
>> On Fri, 25 May 2018 08:46:16 +0200, Michael Tretter wrote:
>>> On Thu, 24 May 2018 17:08:47 +0200, Emre Ucan wrote:
>>> > The example weston.ini file uses source and build
>>> >
On 27 June 2018 at 12:01, Michael Tretter wrote:
> Hi,
>
> On Fri, 25 May 2018 08:46:16 +0200, Michael Tretter wrote:
>> On Thu, 24 May 2018 17:08:47 +0200, Emre Ucan wrote:
>> > The example weston.ini file uses source and build
>> > directory paths. Therefore, it is only useful when
>> > used on
Hi,
On Fri, 25 May 2018 08:46:16 +0200, Michael Tretter wrote:
> On Thu, 24 May 2018 17:08:47 +0200, Emre Ucan wrote:
> > The example weston.ini file uses source and build
> > directory paths. Therefore, it is only useful when
> > used on the same system that is used to build Weston.
> >
> > We
On Thu, 24 May 2018 17:08:47 +0200, Emre Ucan wrote:
> The example weston.ini file uses source and build
> directory paths. Therefore, it is only useful when
> used on the same system that is used to build Weston.
>
> We can use install paths instead of build/source paths
> to fix this problem.
The example weston.ini file uses source and build
directory paths. Therefore, it is only useful when
used on the same system that is used to build Weston.
We can use install paths instead of build/source paths
to fix this problem.
v2 changes:
- use $(westondatadir) instead of $(datadir)
