Hi Óscar,> To the developers: maybe it is a good idea to define something like > LLVM_MAJOR_VERSION and LLVM_MINOR_VERSION ? Preferably in llvm-config.hprobably it's best to just go ahead and implement this (with PACKAGE_VERSION being auto-computed from these) and see if anyone objects :) Ciao, Duncan.
On 05/31/2011 12:50, Duncan Sands wrote:> probably it's best to just go ahead and implement this (with PACKAGE_VERSION > being auto-computed from these) and see if anyone objects :But this only works for C++ apps compiled with headers. It's better to implement version to be returned through the API exported from libLLVM.so Yuri
Hi Yuri, On 31/05/11 22:29, Yuri wrote:> On 05/31/2011 12:50, Duncan Sands wrote: >> probably it's best to just go ahead and implement this (with PACKAGE_VERSION >> being auto-computed from these) and see if anyone objects : > > But this only works for C++ apps compiled with headers. > It's better to implement version to be returned through the API exported from > libLLVM.sohow about both? Patches welcome! Ciao, Duncan.
Apparently Analagous Threads
- [LLVMdev] How to identify LLVM version? [updated patch]
- [LLVMdev] How to identify LLVM version? [correction]
- [LLVMdev] llvm fails on MinGW-32 (Windows) because Python is not supported there
- [LLVMdev] llvm fails on MinGW-32 (Windows) because Python is not supported there
- [LLVMdev] llvm fails on MinGW-32 (Windows) because Python is not supported there