When using go modules, `go build -o <path>` will pick up main package only if it's in the root of repository. Steps to reproduce: 0. Given a go module, where [main](https://github.com/pavel-d/snaptest/blob/master/cli/main.go) package is located in `./cli` subdirectory 1. Clone https://github.com/pavel-d/snaptest 2. `cd snaptest` 2. Run `snapcraft build --use-lxd --debug` Result: ``` snapcraft --use-lxd --debug The LXD provider is offered as a technology preview for early adopters. The command line interface, container names or lifecycle handling may change in upcoming releases. Launching a container. Waiting for container to be ready ...................... status: done snapd 2.43.3 from Canonical✓ refreshed Skipping pull snaptest (already ran) Building snaptest go build -o /root/parts/snaptest/install/bin go build: no main packages to build Failed to run 'go build -o /root/parts/snaptest/install/bin' for 'snaptest': Exited with code 1. Verify that the part is using the correct parameters and try again. snapcraft-snaptest # snapcraft --version snapcraft, version 3.10.1 ``` The `./...` pattern matches all the packages within the current module and `go build` will automatically build main packages in subdirectories. - [x] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)? - [x] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [x] Have you successfully run `./runtests.sh static`? - [ ] Have you successfully run `./runtests.sh tests/unit`? -----