Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Nightly Builds => Topic started by: SirKnightly on December 05, 2009, 01:58:22 pm
-
Here is the nightly for Windows on 05 Dec 2009 - Revision 5700
Group: SSE2
fso-WIN-SSE2-20091205_r5700.7z (http://swc.fs2downloads.com/builds/WIN/fso-WIN-SSE2-20091205_r5700.7z)
MD5Sum (http://swc.fs2downloads.com/builds/WIN/fso-WIN-SSE2-20091205_r5700.md5)
Group: Standard
fso-WIN-Standard-20091205_r5700.7z (http://swc.fs2downloads.com/builds/WIN/fso-WIN-Standard-20091205_r5700.7z)
MD5Sum (http://swc.fs2downloads.com/builds/WIN/fso-WIN-Standard-20091205_r5700.md5)
Group: Inferno_SSE
fso-WIN-Inferno_SSE-20091205_r5700.7z (http://swc.fs2downloads.com/builds/WIN/fso-WIN-Inferno_SSE-20091205_r5700.7z)
MD5Sum (http://swc.fs2downloads.com/builds/WIN/fso-WIN-Inferno_SSE-20091205_r5700.md5)
Group: Inferno_SSE2
fso-WIN-Inferno_SSE2-20091205_r5700.7z (http://swc.fs2downloads.com/builds/WIN/fso-WIN-Inferno_SSE2-20091205_r5700.7z)
MD5Sum (http://swc.fs2downloads.com/builds/WIN/fso-WIN-Inferno_SSE2-20091205_r5700.md5)
------------------------------------------------------------------------
r5699 | Goober5000 | 2009-12-05 01:17:18 -0600 (Sat, 05 Dec 2009) | 1 line
Changed paths:
M /trunk/fs2_open/projects/MSVC_6/Freespace2.dsp
M /trunk/fs2_open/projects/MSVC_6/code.dsp
M /trunk/fs2_open/projects/MSVC_6_Release/Freespace2.dsp
M /trunk/fs2_open/projects/MSVC_6_Release/code.dsp
project file fixes
------------------------------------------------------------------------
r5700 | Wanderer | 2009-12-05 06:01:03 -0600 (Sat, 05 Dec 2009) | 1 line
Changed paths:
M /trunk/fs2_open/code/ai/aicode.cpp
fix for mantis 2016
------------------------------------------------------------------------
-
Ummm. Why are there no debug builds included in the Inferno SSE2 packages?
-
Space. Do we really need debug builds in all of the packages?
I had to cut back. A full set was taking up 100mb a night. This is 44mb as it is.
-
People typically only download one of those packages. Where does this space concern come from? From having to keep old builds around? I don't think anyone minds if old nightlies gets removed after some time, say 3 months?
-
It's also 100mb of upload every build, and yes I keep them around. It's also not a very effective system if you start deleting builds after a little while. You know how far back we've already had to go to track down some bugs. If I start deleting them we lose that. Maybe I just delete some, but it still adds up over time. Also, I make the Windows builds on my main PC, and if it happens to fire up while I'm on it, it sort of gets in the way of some things I might be doing. 100mb takes a while to upload on rural DSL.
-
So how about separating debugs into their own packages? One standard, one inferno.
-
Still 100 mb for a full meal deal upload.
I hope the standard is the SSE implementation. My regular mediafire uploads on the nightlies was only about 66 for SSE/SSE2 for Reg and INF and that included PDBs.
-
Well, you could consider releasing nightlies less often, like once or twice a week.
-
Then they're not really 'nightlies' then :)
-
well, name 'em "weeklies" then :p
-
If the pdb files are required for the debug, why is there one for the regular builds? You could probably reduce the total size by only including those files for the debug builds.
-
They're used by all builds. Even regular builds have errors that report a stack trace, and the pdb file helps convert addresses to symbols so it can still be somewhat useful. The release builds PDBs are much smaller I believe.
-
Wasn't the idea to do full testing on SSE/SSE2 Inferno builds? If so why even do regular SSE/SSE2 builds? Just do SSE/SSE2 Inferno and a standard debug build. Only time a standard debug build should be needed is to confirm an issue isn't Inferno build related. That would cut the builds almost in half. So that is:
SSE2 Inferno
SSE2 Inferno debug
SSE Inferno
SSE Inferno debug
Inferno
Inferno debug
Standard debug.
Non Inferno builds could be available periodically or on request.
-
I don't understand this insistence on phasing out non-INF builds almost entirely before they even put the pilot files in the same place. I don't think we can cut them out that entirely yet.
-
I agree with keeping the normal builds in for now, but unless there are inferno-specific problems we know about that don't include the pilot files we should probably consider dropping the normal sse builds soon...
As far as I've seen they're stable and work fine >.>
-
Well until the strings are cut with non-inferno builds and developers have to start using inferno builds they will continue to use standard builds. Testing wont get done on inferno builds and we will still be here 2 years from now saying we can't move to inferno as standard because it hasn't been tested enough.
-
Well that's because until recently there were several known problems with INF builds (well, it still feels recent to me). If what Inferno testing has gone on lately doesn't reveal any more behavioral differences, then maybe it is time to merge them back into standard. Then I'd definitely be able to cut down the build size :)