| Age | Commit message (Collapse) | Author |
|---|
|
Bug: 78570710
Test: Still builds.
Change-Id: I4a8e58b56e5eb26788d3bcb4e51fbe876bdc04cc
|
|
Clang 6.0.1 update introduced a number of new warnings, failing
werror build. Ignore the -Wcast-qual warning for external/wayland.
Test: m checkbuild
Change-Id: If16b9c46cf477e2db96b052f7f4412004ad1d407
|
|
I added back the MODULE_LICENSE_MIT and NOTICE (dupe of upstream
LICENSE), as those are still required by Android along with the METADATA
file as a more general open source requirement.
The Android.bp file now exports the core Wayland protocol file as a
filegroup, so it can be directly used by codegen steps elsewhere.
I also did some renaming to clarify what the useful targets were, along
with matching changes to the extension protocol Android.bp file in
external/wayland-protocols
Bug: None
Test: master-arc-wm-dev builds, Wayland unit tests pass
Change-Id: Id500642e66bf0b271d1db69c3ca7885dca895e1d
|
|
Bug: 66996870
Test: build with WITH_TIDY=1
Change-Id: Iad6d52bc248ce0bd98947b8461bff574a3f40078
|
|
This is needed by libwayland_service.
Test: libwayland_service can see wayland-client-protocol.h while
building in master-arc-dev branch.
Change-Id: Icb55e4a8151327e7244b1793c967d14e2ccf98ae
|
|
Test: None. libffi is not correct in master.
Change-Id: I721189e57d92ec69f4faa862e9ff0463da72ac06
|
|
Change-Id: I8a1c43f825b3d916689c428d15f0c247039decfa
|
|
|
|
Mostly to make it compliant to new requirement.
|
|
|
|
Android 3p review needs them.
|
|
In prior versions of Android, we needed to emit an explicit dependency
for a special export_includes file (otherwise generated internally to
the Android build system), so that the header files would be generated
before any code outside the library could incldue them.
This dependency was not correct for x86-64 code, as there were two
such export_include files, one under $OUT/obj/..., the other under
$OUT/obj_64/..., and only the first had the headers as a source
dependency.
With the N branch, the Android build system does now have a way to
correctly specify that the generated headers should be a dependency --
they can be added to LOCAL_GENERATED_SOURCES and now all files in that
list will be listed as a dependency, as well as any implementation files
in the same list also being compiled and included in the library.
This patch removes the lines which set up the additional dependencies on
the headers, as that really is an internal detail of the build system,
and now sets LOCAL_GENERATED_SOURCES to include headers as well as
implementation files.
Bug: 65008174
Test: Clean build x86-64
Test: Incremental build with generated files deleted first
Change-Id: Ieb12144401f186e5fedb02fb91c97c722a0d167c
|
|
This change better automates the generation of almost all of the
boilerplate needed when adding a new Wayland protocol.
1) Previously a manually created header in mock_wayland_client/ which
just included a generated header file was needed. This was easily
confused with some kind of problem with the normal protocol headers.
These headers are now generated.
2) Previously the new protocol files would need to be listed in both the
wayland-protocols/Android.mk as well as mock_wayland_client/Android.mk.
I've made changes so that the mock_wayland_client/Android.mk references
the list in wayland-protocols.
3) Adding a new global to wayland_globals meant adding five or six lines
scattered around the .h and the .cpp file. This has now been reduced to
adding just one in the .h file.
4) You also needed to add one line in wayland_unique_ptr.h for every
interface that was added by the protocol where you wanted to use the
unique_ptr<T> wrapper. And you needed to understand which was the right
destructor function to call for the interface. This is now automatically
generated.
After this change, adding a new protocol should be as easy as:
a) Adding the xml file to wayland-protocols/protocol/
b) Referencing it in wayland-protocols/Android.mk (one line)
c) Adding an entry in wayland_globals.h for the global interface(s)
(one line each)
Test: Incremental build from cleanly built parent works
Test: Clean build works (no dependency issues on generated code)
Test: Unit test passes
Test: Play store loads
Bug: None
Change-Id: I705ef9661dc69c9ed9c1cb0cb74832fbec1c4924
|
|
This is the version of wayland used by chrome, which includes a
required update to the wl_touch protocol to v6.
Bug: 33457871
Test: None
Change-Id: I8fe14f1161766e5f5046181473e1d87c547eae74
|
|
Instead the build file now extracts the version from configure.ac. This
makes it easier to uprev by just getting new files without having to
remember to touch Android.mk.
TEST=wayland-version.h defines version "1.11.0" (current version)
Change-Id: Ic7d0054de2e1028c8818ecd4caa441116c65fdae
|
|
This will fix the spurious build breakages
BUG=29996423
TEST=ninja -t query
out/host/linux-x86/obj/EXECUTABLES/wayland_scanner_intermediates/src/scanner.o
Change-Id: I9cf728fab26239d031d1a5814e4ce560f86fbdaa
|
|
Update to the latest version of wayland that is being used in Chrome.
BUG=29131732
TEST=no functional change expected
Change-Id: I9a9d61aae3ded73c3d4adadf191bf8c7c6e005b4
|
|
BUG=b:27346640
TEST=build
Change-Id: I03ebbc781c86b1fa90ae7cb62a6777f051ce8ff4
|
|
Update to the latest version of wayland that is being used in Chrome.
Most importantly, this update adds pointer events necessary for smooth
and kinetic srolling.
BUG=b:26917697
TEST=no functional change expected
Change-Id: Ie4020a3d9ff02b55c41921e1e41d517f54919d9e
|
|
Source files for clients of the libraries could be compiled before the
public/exported headers were generated.
This patch ensures they are generated before a client tries to use them.
Change-Id: Ie47b6e2c41a8e55ae724eae145d7c6b599216d34
|
|
wayland-client will be used by the hardware composer.
libffi is required by libwayland-client.
BUG=b/25324609
TEST=drm_hwcomposer.cpp compiles/links when including "wayland-client.h"
and calling wl_display_connect(NULL)
Change-Id: I2d05e174b5044b11fae798d93ef2fd1090b70f1f
|
