Not a issue but a tip...

[shineworld]

The build require libusb-dev to avoid that:

shine@shine:~/android/build/awutils$ make
cc -Wall -o awflash awflash.c -lusb
awflash.c:23:17: fatal error: usb.h: No such file or directory
compilation terminated.
make: *** [awflash] Error 1

Can you add the library requirement on documentation ?

sudo apt-get install libusb-dev

Best regards

[osynge]

In addition to publishing deps:

I suggest the Library include and linking issues many non coders have, could easily be solved with autotools or cmake in preference to a simple Makefile.

Please let me know if your interested in using autotools, I know cmake is said to be better, but I have not learnt it and autoools works just fine, and has a good track record of helping C code remain portable with minimal maintenance. if you got the code to build on "master/trunk" branch I would consider fixing up autotools, as it wont take me much effort to autotool the project, as I have done several.

From a git checkout:

sh bootstrap.sh

and then following these steps, which is identical for a source download:

./configure

make
make install
make rpm

configure would then provide clear error messages about dependencies, and a nice macro system to allow you to abstract the differences between versions of libusb-dev.

My previous autotools work includes the following packages now in redhat's EPEL and debian:

dcap - Client Tools for dCache
dcap-dbg - Debug symbols for dcap
dcap-dev - Client Development Files for dCache
dcap-tunnel-gsi - GSI tunnel for dCache
dcap-tunnel-krb - Kerberos tunnel for dCache
dcap-tunnel-ssl - SSL tunnel for dCache
dcap-tunnel-telnet - Telnet tunnel for dCache
libdcap1 - Client Libraries for dCache

I also made a very old piece of C code I wrote here libsubprocess and publish my code here.