FFI bindings to the LLVM compiler toolkit. We try to stay up to date with LLVM releases. The current version of this package is compatible with at least LLVM 3.2. Please understand that the package may or may not work against older LLVM releases; we don't have the time or resources to test across multiple releases. New in 3.2: Builds against LLVM 3.2, new mid-level Wrapper interface and ST-based pure interface New in 3.0: Builds against LLVM 3.0. New in 0.9.1.1: Builds against LLVM 2.9. New in 0.9.1.0: Util.Memory for memory related intrinsics. New in 0.9.0.0: Adapted to LLVM 2.8 (removed support for Union types).
llvm-base is a tool in the Build Automation category of a tech stack.
No pros listed yet.
No cons listed yet.
What are some alternatives to llvm-base?
A free and open-source package manager designed for the Microsoft development platform. It is also distributed as a Visual Studio extension.
It is a package manager for the Ruby programming language that provides a standard format for distributing Ruby programs and libraries, a tool designed to easily manage the installation of gems, and a server for distributing them.
Bower is a package manager for the web. It offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. There are no system wide dependencies, no dependencies are shared between different apps, and the dependency tree is flat.
With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.