On 04/07/2013 22:20, Kristian Høgsberg wrote:
On Thu, Jul 4, 2013 at 12:35 PM,
wrote:
And they must link directly! That is the proper way to do that.
Providing API using these libraries does not mean forcing anyone to
use that. And using a library does require linking to it. Hiding
this depend
On Fri, 05 Jul 2013 10:35:20 -0700
Thiago Macieira wrote:
> On sexta-feira, 5 de julho de 2013 09.26.23, Pekka Paalanen wrote:
> > The color management modules are an example of a weston module, that
> > does not need pixman at all. If you grep through src/cms*.[ch], there
> > is not a single men
Hi,
On 5 July 2013 20:35, Thiago Macieira wrote:
> First, it mentions that Requires.private is *not* used in dynamic linking.
> Then it changes its mind with that last sentence, which is cryptic.
>
> In any case, the actual behaviour is that Requires.private is used in dynamic
> linking. It adds
On sexta-feira, 5 de julho de 2013 09.26.23, Pekka Paalanen wrote:
> The color management modules are an example of a weston module, that
> does not need pixman at all. If you grep through src/cms*.[ch], there
> is not a single mention of "pixman". Why do these modules, if they were
> external, nee
On Thu, 04 Jul 2013 13:18:27 -0700
Thiago Macieira wrote:
> On quinta-feira, 4 de julho de 2013 18.35.16,
> sardemff7+wayl...@sardemff7.net wrote:
> > > Suppose that our headers #include headers from a project whose
> > > headers aren't usually in /usr/include (that is, they require
> > > -I). In
On Thu, Jul 4, 2013 at 12:35 PM, wrote:
> On 04/07/2013 18:25, Thiago Macieira wrote:
>>
>> On quinta-feira, 4 de julho de 2013 10.12.05, Pekka Paalanen wrote:
>>>
>>> On Wed, 3 Jul 2013 18:26:06 -0400
No, it has to be plain Requires. By having pixman and libxkbcommon
headers in o
On quinta-feira, 4 de julho de 2013 18.35.16, sardemff7+wayl...@sardemff7.net
wrote:
> > Suppose that our headers #include headers from a project whose headers
> > aren't usually in /usr/include (that is, they require -I). In order for
> > our users' applications to build, they need to add those -
On 04/07/2013 18:25, Thiago Macieira wrote:
On quinta-feira, 4 de julho de 2013 10.12.05, Pekka Paalanen wrote:
On Wed, 3 Jul 2013 18:26:06 -0400
No, it has to be plain Requires. By having pixman and libxkbcommon
headers in our SDK headers, we expose those dependencies to
applications.
Hi,
On quinta-feira, 4 de julho de 2013 10.12.05, Pekka Paalanen wrote:
> On Wed, 3 Jul 2013 18:26:06 -0400
> > No, it has to be plain Requires. By having pixman and libxkbcommon
> > headers in our SDK headers, we expose those dependencies to
> > applications.
>
> Hi,
>
> could you explain that logi
On Wed, 3 Jul 2013 18:26:06 -0400
Kristian Høgsberg wrote:
> On Mon, Jul 01, 2013 at 05:03:01PM +0200, Quentin Glidic wrote:
> > From: Quentin Glidic
> >
> > Weston headers include pixman and libxkbcommon headers
> > Using Requires.private means that CFLAGS from pixman-1 and
> > xkbcommon are a
On Mon, Jul 01, 2013 at 05:03:01PM +0200, Quentin Glidic wrote:
> From: Quentin Glidic
>
> Weston headers include pixman and libxkbcommon headers
> Using Requires.private means that CFLAGS from pixman-1 and xkbcommon are
> added to weston CFLAGS, while LIBS are added in case of static linking
> o
From: Quentin Glidic
Weston headers include pixman and libxkbcommon headers
Using Requires.private means that CFLAGS from pixman-1 and xkbcommon are
added to weston CFLAGS, while LIBS are added in case of static linking
only. This way, plugins does not have to use them, but will need to do
so exp
12 matches
Mail list logo
