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
When we run gotron-builder on Mac, we get a folder containing a Unix executable file with the name of our app and subfolder called electronjs which contains an Application file called gotron-browser-window. We can run the executable file to start the application locally, but if we try to copy it to another machine without the accompanying gotron-browser-window Application file, it will not run.
We would like the output to be a portable Application file that we could copy to any Mac and run independently. How can we achieve this?
Note: When we attempt to build for windows, we have a similar issue.
The text was updated successfully, but these errors were encountered:
gotron-builder creates one executable e.g. your_app containing the go binary
gotron-builder downloads electron and bundles it with your UI in a directory name electronjs
3: When starting your_app, gotron knows if your are in develop or production mode. When in production mode it will run ./electronjs/gotron-browser-window to bring up electron UI.
So you need to copy the executable your_app+ the folder electronjs together.
But be aware there is actually a bug which might prevent you from doing this, see #27 .
When we run
gotron-builder
on Mac, we get a folder containing a Unix executable file with the name of our app and subfolder calledelectronjs
which contains an Application file calledgotron-browser-window
. We can run the executable file to start the application locally, but if we try to copy it to another machine without the accompanyinggotron-browser-window
Application file, it will not run.We would like the output to be a portable Application file that we could copy to any Mac and run independently. How can we achieve this?
Note: When we attempt to build for windows, we have a similar issue.
The text was updated successfully, but these errors were encountered: