nx-libs/nx-X11/lib/X11/Xutil.h, branch update-workflows

Convert nx-X11/lib/ build flow from imake to autotools.

2017-08-25T08:06:49+00:00

Align files with upstream libX11-1.6.0

2016-10-19T19:40:27+00:00

This commit looks a bit crazy at first glance. It (re-)introduces lots of whitespaces and bad formatting. Explanation: Backporting upstream changes lead to commits being applied out of order. This meant a lot of manual intervention which in turn lead to slight differences between upstream and NX. With this commit these slight differences are minimized which will be of great help when adding further upstream patches.

Tell clang not to report -Wpadded warnings on public headers we can't fix

2016-10-19T19:40:27+00:00

Better to silence the compiler warning than break ABI. Signed-off-by: Alan Coopersmith Backported-to-NX-by: Ulrich Sibiller

libX11: Fixing modifier key range in Xutil.h (Bug #21910)

2016-10-19T19:40:26+00:00

IsModifierKey, defined in include/X11/Xutil.h, is a macro determining, which keys are regarded as modifiers. The constants ISO_Level5_Shift, ISO_Level5_Latch and ISO_Level5_Lock where excluded previously, leaving some Neo2 modifiers functionless in combination with compose. This patch adjusts the range to include the correct, full range of modifier constants. Neo2 Bug 277 X.Org Bug 21910 Signed-off-by: Bodo Graumann Reviewed-by: Daniel Stone Backported-to-NX-by: Ulrich Sibiller

Xutil.h: Fix wrong include path

2016-10-10T20:52:31+00:00

adapt include files to libX11 1.3.4

2016-10-10T20:52:30+00:00

improve header guards

2016-10-10T20:52:29+00:00

Upstream has changed the header guards. We adapt them to prevent double inclusion.

VCS info lines: Remove ancient X.org / XFree86 VCS info line from code files.

2016-07-05T23:09:15+00:00

This has already been started while replacing copyright info in file headers and has now been completed with this commit.

avoid conflicts when mixing own includes with upstream includes

2016-07-01T13:56:28+00:00

We might better change all guard defines with the ones upstream is using but for now this should also work.

X11/nx-X11 clear-up: More places where we need to explicitly distinguish between X11 and nx-X11 namespace regarding header include paths.

2015-12-29T16:41:24+00:00