Be aware that Subversion will change the modification times on all of your
dlls to the time that they are checked in or checked out (configurable), but
you can not keep the actual modification time.
In my experience this wreaked havoc on our patch build system (every file
looked like it was updated) and broke windows systems by overwriting newer
dlls with older versions that had incorrect timestamps.
Your experience may be different, but I don't think that Subversion is ready
to handle build artifacts yet, and judging by the mailing list archives I've
read through, the maintainers have no interest in supporting users going
down that path or even accepting patches.
-Eric
On 6/13/07, Henrik Sundberg <storangen@gmail.com> wrote:
>
> Hi,
>
> I've just heard that Microsofts C++ compiler generates different obj
> or exe files at each recompilation.
> The problem was said to be that they are storing pointers in maps and
> then generate code while iterating the map. And thus places all
> routines in random order at each recompilation.
>
> 1) Is this true? Both for obj and exe files?
>
> 2) Is this handled well by Subversion? Should I avoid placing binaries
> generated by Microsoft compilers in Subversion?
>
> I intended to place ~300 exe/dll files in one Subversion directory,
> and to recompile and commit them often (every day).
> There are also a couple of thousands of obj files that I might like to
> keep as well.
>
> /$
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Received on Wed Jun 13 23:08:29 2007