-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pkl + plz: multi-directory genrule outs #3123
Comments
Regarding the second question, I'm going to answer my own question and post this here for future eyeballs. I just discovered the:
options and the
|
I might suggest wrapping
alternatively you can call this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Howdy. I've started tinkering with
pkl
and am pretty pleased with it (no pun intended), but am running into a few quirks integrating it intoplz
. Using the followingexample.pkl
file:To generate the
.go
files by hand, you run:which emits the following files:
The problem is
loglevel/LogLevel.pkl.go
and mygenrule()
command. TheBUILD.plz
that I'm using now is:and:
If I add
loglevel/LogLevel.pkl.go
toouts
, I get the following error:TwoOne question:loglevel/LogLevel.pkl.go
so I don't need a random build file for every subdirectory? Ideally,outs
would includeloglevel/LogLevel.pkl.go
and it would be copied tologlevel/LogLevel.pkl.go
, but that doesn't appear to be the case.2. My editor's language server doesn't like the missing*.pkl..go
files, so I have to manually generate the.pkl.go
files inmycmd/pkl/
. Is there a way to copy or have symlinks created for the generated files? Something likemycmd/pkl/Config.pkl.go -> ./plz-out/go/src/mycmd/pkl/Config.pkl.go
? Protobuf has a similar problem, iirc.The text was updated successfully, but these errors were encountered: