Hard Light Productions Forums

Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: General Battuta on May 25, 2011, 10:27:59 pm

Title: Request for altered build name scheme
Post by: General Battuta on May 25, 2011, 10:27:59 pm
Pursuant to the following user complaint:

Quote
"I figured out what was wrong, was running the wrong .exe in my freespace folder.  Not sure why there are two executable freespace open files named practically the same thing that got installed, but oh well.  One is fs2_open_3_6_12r_INF and the other is fs2_open_3_6_12d_INF, is that normal?"

I would like to open discussion for a new build naming scheme that makes it more clear to users which build they should be using to play.
Title: Re: Request for altered build name scheme
Post by: Shivan Hunter on May 26, 2011, 03:14:38 am
renaming them to "debug" and "release" instead of just "d" and "r" should work imo. one less element of confusion when it's clear just what the mystical "debug build" is.
Title: Re: Request for altered build name scheme
Post by: Jeff Vader on May 26, 2011, 03:25:02 am
"r" and "release" might also be confusing to the most dimwitted of users. I'd opt for a format like "fs2_open_3_6_12.exe" and "fs2_open_3_6_12_DEBUG.exe". With "INF"s and "SSE"s somewhere in the middle.
Title: Re: Request for altered build name scheme
Post by: Dragon on May 26, 2011, 03:47:55 am
Since Inferno is now a standard, I suggest dropping "INF".
Title: Re: Request for altered build name scheme
Post by: karajorma on May 26, 2011, 04:27:32 am
I'd agree with dropping INF and simply having standard and Non_INF builds. Same with SSE2. So you'd have

fs2_open_3_6_12.exe
fs2_open_3_6_12_DEBUG.exe
fs2_open_3_6_12_SSE1.exe
fs2_open_3_6_12_NO-SSE.exe
fs2_open_3_6_12_NON-INF.exe

etc.

Simple, to the point and it makes clear that the builds with extra words are in some way special rather than having the standard builds looking practically the same as all the other special builds you might need to use.

It also makes it blindingly obvious what is meant when you are told to use a debug build.
Title: Re: Request for altered build name scheme
Post by: The E on May 26, 2011, 04:29:44 am
Actually, didn't we sort of agree to drop non-Inf builds completely?
Title: Re: Request for altered build name scheme
Post by: mjn.mixael on May 26, 2011, 09:03:43 am
I'd agree with dropping INF and simply having standard and Non_INF builds. Same with SSE2. So you'd have

fs2_open_3_6_12.exe
fs2_open_3_6_12_DEBUG.exe
fs2_open_3_6_12_SSE1.exe
fs2_open_3_6_12_NO-SSE.exe
fs2_open_3_6_12_NON-INF.exe

etc.

Simple, to the point and it makes clear that the builds with extra words are in some way special rather than having the standard builds looking practically the same as all the other special builds you might need to use.

It also makes it blindingly obvious what is meant when you are told to use a debug build.

This one seems pretty clear to me and gets my vote.
Title: Re: Request for altered build name scheme
Post by: General Battuta on May 26, 2011, 09:05:50 am
I like Kara's scheme (with the obvious addition that we won't need NON-INF as all builds will be INF). But I wonder if the standard build deserves a STANDARD or PLAY tag.
Title: Re: Request for altered build name scheme
Post by: Goober5000 on May 26, 2011, 10:05:17 am
Kara's scheme is the way it used to be, in fact.  I think it started getting abbreviated to just "d" and "r" because people got tired of typing.
Title: Re: Request for altered build name scheme
Post by: Luis Dias on May 26, 2011, 10:11:20 am
I vote for kara's solution too.
Title: Re: Request for altered build name scheme
Post by: Iss Mneur on May 26, 2011, 11:40:59 am
Kara's scheme is the way it used to be, in fact.  I think it started getting abbreviated to just "d" and "r" because people got tired of typing.
Which probably is not a big deal (now anyway) because the build system does all of the renaming for us.

I think Kara's solution is best, and think the build that we want everyone to use should have the shortest, plainest name (which it would have before the INF and the SSE stuff was tacked on because they were experimental).
Title: Re: Request for altered build name scheme
Post by: chief1983 on May 27, 2011, 01:35:31 pm
It also changed because different Visual Studio projects had different default naming schemes.
Title: Re: Request for altered build name scheme
Post by: JGZinv on May 27, 2011, 03:31:17 pm
Not that I have a say in anything, buy as an outside opinion I agree with kara's solution as well.

I know what the d and r is for, but I'll often hit the one I don't want of the two simply because I'm
clicking right along and they look so similar. Expanding it out would help significantly with the minor irritation.