Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
Differences Between Git Repo and Release Archives
We recently compared source code trees from Git and from a downloaded release archive and found many differences. Is that expected? Or did we miss something? Should we expect to get the same results after either is built?
and found many differences
Which differences? The git repo e.g. does not create the CamelCase header files - they are created by a perl script when compiling from git.
Sam Thomsen last edited by Sam Thomsen
There are many files involved, but looking only at directories, here's what we're seeing:
Non-empty dirs in repo, but missing from archive:
qtrepotools (makes sense)
Non-empty dirs in archive, but missing from repo are all include dirs, which makes sense from what you said.
I should add that we're using Qt v5.13.2
One other thing, did you checkout the corresponding tag ?
Otherwise your clone will anyway be more recent, and currently will be checked out on the dev branch which is for Qt 6.
@Sam-Thomsen what git archive exactly ?
There are many out there.
Git tag: v5.13.2
Archive: qt-everywhere-src-5.13.2.tar.xz (MD5 7c04c678d4ecd9e9c06747e7c17e0bb9)
Might be a silly question but are you sure all modules are checked out at that tag ?
@SGaist I think so.
After cloning the repo, we run the following:
git checkout <TAG>
git submodule update --recursive
Could we be missing a step?
Looks good, I would cd in one of the submodule to ensure it's on the correct tag.
Just thought of something, modules like QtWebEngine may have git submodule, did you also check that ?
@SGaist The 4 modules with differences are:
qtcharts (confirmed correct tag)
qtdatavis3d (confirmed correct tag)
qtqa (wrong tag. module only has one tag v184.108.40.206-beta1)
qtxmlpatterns (confirmed correct tag)