You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 16, 2022. It is now read-only.
Bug: difference between zip contents, when the "ResourcesInclude" config setting has a path that is above the main path your building from, and its a windows build.
#98
Closed
joeblew99 opened this issue
Mar 7, 2016
· 2 comments
I am doing a Windows and a Darwin build and getting slightly different folder structure inside the final zip file. The files are all there correctly, its just that with windows build it adds an extra "Parent" folder.
Screenshots to highlight difference (see the Red circle !!!!)
For the Darwin build it works fine. See Screen shot.
For the Windows build, it adds a "Parent", with its sub folder called "toolbin" See Screen shot.
Windows Build:
Darwin Build:
Steps to Reproduce:
The bug is caused when, in the build config, the "ResourcesInclude" has a path that is above the main path your building from, and its a windows build. I my case its the "./../toolbin/*" path that i am referencing in my config.
On your side side, to reproduce the bug, all you need to do is copy my config(s) and bash script(1), and just reference a folder in the "ResourcesInclude" that is above your main terminal path.
I have included all config and scripts below.
The text was updated successfully, but these errors were encountered:
joeblew99
changed the title
when running zip of the build, there is a difference between Windows and Darwin
Bug: difference between zip contents, when the "ResourcesInclude" config setting has a path that is above the main path your building from, and its a windows build.
Mar 7, 2016
I have nailed it down further:
On Windows, when i unzip the windows build zip file, the "Parent" folder does not exist in the output
On OSX, when i unzip that same windows build zip on OSX, the "Parent" folder does exist in the output.
I am doing a Windows and a Darwin build and getting slightly different folder structure inside the final zip file. The files are all there correctly, its just that with windows build it adds an extra "Parent" folder.
Screenshots to highlight difference (see the Red circle !!!!)
For the Darwin build it works fine. See Screen shot.
For the Windows build, it adds a "Parent", with its sub folder called "toolbin" See Screen shot.
Windows Build:
![windows](https://cloud.githubusercontent.com/assets/11999859/13578588/2c160eb8-e499-11e5-9e57-241a9a54ec38.png)
Darwin Build:
![darwin](https://cloud.githubusercontent.com/assets/11999859/13578503/a79e4f60-e498-11e5-9638-522d6370f09e.png)
Steps to Reproduce:
The bug is caused when, in the build config, the "ResourcesInclude" has a path that is above the main path your building from, and its a windows build. I my case its the "./../toolbin/*" path that i am referencing in my config.
On your side side, to reproduce the bug, all you need to do is copy my config(s) and bash script(1), and just reference a folder in the "ResourcesInclude" that is above your main terminal path.
I have included all config and scripts below.
My go env:
My bash script that kicks each off (tool-dist.sh):
my Windows conf (tool-dist-windows.goxc.json):
my Darwin conf (tool-dist-darwin.goxc.json):
The text was updated successfully, but these errors were encountered: