70
70
Judy is now based on the GNU Auto tools. This means that you can do the standard
71
71
configure, make, make check and make install and everything should work, with
72
one minor differnece and a little caviot.
72
one minor difference and a little caveat.
74
Judy is capiable of being built as a 32-bit or a 64-bit library. Therefor you
75
need to tell Judy what you want. You MUST run configure with one of the
74
Judy is capable of being built as a 32-bit or a 64-bit library. Configure
75
will test to detect the native environment and default to that. Therefor if you
76
explicitly want to to compile for the non-native environment you need to tell
77
Judy what you want. You can run ./configure with one of the following flags:
81
If your compiler generates 32-bit code by default, such as x86, and you run
82
configure with --enable-32-bit, your done. You can now run make, make check and
85
If your compiler generates 64-bit code by default, such as Linux IA-64, and you
86
run configure with --enable-64-bit, your done. You can now run make, make check
89
The caviot comes in on machines that support both at 32-bit and 64-bit runtime
82
The caveat comes in on machines that support both at 32-bit and 64-bit runtime
90
83
environments such as RISC platforms and x86-64. In this case your compiler will
91
84
either use 32-bit or 64-bit as default. If you plan to use the default you can
92
85
follow the above instructions and be finished.
94
87
However, if you wish to compile for the non-default target type. YOU ARE
95
RESPONSIABLE FOR SETTING THE CORRECT FLAGS! Such as CFLAGS to make your compiler
88
RESPONSIBLE FOR SETTING THE CORRECT FLAGS! Such as CFLAGS to make your compiler
96
89
switch modes LDFLAGS to make your linker behave, etc.
98
91
For example: On HP-UX PA-RISC the compiler generates 32-bit code by default. If
99
I wish to stick with the defautls I can build Judy by:
100
./configure --enable-32-bit
92
I wish to stick with the defaults I can simply build Judy by:
added
removed
README
