I ran into an error while using git bisect
to investigate PR #1051
. I began with the latest master checked out which had just been built successfully. Then I kicked off a bisection and checked out the fs2_open_3_7_4
tag, like so...
On branch master
Your branch is up-to-date with 'origin/master'.
nothing to commit, working directory clean
>git bisect start
>git bisect bad
>git fetch upstream --tags
remote: Counting objects: 486, done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 486 (delta 182), reused 177 (delta 177), pack-reused 293
Receiving objects: 100% (486/486), 122.75 KiB | 0 bytes/s, done.
Resolving deltas: 100% (252/252), completed with 129 local objects.
d60b756..0e99ae7 coverity_scan -> upstream/coverity_scan
* [new tag] fs2_open_3_7_4_RC2 -> fs2_open_3_7_4_RC2
* [new tag] fs2_open_3_7_4_RC3 -> fs2_open_3_7_4_RC3
* [new tag] fs2_open_3_7_4_final -> fs2_open_3_7_4_final
[lots of nightly tags]
>git checkout fs2_open_3_7_4_final
warning: unable to rmdir cmake/external/cotire: Directory not empty
warning: unable to rmdir cmake/external/rpavlik-cmake-modules: Directory not empty
Checking out files: 100% (2923/2923), done.
Note: checking out 'fs2_open_3_7_4_final'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b new_branch_name
HEAD is now at 24a9a12... Automated 3.7.4 Final versioning commit
>git bisect good
Bisecting: a merge base must be tested
[dc708ccbbb61c6dd63307262ffe3be3794a732bb] Merge pull request #547 from Goober5000/game_level_seed
HEAD detached at dc708cc
You are currently bisecting, started from branch 'master'.
(use "git bisect reset" to get back to the original branch)
(use "git add <file>..." to include in what will be committed)
nothing added to commit but untracked files present (use "git add" to track)
Immediately after that, when trying to build, Visual Studio generates a whole bunch of this sort of error:
CUSTOMBUILD : CMake error : The source directory "<project dir>" does not appear to contain CMakeLists.txt.
CMake-gui also displays this error:
CMake Error: The source directory "<project dir>" does not appear to contain CMakeLists.txt.
Specify --help for usage, or press the help button on the CMake GUI.
Where did CMakeLists.txt go, and why?
I have used git bisect
many times successfully in the past and never encountered this error before.