[LLVMdev] VS build is broken again

Dmitri Makarov nebraskin at yahoo.com
Sun May 18 13:07:22 PDT 2008


If you look at an .sln file, there's a long sequence of digits
associated with every project, something like this
8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942. For the lack of a better word I
called it "encoding".  After I changed the dependencies between
projects in the solution, msvs replaced those numeric sequences by new
ones literally for every project in the solution file. The diff now
includes all such changes of numeric sequences associated with each
project, which are not really relevant to the problem at all.  I don't
think it matters and would work for anyone equally well, but
nevertheless not to confuse you with such a large diff, I think it's
better if someone on your site would just add the dependency I
mentioned before and would check-in his .sln file.

--- Ted Kremenek <kremenek at apple.com> wrote:

> 
> On May 17, 2008, at 11:51 PM, Dmitri Makarov wrote:
> 
> > This in effect adds codegen.lib to the
> > list of libraries linked into clang.exe and solves all the
> unresolved
> > symbol errors in the clang build.  I would submit the diff, but it
> > looks like visual studio changes all the encodings of projects in
> the
> > .sln file, so the diff includes a lot of irrelevant lines.
> 
> Changes all the encodings?  Does this have to do with locale
> settings?
> 



      



More information about the llvm-dev mailing list