Ceres

Another question: Would it be sufficient to only copy the pyrogenesis.exe over to the "gaming PC" in question (where it chrashed), or do I need to copy all folders & files (under 'binaries') from the "developer's laptop" to the "gaming PC"?

Oh, I thought that I need to build so many commits until I find out which one is the last one that works and which one is the first that crashes (top to bottom). So bisect does that for me? How can it know if it crashes?

So I'm back again (for a short while). I just did this: $ git status On branch master Your branch is up to date with 'origin/master'. nothing to commit, working tree clean $ git reset --hard 3815c08 Updating files: 100% (2876/2876), done. HEAD is now at 3815c08292 [Windows] Automated build. And run 'update-workspaces.bat'. Now I will go to VC and build - just to get the hang on it.

Yep, and I don't understand it - yet. But I am really willing to do so. It's good for my personal education, it will be great to be able to help you guys with this wonderful game, and your and others' help and friendliness here is amazing.

Oh my bad. The version on top (HEAD) is the one I used for my build. I've started reading some introduction to git and will hopefully learn faster. Just need to see how I do 'git reset --hard a24b' correctly, so that it works (tomorrow, though). Have a good evening - and thousand thanks for your patience and very helpful hints.

You mean "up", because the latest one (and in this case the working one) is always (by definition) at the top? Ok, I will keep this in mind. The a24bxxxxxx are the revisions and the highlighted numbers in the screenshot the commits, correct? There are many [Windows] Automated builds: https://github.com/0ad/0ad/search?q=[Windows]+Automated+build&type=commits How could I have found by myself the commit (3815c082925df90726f0207edd53497407ebff99) you kindly posted?

And as there are multiple hashes starting with a24b, I get this: $ git reset --hard a24b error: short object ID a24b is ambiguous hint: The candidates are: hint: a24b635c4a tree hint: a24b74f607 tree hint: a24bd63a5c tree hint: a24b03eb7a blob hint: a24b0809f8 blob hint: a24b10fac3 blob hint: a24bbbee9c blob fatal: ambiguous argument 'a24b': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' Hmm, trees and blobs...

Oh, and then I get there, right? https://github.com/0ad/0ad/commits/A24b And under there, I should step down several commits until I come to the one where the build would crash, right? (please forgive me my repetitive questions - just want to do it right ;))

Yep, I use a mixture of console and TortoiseGit GUI. I am still struggling in understanding how I can fetch&merge or pull a certain revision. With git on the console it would be something like But how/where do I get the correct hash of a certain revision I want to build on? And how would I do this with TortoiseGit? The latter does not offer me (via the Pull menu) any option to select a revision or something.

Great, thanks once more! My problem - tortoisegit "did not exit cleanly (exit code 1)" - should be resolved by this: git gc --force git fetch -p But it takes ages, so I delete the local folder completely and start from "scratch": git clone https://gitlab.com/0ad/0ad.git Sorry, please bear with me...

Erm, how do I revert to A24B now? I fear I screwed everything up and will clone fresh. And I have to read & understand more about git repos, commits, etc. It's not clear to me how to checkout source code at a certain commit. EDIT: I have good knowledge in Linux and Windows, and very basic programming skills, but master/head/branches/tags etc. are terra incognita to me. Do you have a good reading source for this, which is understandable by somebody like me?

Ok, thanks. Hmm, now I get a "Unknown compiler version - please run the configure tests and report the results" message when building. Strange, how can the compiler version become unknown, when I have not touched the VC 2017 installation? Oh my, so many questions - I feel very embaressed. There are lots of syntax error messages in the build log. Unfortunately, I cannot remember if there were such on my first build (which works nicely). Well, there were not - the logs is now full of them.

Ok, I guess that I have understood the concept now and can follow your very helpful video with my own TurtoiseGit. However, I have to invoke the context menu on the folder "0ad", i.e. a level higher than shown in your video. But maybe that does no matter. How can I confirm which version I have checked out? I ask, because I have different context menu possibilities, one called "Git GUI Here", the other "TurtoiseGit >", and even some more. I used "Git GUI Here" => Branch => Checkout =>Tag => A23 => Checkout As I am not sure if this was correct, I would like to verify what is really checked out. EDIT: As my understanding correct that I have to invoke the "update-workspaces.bat" script every time I build from another/earlier commit?

That's what @vladislavbelov meant, I guess. Correct? How can I (with TurtoiseSVN) keep the "good" (no crash) checked out files and check out another version in parallel (for comparison)? Sorry to ask these many (noob) questions. It seems that I am asking for a lecture in git etc.

So I compare the first commit for a25 https://github.com/0ad/0ad/commit/934feaa9207b6000f9a319760e865f1e5ff491d8 (no crash) vs. some earlier commit that crashes, i.e. I have to build earlier commits every time and test if they crash/when they do not crash anymore, right? It seems like guessing a number between 1 and 100 my kids ask me about - I would always guess the number in the middle between upper and lower known numbers.

Hence my earlier comment: By this I meant that The official 0.0.24a crashes on the PC as soon as GLSL gets enabled. The official 0.0.24a does not crash on the PC when GLSL is disabled. My own built does not crash on the PC at all (GLSL disabled or enabled). By "PC" I mean this one device with the Intel 605 iGPU, which is the only one, where the official 0.0.24a crashed with GLSL enabled. It is not the laptop which I used to build, but that does not matter, I guess. Now my question is: Is the "only" missing information, at which point (version/commit) the crash disappears/reappears?

Thank you! By the way, I did not use "debug" but "release" for my build. Yes, it works on the PC, where it crashed before. Just for clarity: The "crashy" device is the PC with the Intel 605 iGPU (not the laptop). I am sorry that I obviously have not described this in an understandable way in the beginning. So to confirm: The version that I built works with GLSL enabled even on the PC (Intel 605 iGPU), where the official 0.0.24a version always crashes when GLSL is enabled.

Sorry, I do not understand this. How do I find out which code version was used for the official Windows 0.0.24b release? This would be the "bad" version for git-bisect, right? And irrespective if this was before or after the "good" version? And the version that I checked out (with TurtoiseGit) is my "good" version (as it does not crash), correct? I also struggle with what @vladislavbelov asked: How can I help answering these questions? Thanks for your patience and help!

Is my understanding correct that the version I used on Tuesday to build pyrogenesis is the "good" version, (is it this one: https://github.com/0ad/0ad/commit/3815c082925df90726f0207edd53497407ebff99) that I have to know which version is the one causing the crash ("bad"), which the Windows release 0.0.24a was built on? (how do I know which version was used for this official build?)

Sorry, I was away longer than planned. Where can I find the game installer for the current development version? I checked the Wiki and GitHub Repository, but could not find anything like it.

Ah, ok. I will have to call it a day for today, but I will further work on this in the next days - also great learning for me.

What is a "release build for the SVN version"?

Oh, I am using TurtoiseGit, and there is also TortoiseGitIDiff. I will check... About your other comment: "... but a release build for the SVN version". Sorry, I don't understand what you meant by this. Can you please explain? Thanks.

The release build still crashes on that PC, when GDSL is enabled. It does not crash, when GDSL is disabled. How can I find out? I have some very vague idea about commits etc., but need some more guidance (if your time permits it), so I know what to do. Shall I go back commits and build every time and check when it crashes/does not crash anymore? How do I do this with TurtoiseSVN and VC? Thanks for your patience. EDIT: Ah, found this: https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-update.html EDIT2: As I use TurtoiseGit, this is not applicable for me, though.

Here some screenshots (if this is too much/not wanted/helpful), please let me know, so I would remove them.