Bazel Concepts
Internal
Repository
Package
Target
Label
BUILD files
Dependencies
Visibility
Platforms
Rules
Hermeticity
Directories
Workspace
A project's workspace is the directory where bazel looks for build inputs and BUILD files, and where it stores build outputs. The actual location is obtained with bazel info.
Bin
The actual location is obtained with bazel info.
Genfiles
The actual location is obtained with bazel info.
Testlogs
The actual location is obtained with bazel info.
Execution Root
The actual location is obtained with bazel info.
Install Base
The actual location is obtained with bazel info.
Output Base
The actual location is obtained with bazel info.
Output Path
The actual location is obtained with bazel info.
Package Path
%workspace%. See Workspace.
Repository Cache
The actual location is obtained with bazel info.
Files
Server Log
The actual location is obtained with bazel info.
Command Log
The actual location is obtained with bazel info.
.bazelrc
Project View File
Seems to be this one:
directories:
# Add the directories you want added as source here
# By default, we've added your entire workspace ('.')
.
# Automatically includes all relevant targets under the 'directories' above
derive_targets_from_directories: true
targets:
# If source code isn't resolving, add additional targets that compile it here
additional_languages:
# Uncomment any additional languages you want supported
# android
# dart
# go
# javascript
# kotlin
# python
# scala
# typescript
# Uncomment to run this target before every sync
# gazelle_target: //:gazelle
BUILD File
Starlark
Bazelisk
A bazel runner. as "Bazel binary location" in the Bazel IntelliJ Plugin.
Bazel and IntelliJ
Sync Process
The sync process queries Bazel for information and builds IntelliJ project structure to fid Bazel's model.
If the file is not reachable from Bazel targets, it will show up as unsynced in the IDE.
TODO: https://blog.bazel.build/2019/09/29/intellij-bazel-sync.html