- Guide: rules_ocaml
-
Topics
- Accessibility
- Aggregates
- Aspects
- Bootstrapping
- Caching
- Compilers
- Conditional Builds
- Configuration
- Configurable Defaults
- Configuration Profiles
- Conventions
- Dependencies
- Deployment
- Diagnostics
- Executables
- File Generation
- Interop
- Labels
- Linking
- Maintenance
- Modules (Bazel)
- Modules (OCaml)
- Namespacing
- Offline development
- OPAM
- Optimization
- Packages
- Preprocessing
- Profiles
- Providers
- PPX Support
- Querying
- Repositories
- Refactoring
- Separate Compilation
- Split Dependencies
- Signatures
- Stamping
- Structures
- Targets
- Testing
- Threading
- Toolchains
- Tools
- Troubleshooting
- user.bazelrc
- Visibility
- Workspaces
OPAM Last updated May 4, 2022
OPAM Dependencies
OPAM dependencies specified by passing their names via the deps_opam
attribute.
misc
Some OPAM packages depend on libraries installed on the local system:
-
all of the conf-* libs? e.g. conf-gmp
-
pkg-config is require by something - ctypes?
-
zarith - contains c code and needs libgmp-dev, perl
-
async - ?
-
ctypes etc.
-
something depends on libffi, I forget what. ctypes?
-
perl - needed by zarith
-
etc.