- 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
Separate Compilation Last updated June 2, 2022
One of the distinguishing features of OCaml is its support for separate compilation of interfaces and implementations. But there is more to it than just separate compilation. Dependencies can also be expressed independently - if the build tool supports it.
Separate compilation of structfiles and sigfiles is always possible but it is not required.
See also Modules, Split Dependencies