That's odd. None of the git version I tried on Windows (apparently I had 3) have this --max-count option for rev-parse. Does yours have it? Apparently git describe --tags --abbrev=0 would do the same. That is, find the closest tag reachable from the current commit.

Does the following makes sense to you? Capturing stdout into a variable seems to be rather awkward in a bat file.

:: GitCloneOrPullRepositoryAndCheckoutLatestTag- Clones a Git repository and checks out the latest tag reachable from HEAD
:: Params: %1 gitUrl, %2 destDir
:: F.ex. call :GitCloneAndCheckoutRevision https://github.com/tpaviot/oce.git "%DEPENDENCY_DIR%"
:GitCloneOrPullRepositoryAndCheckoutLatestTag
call cecho.cmd 0 13 "GitCloneOrPullRepositoryAndCheckoutLatestTag"
call :GitCloneOrPullRepository "%1" "%2"
pushd %2
for /f "tokens=*" %%i in ('git describe --tags --abbrev^=0') do set RECENT_TAG=%%i
call cecho.cmd 0 13 "Checking out %RECENT_TAG%"
call git checkout "%RECENT_TAG%"
popd
set RET=%ERRORLEVEL%
exit /b %RET%

Edit: no this is wrong. This would never update to a newer tag if one is created after the repo is already cloned? Or does the pull in GitCloneOrPullRepository take care of that? Can you even pull after checking out a tag?

Edit2: It seems we need to update GitCloneOrPullRepository to git pull origin master instead of merely git pull for this to work.

Uh oh!

Fix build scripts to known good revisions of OpenCOLLADA and OCE #38

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions