From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Morton, Derek J" <derek.j.morton@intel.com>,
"Wood, Thomas" <thomas.wood@intel.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] Android.mk: Disable tools that do not build for android
Date: Mon, 15 Jun 2015 16:23:41 +0300 [thread overview]
Message-ID: <87h9q95cma.fsf@intel.com> (raw)
In-Reply-To: <2D016F5BA44C744783BA96B1D3EBC5BDA5C9FF@IRSMSX102.ger.corp.intel.com>
On Mon, 15 Jun 2015, "Morton, Derek J" <derek.j.morton@intel.com> wrote:
>>
>>-----Original Message-----
>>From: Thomas Wood [mailto:thomas.wood@intel.com]
>>Sent: Monday, June 15, 2015 2:09 PM
>>To: Morton, Derek J
>>Cc: Intel Graphics Development; Gore, Tim
>>Subject: Re: [PATCH i-g-t] Android.mk: Disable tools that do not build for android
>>
>>On 15 June 2015 at 14:04, Derek Morton <derek.j.morton@intel.com> wrote:
>>> Disable the tools / demo code that do not currently build for android
>>> until they can be fixed.
>>
>>What needs to be fixed?
>>
>
> Intel_reg - Relies on a header file not provided by the Android compiler
...which one?
> Intel_display_crc - Cairo dependency
> Intel_sprite_on - An API difference in the Android i915 driver.
>
> //Derek
>
>>
>>>
>>> Affected tools / demos
>>> intel_reg
>>> intel_display_crc
>>> intel_sprite_on
>>>
>>> Signed-off-by: Derek Morton <derek.j.morton@intel.com>
>>> ---
>>> Android.mk | 2 +-
>>> tools/Android.mk | 2 ++
>>> 2 files changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/Android.mk b/Android.mk
>>> index 1ab3e64..681d114 100644
>>> --- a/Android.mk
>>> +++ b/Android.mk
>>> @@ -1,2 +1,2 @@
>>> -include $(call all-named-subdir-makefiles, lib tests tools benchmarks
>>> demos)
>>> +include $(call all-named-subdir-makefiles, lib tests tools
>>> +benchmarks)
>>>
>>> diff --git a/tools/Android.mk b/tools/Android.mk index
>>> 39f4512..fd2800e 100644
>>> --- a/tools/Android.mk
>>> +++ b/tools/Android.mk
>>> @@ -36,7 +36,9 @@ endef
>>> #================#
>>>
>>> skip_tools_list := \
>>> + intel_display_crc \
>>> intel_framebuffer_dump \
>>> + intel_reg \
>>> intel_reg_dumper \
>>> intel_vga_read \
>>> intel_vga_write
>>> --
>>> 1.9.1
>>>
>>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-15 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 13:04 [PATCH i-g-t] Android.mk: Disable tools that do not build for android Derek Morton
2015-06-15 13:08 ` Thomas Wood
2015-06-15 13:19 ` Morton, Derek J
2015-06-15 13:23 ` Jani Nikula [this message]
2015-06-15 13:38 ` Morton, Derek J
2015-06-15 13:42 ` Daniel Vetter
2015-06-15 14:08 ` Morton, Derek J
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=87h9q95cma.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=derek.j.morton@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.