From: "Liu, Ying2" <ying2.liu@intel.com>
To: "Wood, Thomas" <thomas.wood@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: how to build intel-gpu-tools without cairo
Date: Wed, 2 Jul 2014 18:15:03 +0000 [thread overview]
Message-ID: <C91D9A17C2DDEB479E1981A655A205A5481D0078@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <CANkqdn28rXx=_b5boz4ZrkT0yvTse4MrfQk47wBS8oHfZAjZrg@mail.gmail.com>
Thank you so much for your reply
Ying
-----Original Message-----
From: Thomas Wood [mailto:thomas.wood@intel.com]
Sent: Wednesday, July 02, 2014 3:04 AM
To: Liu, Ying2
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] how to build intel-gpu-tools without cairo
On 1 July 2014 19:49, Liu, Ying2 <ying2.liu@intel.com> wrote:
> The latest intel-gpu-tools has dependency on cairo. We don’t use cairo.
>
> Is there any way to build intel-gpu-tools without cairo?
Cairo has been a required dependency since version 1.2. It is used by various tests and tools and therefore there isn't a way to build intel-gpu-tools without it.
>
>
>
> Thank you so much for your help
>
>
>
> Ying
>
>
>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-07-02 18:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 18:49 how to build intel-gpu-tools without cairo Liu, Ying2
2014-07-02 10:03 ` Thomas Wood
2014-07-02 10:26 ` Mateo Lozano, Oscar
2014-07-02 18:15 ` Liu, Ying2 [this message]
2014-07-02 10:59 ` Damien Lespiau
2014-07-03 21:47 Liu, Ying2
2014-07-07 20:52 ` Daniel Vetter
2014-07-07 21:23 ` Liu, Ying2
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C91D9A17C2DDEB479E1981A655A205A5481D0078@ORSMSX114.amr.corp.intel.com \
--to=ying2.liu@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=thomas.wood@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.