- 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
Visibility Last updated May 14, 2022
All Bazel targets have a
visibility
property that determines accessibility to depending targets. By
default, all targets are private
, which means package-local; only
targets within the same package may "see" (that is, depend on) private targets.