2007/6/14, Ulrich Eckhardt <firstname.lastname@example.org>:
> 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.
I'd expect Subversion's binary diff to handle such changes with no
problem at all.
What bothers me is in the snipped part of my description:
"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."
I.e. If the binaries are completely rearranged between recompilations
(due to values of compiler internal pointers), I would expect the diff
to be expensive.
Does anyone have experience from this?
> > 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
I intended to use different repositories for the distributions.
> > There are also a couple of thousands of obj files that I might like to
> > keep as well.
> "might like" or "will need"?
It seems that minimal rebuild info isn't portable between machines
(the vc80.idb file (and more?)). I could save 20 minutes per user
(every day) if the obj-files were portable. But if this can't be done,
I have to make them recompile these from scratch anyway.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Jun 14 10:53:24 2007