-
-
Notifications
You must be signed in to change notification settings - Fork 196
packr2 not parsing flags correctly #141
Comments
I have tried cd'ing into the cmd directory and running |
Can you provide a working example and the output of of the commands with -v? Packr2 follows import paths to find boxes, if you’re not importing a package it won’t find you boxes. If you want the old style, folder walking, then use the skip imports flag. |
Thanks for the hint about imports. I have got this working now but for others stumbling across this.
Here's the basic
I set go module support: |
Although I couldn't get ignore imports to work with the packr2 build command |
I have the same. Flag |
I found Breaking up the command worked though.
|
If someone would like to open a PR to fix this, it would be very welcome, otherwise It’ll be a bit before I can get to this. I’m backed up at work.
…On Jan 18, 2019, 7:38 AM -0500, Thomas Hughes ***@***.***>, wrote:
I found
packr2 --ignore-imports build cmd/main.go would always fail with the error
flag provided but not defined: -ignore-imports
Breaking up the command worked though.
packr2 --ignore-imports build
go build cmd/main.go
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi. I have my application entry point (main.go) in a subdirectory e.g. cmd/main.go and the repo is using go modules. When I run
packr2 build -v cmd/main.go
it complies the binary fine but it cant find the boxes I setup in the main.goDEBU[2019-01-15T09:49:14Z] found 0 boxes
The text was updated successfully, but these errors were encountered: