2.2.0.9999?

[Tasoulis]

I was lurking in GlideN64 github page and i noticed people posting pictures using version "2.2.0.9999" of PJ64... The latest i manage to find is 2.2.0.3. How can we find the latest one? Also, is it any better?

[zilmar]

it shows that version if it is compiled from the source (https://github.com/project64/project64)

You an see all the changes in the commit history:
https://github.com/project64/project64/commits/master

tho not sure how good that is for a non coder

[ExtremeDude2]

Maybe it should be changed to show the hash? (ex. 2.2.0.d3f4)

[zilmar]

Originally Posted by ExtremeDude2

Maybe it should be changed to show the hash? (ex. 2.2.0.d3f4)

Feel free to make a PR to do that :P

[ExtremeDude2]

I don't have a clue, but I know it is possible.

[HatCat]

I'm fine with the 9999 as-is.

The build-bot builds should maybe be labeling the application title/version after commits, but everybody with the simple success of compiling the source on their own should be fine with the special value of 9999 in the version.

[Tasoulis]

Originally Posted by zilmar

it shows that version if it is compiled from the source (https://github.com/project64/project64)

You an see all the changes in the commit history:
https://github.com/project64/project64/commits/master

tho not sure how good that is for a non coder

Thanks for the reply.

[HatCat]

Originally Posted by ExtremeDude2

I don't have a clue, but I know it is possible.

wow

such brainz

very clue

much smarts

professor doge will cry

[V1del]

GlideN64 does it by executing a shell/batch script on compile which gets the output of git rev-parse and creates a version.h with a pluginversion macro which gets used in the relevant parts I'd guess many other projects do something similar.

I'm def not the one who's going to do a PR for that though

[zilmar]

there is already a script that is most of the way there in project64\Source\Script\UpdateVersion.cmd