-
Notifications
You must be signed in to change notification settings - Fork 440
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmake build support (required for use with LLVM newer than 3.8 release) #5
Comments
SVF was initially developed based on earlier version of LLVM (version 3.2) in which autoconf is still popular. Yes, we have to use CMake later as autoconf will be dropped in 3.8.1. Are you willing to help us make this change? or do you have some samples on how to set up a tiny cmake project using llvm libraries. |
Understood. I'm not sure--I've integrated it with my own cmake-based project but I'm not sure how to best accommodate your projects needs. In particular, many of your components are built as both static libraries as well as loadable modules (for use in opt), and I'm not sure how to best accomplish that with CMake. In my own project I only build SVF as static libraries that I link into my tools... if this is sufficient I'd be happy to share my CMake pieces, they're pretty simple :). (Why was this closed?) |
Hi Will, If possible, could you please send us a patch diff file on top of current SVF repo for CMake build? We could start from there. Thanks |
LLVM deprecated autoconf in favor of CMake around the 3.8 release, which means projects must move to CMake in order to be used with newer versions of LLVM.
Mostly filing issue to track the status of CMake support in SVF :).
Any plans on adding it in order to support continued use with LLVM?
The text was updated successfully, but these errors were encountered: