|
a/src/php/00README.txt |
|
b/src/php/00README.txt |
|
... |
|
... |
2 |
|
2 |
|
3 |
Author: Wenqiang Song (wsong.cn, google mail)
|
3 |
Author: Wenqiang Song (wsong.cn, google mail)
|
4 |
|
4 |
|
5 |
This has minimum features for now.
|
5 |
This has minimum features for now.
|
6 |
|
6 |
|
7 |
The sample/ subdirectory has a minimal script which demonstrates the
|
7 |
The php/sample/ subdirectory has a minimal script which demonstrates the
|
8 |
interface.
|
8 |
interface.
|
9 |
|
9 |
|
10 |
Building the extension needs the librcl.a library (recoll-xxx/lib/librcl.a)
|
10 |
Building the extension needs the librcl.a library (recoll-xxx/lib/librcl.a)
|
11 |
to have been built with PIC objects. This will be handled by the Recoll
|
11 |
to have been built with PIC objects.
|
12 |
build system in the future, but, for now, if using gcc, just add -fPIC
|
|
|
13 |
DPIC to LOCALCXXFLAGS inside mk/localdefs, and run "make clean;make" inside
|
|
|
14 |
lib/ . For other compilers, adjust to taste :)
|
|
|
15 |
|
12 |
|
|
|
13 |
Use "configure --enable-pic" in the top Recoll directory, then
|
|
|
14 |
"make". There is no significant disadvantage in using PIC objects for
|
|
|
15 |
everything so you need not bother having different builds for the
|
|
|
16 |
extensions and the programs.
|
|
|
17 |
|
16 |
The recoll/ subdirectory has the C++ code and the build script
|
18 |
The php/recoll/ subdirectory has the C++ code and the build script
|
17 |
(make.sh). You'll need to "make install" after building.
|
19 |
(make.sh). You'll need to "make install" after building.
|
18 |
|
20 |
|
19 |
If you want to clean up the recoll/ directory, you can run phpize --clean
|
21 |
If you want to clean up the php/recoll/ directory, you can run phpize --clean
|
20 |
in there.
|
22 |
in there.
|