DarPython
|
Size: 1022
Comment: Added quick instructions to build
|
Size: 1673
Comment: Added problems with debuild
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| 2. Download everything else you need {{{ apt-get install python-dev swig autoconf automake1.9 | 2. Download everything else you need {{{ apt-get install python-dev swig autoconf automake1.9 |
| Line 5: | Line 5: |
| 3. go to source directory {{{ cd dar-2.3.0 | 3. go to source directory {{{ cd dar-2.3.0 |
| Line 8: | Line 8: |
| 5. apply the patch {{{ patch -p0 < /path/to/dar-python-*.patch | 5. apply the patch {{{ patch -p0 < /path/to/dar-python-*.patch |
| Line 13: | Line 13: |
| 7. configure it {{{ ./configure --with-python | 7. configure it {{{ ./configure --with-python |
| Line 15: | Line 15: |
| 8. compile it {{{ make | 8. compile it {{{ make |
| Line 17: | Line 17: |
| 8.1 It fails, just do {{{ make | 8.1 If it fails, just do {{{ make |
| Line 19: | Line 19: |
| '''NOTE''': Instructions on how to fix that below | |
| Line 20: | Line 21: |
| 9.1 for a quick test, you can copy the libdar/.libs/libdar.so.4 to /usr/lib/ and go to libdar/bindings/swig/python and run python -c 'from dar import archive' if everything is ok, you'll see {{{ DEBUG: Loading python bindings | 9.1 for a quick test, you can copy the libdar/.libs/libdar.so.4 to /usr/lib/ and go to libdar/bindings/swig/python and run python -c 'from dar import archive' if everything is ok, you'll see {{{ DEBUG: Loading python bindings |
| Line 23: | Line 24: |
| == Fixes == To fix the build error, you need to insert {{{ %import "user_interaction_bind.hpp" }}} just before the {{{ class libdar::int_pycb { ... } }}} in the file {{{src/bindings/swig/libdar.i}}}. |
|
| Line 24: | Line 30: |
| fix the build error | Currently, when running debuild in the directory, the modules will have unresolved symbols. This is because of the compile option {{{--enable-mode=64}}}. There are also problems with the compile flags of swing, so there is still something to do. Manually adding them (-DLIBDAR_MODE=64) to Makefile.am causes the build to faile with swig failing to create infinit_wrap.cpp. -I need to look at that. (MartinBergner) |
- Download the dar source and all depends {{{ apt-get build-dep dar
apt-get source dar }}}
- Download everything else you need {{{ apt-get install python-dev swig autoconf automake1.9
}}}
- go to source directory {{{ cd dar-2.3.0
}}}
get the patch from [http://sourceforge.net/project/downloading.php?group_id=131569filename=dar-python-0.1.0-cvs-2.4.0.patch&47448731 here]
apply the patch {{{ patch -p0 < /path/to/dar-python-*.patch
}}} (Ignore the fail, it doesn't matter)
- Prepare everything so that you compile it {{{aclocal -I m4
autoconf }}}
- configure it {{{ ./configure --with-python
}}}
- compile it {{{ make
}}}
- 8.1 If it fails, just do {{{ make
}}}
NOTE: Instructions on how to fix that below
- install everything where you want it to be
- 9.1 for a quick test, you can copy the libdar/.libs/libdar.so.4 to /usr/lib/ and go to libdar/bindings/swig/python and run python -c 'from dar import archive' if everything is ok, you'll see {{{ DEBUG: Loading python bindings
}}}
Fixes
To fix the build error, you need to insert {{{ %import "user_interaction_bind.hpp" }}} just before the {{{ class libdar::int_pycb { ... } }}} in the file src/bindings/swig/libdar.i.
TODO
Currently, when running debuild in the directory, the modules will have unresolved symbols. This is because of the compile option --enable-mode=64. There are also problems with the compile flags of swing, so there is still something to do. Manually adding them (-DLIBDAR_MODE=64) to Makefile.am causes the build to faile with swig failing to create infinit_wrap.cpp.
-I need to look at that. (MartinBergner)
HomeUserBackup/DarPython (last edited 2008-08-06 16:59:37 by localhost)