Qt binding for Go (Golang) with support for Windows / macOS / Linux / FreeBSD / Android / iOS / Sailfish OS / Raspberry Pi / AsteroidOS / Ubuntu Touch / JavaScript / WebAssembly
GNU Lesser General Public License v3.0
10.5k
stars
748
forks
source link
qtdeploy does not support specifying main file #1226
The qtdeploy script does not support the use case of more than 1 entry point in a project. A simple example project can be found here. Additionally the output directory for the build is also not configurable it's just dumped to wherever you are located in deploy. This causes further problems in the above case since the workaround is to switch to the directory where the main.go file is located. the deploy then clutters up the src with the qt DLL's
would it be possible to add the ability to accept a path for both the main go file and the desired output location. I think defaulting to here and deploy is just fine. If you can recommend a fix I have some time ATM to implement it if you like.
The qtdeploy script does not support the use case of more than 1 entry point in a project. A simple example project can be found here. Additionally the output directory for the build is also not configurable it's just dumped to wherever you are located in deploy. This causes further problems in the above case since the workaround is to switch to the directory where the main.go file is located. the deploy then clutters up the src with the qt DLL's
would it be possible to add the ability to accept a path for both the main go file and the desired output location. I think defaulting to here and deploy is just fine. If you can recommend a fix I have some time ATM to implement it if you like.