1 | | {{{ |
2 | | It would be quite useful for packagers having a splitting of the two paths |
3 | | instead of supporting --with-ecw and the traditional single dir approach. FHS in |
4 | | Linux for instance would require installing header files under /usr/include/ecw |
5 | | and libraries under /usr/lib. Indeed, ECW sdk should allow installation under an |
6 | | include suddir to avoid name collisions, but that can be done by packagers in |
7 | | any case. |
8 | | }}} |
| 1 | It would be quite useful for packagers having a splitting of the two paths instead of supporting --with-ecw and the traditional single dir approach. |
| 2 | |
| 3 | FHS in Linux for instance would require installing header files under /usr/include/ecw and libraries under /usr/lib. |
| 4 | |
| 5 | Indeed, ECW sdk should allow installation under an include suddir to avoid name collisions, but that can be done by packagers in any case. |