Page 1 of 1

Include version number in compiled executable

PostPosted: Sat Apr 30, 2016 5:08 pm
by sdfgeoff
This is more of a suggestion for Descent Retromod than for the ladder. Pretty much I like to have lots of versions of Descent sitting around. Vanilla rebirth, retromod 1.4, 1.5x3 and so on. Every time I compile though, it just comes out as the executable 'd1x-rebirth.' I would find it amazing if you could change this to be 'd1x-retro' or even better 'd1x-retro-1.5.'
I think this would make it easier to maintain all the different versions of Descent on a system.

Re: Include version number in compiled executable

PostPosted: Sat Apr 30, 2016 10:31 pm
by roncli
Pro Tip: F2 renames files. :)

Re: Include version number in compiled executable

PostPosted: Sun May 01, 2016 2:20 pm
by sdfgeoff
I fully expected F2 not to work, because I run such a weird system, but apparently F2 is standard enough that my file browser knows about it!

Yes, the renaming option exists, but I would like to:
- Differentiate between retro and rebirth without having to remember which I've built
- Avoid renaming files unnecessarily.

Re: Include version number in compiled executable

PostPosted: Sun May 01, 2016 5:55 pm
by Drakona
Sounds great to me!

I'm the first to admit that Retro is a parasite when it comes to the build system. I didn't write it, and I don't even understand it. I barely know how to call it. It's Rebirth's. I have occasionally gone spelunking to try to get the executable to come out 'retro' at the very least, as the name changes annoy me too. I'm sure there's a way that's obvious to someone a bit more versed in such things. Alas, I am not that person. Likely it lurks somewhere in something that scons consumes. . . it's hard for me to justify spending a lot of time figuring it out. Shoot, I haven't even gotten to the point of writing a script to call the build and then rename the file . . . I guess it doesn't annoy me enough. ;)

I'm all for it though . . . if you figure out how . . . let me know. ;)