autogen.sh
author Sam Lantinga
Wed, 07 Feb 2018 14:07:54 -0800
changeset 11850 8d97fd557ba1
parent 10722 30e271a26a02
permissions -rwxr-xr-x
Fixed bug 4060 - Alternative DualShock 4 v2 controller GUID

ayer.3d

I have a DualShock 4 v2 controller with a GUID that's not in the database. There is an existing GUID that is almost identical, with the only difference that I can tell being the reported version string (mine being 8001, database is 8100).

Existing GUID: 050000004c050000cc09000000810000
New GUID: 050000004c050000cc09000001800000

When connected via USB, the GUID matches an existing entry: 030000004c050000cc09000011810000
slouken@0
     1
#!/bin/sh
slouken@0
     2
#
slouken@1376
     3
echo "Generating build information using autoconf"
slouken@0
     4
echo "This may take a while ..."
slouken@0
     5
hadess@10398
     6
srcdir=`dirname $0`
hadess@10398
     7
test -z "$srcdir" && srcdir=.
icculus@10722
     8
cd "$srcdir"
hadess@10398
     9
slouken@0
    10
# Regenerate configuration files
slouken@7232
    11
cat acinclude/* >aclocal.m4
slouken@1564
    12
found=false
slouken@1832
    13
for autoconf in autoconf autoconf259 autoconf-2.59
slouken@1564
    14
do if which $autoconf >/dev/null 2>&1; then $autoconf && found=true; break; fi
slouken@1563
    15
done
slouken@1564
    16
if test x$found = xfalse; then
slouken@1564
    17
    echo "Couldn't find autoconf, aborting"
slouken@1564
    18
    exit 1
slouken@1564
    19
fi
slouken@1380
    20
(cd test; sh autogen.sh)
slouken@0
    21
slouken@0
    22
# Run configure for this platform
slouken@0
    23
echo "Now you are ready to run ./configure"