| OLD | NEW |
| 1 INSTALLATION OVERVIEW | 1 INSTALLATION OVERVIEW |
| 2 ===================== | 2 ===================== |
| 3 | 3 |
| 4 Once libmtp is built and installed, you will have the following files | 4 Once libmtp is built and installed, you will have the following files |
| 5 ($PREFIX is the --prefix option given to the "configure" script and | 5 ($PREFIX is the --prefix option given to the "configure" script and |
| 6 defaults to /usr/local/): | 6 defaults to /usr/local/): |
| 7 | 7 |
| 8 $PREFIX/lib/libmtp.a Static C library | 8 $PREFIX/lib/libmtp.a Static C library |
| 9 $PREFIX/lib/libmtp.so.x.y.z Dynamic C library | 9 $PREFIX/lib/libmtp.so.x.y.z Dynamic C library |
| 10 $PREFIX/lib/libmtp.so.x A link to the library | 10 $PREFIX/lib/libmtp.so.x A link to the library |
| (...skipping 69 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 80 home directory however. Read more about this environment variable | 80 home directory however. Read more about this environment variable |
| 81 here: http://www.visi.com/~barr/ldpath.html | 81 here: http://www.visi.com/~barr/ldpath.html |
| 82 | 82 |
| 83 The shared library comes with different interface version numbers, | 83 The shared library comes with different interface version numbers, |
| 84 for example libmtp.so.4, libmtp.so.5 and so forth. This is used so | 84 for example libmtp.so.4, libmtp.so.5 and so forth. This is used so |
| 85 that both old and new libmtp libraries shall be able to coexist on | 85 that both old and new libmtp libraries shall be able to coexist on |
| 86 the same system. When you compile your programs they will typically | 86 the same system. When you compile your programs they will typically |
| 87 bind to the latest version of the shared library. A link to the | 87 bind to the latest version of the shared library. A link to the |
| 88 latest version is always provided as $PREFIX/lib/libmtp.so. | 88 latest version is always provided as $PREFIX/lib/libmtp.so. |
| 89 | 89 |
| 90 libusb support | 90 libusb Support |
| 91 -------------- | 91 -------------- |
| 92 | 92 |
| 93 This package depends on libusb. Get libusb from sourceforge at: | 93 This package depends on libusb. Get libusb from sourceforge at: |
| 94 | 94 |
| 95 http://www.sourceforge.net/projects/libusb/ | 95 http://www.sourceforge.net/projects/libusb/ |
| 96 | 96 |
| 97 libusb 1.0 and later is preferred for libmtp, but currently also | 97 On Linux, please use the very latest version you can get, between |
| 98 older 0.1.x versions of libusb are supported. | 98 0.1.8 and 0.1.12 a lot of things happened which pertains to |
| 99 | 99 the udev hotplugging support, see below. |
| 100 | |
| 101 libgcrypt support | |
| 102 ----------------- | |
| 103 | |
| 104 The MTPZ extension to libmtp requires libgcrypt to be installed. | |
| 105 | |
| 106 http://www.gnu.org/software/libgcrypt/ | |
| 107 | |
| 108 MTPZ support will not be built unless the configure script finds | |
| 109 libgcrypt. | |
| 110 | 100 |
| 111 | 101 |
| 112 BASIC BUILD PROCEDURE | 102 BASIC BUILD PROCEDURE |
| 113 ===================== | 103 ===================== |
| 114 | 104 |
| 115 To build the package: | 105 To build the package: |
| 116 | 106 |
| 117 % ./configure | 107 % ./configure |
| 118 % make | 108 % make |
| 119 % make install | 109 % make install |
| (...skipping 87 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 207 Then libusb may need to be patched to recognize this hierarchy. | 197 Then libusb may need to be patched to recognize this hierarchy. |
| 208 The 0.1.12 version is the first which is properly fixed. | 198 The 0.1.12 version is the first which is properly fixed. |
| 209 | 199 |
| 210 | 200 |
| 211 | 201 |
| 212 If you cannot run hotplugging | 202 If you cannot run hotplugging |
| 213 ----------------------------- | 203 ----------------------------- |
| 214 | 204 |
| 215 If you have a distro without hotplugging enabled try this as root: | 205 If you have a distro without hotplugging enabled try this as root: |
| 216 | 206 |
| 217 % chmod -R a+w /dev/bus/usb | |
| 218 | |
| 219 Or if it's *really* ancient you could try: | |
| 220 | |
| 221 % chmod -R a+w /proc/bus/usb | 207 % chmod -R a+w /proc/bus/usb |
| 222 | 208 |
| 223 You have to do this again every time you unplug/replug your USB cable | 209 You have to do this again every time you unplug/replug your USB cable |
| 224 or restart the jukebox, every time you quit libnjb and restart it, | 210 or restart the jukebox, every time you quit libnjb and restart it, |
| 225 etc etc etc an alternative is to run libmtp as root which works just fine. | 211 etc etc etc an alternative is to run libmtp as root which works just fine. |
| 226 The problem is to somehow assure that you (ie the current user) always | 212 The problem is to somehow assure that you (ie the current user) always |
| 227 has write access to these files. | 213 has write access on /proc/bus/usb/* |
| 228 | 214 |
| 229 You can find the Linux hotplug project at: | 215 You can find the Linux hotplug project at: |
| 230 http://linux-hotplug.sourceforge.net/ | 216 http://linux-hotplug.sourceforge.net/ |
| 231 | 217 |
| 232 | 218 |
| 233 Compilation for embedded devices | 219 Compilation for embedded devices |
| 234 -------------------------------- | 220 -------------------------------- |
| 235 | 221 |
| 236 Problems with Autoconf complaining about a missing malloc() function | 222 Problems with Autoconf complaining about a missing malloc() function |
| 237 during cross-compilation can be solved with this hack if you're using | 223 during cross-compilation can be solved with this hack if you're using |
| (...skipping 73 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 311 % gmake | 297 % gmake |
| 312 % sudo gmake install | 298 % sudo gmake install |
| 313 | 299 |
| 314 | 300 |
| 315 General Notes: | 301 General Notes: |
| 316 All MTP devices on Solaris 11+ are driven by the usb_mid driver, which | 302 All MTP devices on Solaris 11+ are driven by the usb_mid driver, which |
| 317 will automatically export ugen device interfaces with the correct device | 303 will automatically export ugen device interfaces with the correct device |
| 318 permissions. No special configuration is required. See the usb_mid(7D) | 304 permissions. No special configuration is required. See the usb_mid(7D) |
| 319 and ugen(7D) manpages and /usr/share/doc/libusb/libusb.txt for more | 305 and ugen(7D) manpages and /usr/share/doc/libusb/libusb.txt for more |
| 320 information. | 306 information. |
| OLD | NEW |