libuuu/gen/gitversion.h is missing in all recent packaged versions about mfgtools

[nxpfrankli]

tar ball can't correct identify source version. github don't provide customer script to generate it. which is known issue

[joerg-krause]

Why not define a version string in CMakeLists.txt, e.g. using the project() command, and use this version string if no git clone is used? This why, both the source tarball and the git clone will compile.

[Floweynt]

CMakeList.txt can't sync with git tag and commit hash automatically.
github don't support external script to generate tarball.

[joerg-krause]

Maybe I was not clear enough. I've pushed an example to my fork which does apply a version string even when building the source tarball: https://github.com/joerg-krause/mfgtools/tree/gitversion.

[nxpfrankli]

If version upgrade 1.2.128, I have to change CMakeList.txt (project(uuu VERSION 1.2.91)).

[joerg-krause]

Yes. Is it a no-go?

[joerg-krause]

Another solution would be to add a travis rule to automatically publish a release tarball when tagging a commit. Something like this (totally untested!):

jobs:
  include:
    - stage: deploy
      if: tag IS present
      script: skip
      before_deploy:
        - .ci/make_version.sh $TRAVIS_TAG
      deploy:
        provider: releases
        api_key: $GITHUB_OAUTH_TOKEN
        file: mfgtools-$TRAVIS_TAG.tar.gz
        overwrite: true
        skip_cleanup: true
        on:
          tags: true

[nxpfrankli]

but in release page https://github.com/NXPmicro/mfgtools/releases,
source tar ball is generate by github, I am not sure how to replace it with generated by travis-ci

[joerg-krause]

You're right, you cannot overwrite the github source tarball, but you can create your own one and upload it. I've tested it on my fork: https://github.com/joerg-krause/mfgtools. In releases you can see the created tarball uuu_1.2.92.tar.gz.

Note, I am not an expert in Travis. I've just re-used the code from some other project.
Note, this is just a test and I will remove the tarball later.

[nxpfrankli]

but Source code (zip) and Source code (tar.gz), which will cause confuse.

[joerg-krause]

Maybe. However, the automatically generated source tarballs from github have some disadvantages:

1. They can change at any point. The tarballs are generated and cached, once the cash is invalidated, a new tarball is generated by github. This new tarball will have a different checksum. This makes it difficult for package management systems as they rely on a valid checksum. An uploaded release tarball will not change (until you force it).
2. They do not contain submodules.

[Floweynt]

but we can't prevent github to create it. So I don't prefer use tarball at all.

[joerg-krause]

Note that the automatically generated source tarball does not even compile. In my opinion, that is confusing.

[nxpfrankli]

That's problem, we claim tarball is not supported before work out and good solution.