On Wed, Nov 12, 2008 at 19:07, howszat <cgu0sij02_at_sneakemail.com> wrote:
> Usually no, but when getting close to the final release, before formal
> integration testing its good to revision the actual binary code.
> Otherwise the tested code might not be exactly the same as the
> released code due to some compiler settings not being exactly the same
> between builds (of the same source code).
> In the environment I'm using (a small embedded microcontroller) this
> matters a lot more than on something like .net though.
Then your build process isn't repeatable & reliable. Why isn't the
build script, which controls those compiler settings, also stored in
the repository with the code?
> On Nov 13, 12:20 am, "Brad Stiles" <bradley.sti..._at_gmail.com> wrote:
>> > I have a compiler that completely clears the output folder at the
>> > start of a build.
>>
>> Is it necessary to version control the output folder? If there are
>> only products of compilation/linking in that folder, then you might
>> consider not placing it under version control at all. For instance,
>> when I use Visual Studio, it creates "bin" and "obj" folders when it
>> builds my app, into which it puts the binaries. I don't have those
>> folders under version control.
>>
>> Brad
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscr..._at_tortoisesvn.tigris.org
>> For additional commands, e-mail: users-h..._at_tortoisesvn.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
> For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-11-13 02:13:32 CET