search for: 00a0c91bc942

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

.../VS2015/opus.sln +++ b/win32/VS2015/opus.sln @@ -1,7 +1,7 @@  Microsoft Visual Studio Solution File, Format Version 12.00 # Visual Studio 14 -VisualStudioVersion = 14.0.23107.0 +VisualStudioVersion = 14.0.25123.0 MinimumVisualStudioVersion = 10.0.40219.1 Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "opus", "opus.vcxproj", "{219EC965-228A-1824-174D-96449D05F88A}" ProjectSection(ProjectDependencies) = postProject @@ -12,6 +12,9 @@ Project("{8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942}") = "opus", "opus.vcxproj", "{21 EndPro...

...s one extra EndProject line. b) it has 4 lines that start with {4cefbc82-c215-11db-8314-0800200c9a66}. They left from in_flac and useless now. c) According to http://msdn.microsoft.com/en-us/library/hb23x61k(v=vs.80).aspx , the standard GUID for Visual C++ project is 8BC9CEB8-8B4A-11D0-8D11-00A0C91BC942, not the current 4cefbc7c-c215-11db-8314-0800200c9a66 (download SoX or LAME tarball and you'll see 8BC9CEB8-... there). d) Also GUIDs should be uppercase (again, look at SoX or LAME .sln files) -------------- next part -------------- A non-text attachment was scrubbed... Name: sln.zip...

...n cause problems with Apple's Mail program (weird CRLF issues, etc.). Thanks! Ted On May 18, 2008, at 1:07 PM, Dmitri Makarov wrote: > 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 nume...

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

...weird CRLF issues, etc.). > > Thanks! > > Ted > > On May 18, 2008, at 1:07 PM, Dmitri Makarov wrote: > > > 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 > > inc...

Ted, Thanks for taking care of this. I found that in order to build clang (in addition to the vcproj changes I posted earlier today) I had to add a dependency such that the clangDriver project depends on the CodeGen (basically the CodeGen checkbox has to be checked in the list of the clangDriver's dependencies). This in effect adds codegen.lib to the list of libraries linked into clang.exe