3 ms·
Hum, I hadn't, but in retrospect I should have. I've done my share of Qt builds in the past and mkspecs path was often an amusing detail. Didn't solve the probl
by bostik 10y ago
Hum, I hadn't, but in retrospect I should have. I've done my share of Qt builds in the past and mkspecs path was often an amusing detail. Didn't solve the problem though.
But I think I found out at least one thing that goes wrong. I'll provide a github issue report later this weekend but here's the short version:
* The generated #cgo directives for CXXFLAGS are different for desktop and minimal files. Minimal is generated with -I$(QT_INCLUDE_DIR)/QtFoo include paths; desktop is generated with -I$(QT_DIR)/<major.minor>/gcc_64/include/QtFoo paths instead. So headers in desktop build are looked up from library directory paths (and with obviously bad path elements too).
* When building, qtsetup goes for desktop target.
More data coming in via github once I get the exact details sorted out.
- therecipe 10y agoMh, usually the minimal_cgo_* files and the cgo_* files should use the same imports. But the qtsetup won't always re-generate these cgo_* files if the QT_DIR is up to date (there is probably a bug if you use QT_PKG_CONFIG). So I would use `qtminimal` or `qtdeploy` for debugging this, because the minimal_cgo_* files are always re-generate. And you may also want to change `InfoLevel` in `internal/utils/logger.go` to `DebugLevel` and then re-build the cmd/tools to get additional infos. Hope this helps :)