Templatize destination path structure, including executable basename

[mcandre]

Hi, thank you for maintaining xgo! What an incredibly powerful, fast way to build ports for Go apps!

Could we please get an option similar to gox's -output, for customizing the names of the file tree?

For example, I would prefer to place the OS, arch pair information as directories leading up to the application name: windows/amd64/octane.exe

[davidalpert]

I would also like this ability. wonder where this is set...

[davidalpert]

seems to be set in ./docker/base/build.sh which is a complicated shell script so injecting a template might be tricky:

NAME is first set here:

• xgo/docker/base/build.sh

  Lines 131 to 134 in c5ccff8

  	NAME=`basename $1/$PACK`
  	if [ "$OUT" != "" ]; then
  	NAME=$OUT
  	fi

then used throughout:

• e.g.

  xgo/docker/base/build.sh

  Line 310 in c5ccff8

  GOOS=linux GOARCH=amd64 CGO_ENABLED=1 go build $V $X "${T[@]}" --ldflags="$V $LD" $R $BM -o "/build/$NAME-linux-amd64$R`extension linux`" ./$PACK

which allows the post-build step to simply copy ./build/* out of the container.

one idea is to update build.sh so that:

• output is built inside the container to a path with its component parts (e.g. ./build/$OS/$ARCH/$NAME)
• output is recursively pulled out of the container by xgo.go (e.g. copy -r container:/build/* ./tmp)
• xgo.go iterates through the folder structure to pars the OS,ARCH,NAME values out of the file system and pass those component parts to a gotemplate parameter

one of the main reasons I'm interested in this is to be able to generate binaries with a consistent name across platforms.

would be nice to run mytool on every environment after an install rather than mytool-os-arch