I would very much like to see this implemented...

I'm working on a modular project, with each 3rd-party module in its own workspace (i.e. @project, @moduleA, @moduleB, etc.). All modules need to depend on @project//:core, but when they are imported as external repositories, I cannot build @project//:main (which depends on @moduleA and @moduleB), because @project's workspace cannot resolve @project to itself.

Is self-referencing local repository an acceptable workaround for now? i.e.

workspace(name = "project")

local_repository(
    name = "project",
    path = __workspace_dir__,
)

I've built @project//:main using this solution as well as by replacing @project//:core with @//:core in modules, and while both binaries have the same filesize and work, their checksums are different, which worries me a bit.

Also, when using the self-referencing solution, project-2.params file lists libcore.a twice (once from main directory and once from external/project)... libcore.a is exactly the same in both cases, so hopefully linker is smart enough about it, but again, this worries me a bit.

Allow using workspace name in labels #1248

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions