|
| 1 | +Installation Instructions |
| 2 | +************************* |
| 3 | + |
| 4 | +Use `./configure; make all; sudo make install' for Unix-like systems. |
| 5 | + |
| 6 | +Depending on your requirements, the following prerequisites are |
| 7 | +needed: |
| 8 | + |
| 9 | +* libelf including header files (for directly reading ELF files) |
| 10 | +* libusb 0.1 or 1.0 (or compatible), including header files |
| 11 | +* libftdi or libftdi1 (for direct access to FTDI devices) |
| 12 | +* libhidapi or libhid (for access to recent Atmel/Microchip dongles) |
| 13 | + |
| 14 | +If the header and/or library files for one of those are found in |
| 15 | +non-default locations, you can add them to configure, e.g. |
| 16 | + |
| 17 | +`./configure CPPFLAGS=-I/opt/local/include LDFLAGS=-L/opt/local/lib' |
| 18 | + |
| 19 | +as an example for MacOS using Macports. MacOS Brew requires |
| 20 | + |
| 21 | +`./configure CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/Cellar' |
| 22 | + |
| 23 | +instead. (LDFLAGS and CPPFLAGS can also be supplied as environment |
| 24 | +variables to configure.) |
| 25 | + |
| 26 | +At the end of the configure script, a configuration summary is issued, |
| 27 | +like this: |
| 28 | + |
| 29 | +Configuration summary: |
| 30 | +---------------------- |
| 31 | +DO HAVE libelf |
| 32 | +DO HAVE libusb |
| 33 | +DO HAVE libusb_1_0 |
| 34 | +DO HAVE libftdi1 |
| 35 | +DON'T HAVE libftdi |
| 36 | +DON'T HAVE libhid |
| 37 | +DO HAVE libhidapi |
| 38 | +DO HAVE pthread |
| 39 | +DISABLED doc |
| 40 | +DISABLED parport |
| 41 | +DISABLED linuxgpio |
| 42 | +DISABLED linuxspi |
| 43 | + |
| 44 | +Make sure all the features you are interested in have been found. |
| 45 | + |
| 46 | +For BSD-like systems, using GNU make (gmake) is not mandatory but |
| 47 | +appears to cause less troubles with the quite complex dependency graph |
| 48 | +that might be produced by autoconf/automake. |
| 49 | + |
| 50 | +For Windows, right now, a toolset like MinGW is required to compile |
| 51 | +AVRDUDE. |
| 52 | + |
| 53 | +Obviously, a working C compiler is needed. Tested compilers so far |
| 54 | +include GCC (in various versions) and Clang. The compiler needs to |
| 55 | +support (at least) C99 language level. For MacOS, either Xcode or the |
| 56 | +(smaller) Xcode Command Line tools are needed, for Windows, some port |
| 57 | +of GCC that supports generating native Windows executables. |
0 commit comments