search for: libllvmpy

...e set TOOLNAME which is for building an executable tool not a shared library. You need to set LIBRARYNAME=..., not TOOLNAME=... 4. Fix the name of your project. It currently builds "llvm.so" which is not correct by our naming standards. It should result to something like "libLLVMpy.so" which will be obtained if you set LIBRARYNAME to "LLVMpy" 5. Consider waiting for or modifying this python interface latter to either directly use the (forthcoming) C interface or design the interface to have a similar structure and naming convention. 6. I looked (briefl...

...nsion module with LIBRARYNAME and SHARED_LIBRARY flags. Anyway, I cannot remember the details now so will try again. > 4. Fix the name of your project. It currently builds "llvm.so" which > is not correct by our naming standards. It should result to something > like "libLLVMpy.so" which will be obtained if you set LIBRARYNAME > to "LLVMpy" I'd like to challenge the usefulness of the naming standard here. I see its value in case of system-wide C/C++ libraries (going to /usr/lib/*), but the Python modules go into a Python-specific directory (/usr...

Hi, I've updated the Python LLVM bindings for LLVM 1.5 (attached). I also thought of setting up a CVS repository for this, but before I do that I thought I'd ask if you want to take the Python bindings to the main LLVM CVS? I noticed that the C language bindings would be maintained there. Changes in Python-LLVM: - Updated to match LLVM 1.5 API - Added Windows build support (created