Re: Storing VS binaries in Subversion

On Wednesday 13 June 2007 22:39, Henrik Sundberg wrote:
> I've just heard that Microsofts C++ compiler generates different obj
> or exe files at each recompilation.
[...]
> 1) Is this true? Both for obj and exe files?

Well, considering the __DATE__ and __TIME__ macros that is not surprising.

> 2) Is this handled well by Subversion?

No.

> Should I avoid placing binaries generated by Microsoft compilers in
> Subversion?

I'd consider these intermediate files not worth versioning anyways. You say in
later mails that you want to distribute the files, but do you really need the
object files or would the final binaries (plus the debug databases for MSC)
be enough? In any case, I would consider not mixing those with the source
code because that makes it pretty hard to know if your working copy contains
changes or not. We use a completely separate repository to distribute
executable installations of a program internally. If you want to release, you
either manually copy them over or execute a batch script that does it for
you.

> 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.

"might like" or "will need"?

Uli

-- 
Sator Laser GmbH
Geschäftsführer: Ronald Boers, Amtsgericht Hamburg HR B62 932
**************************************************************************************
           Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org