[cfe-dev] cmake & vc++: clang vs. libclang woes

[Francois Pichet]

On Tue, Apr 5, 2011 at 10:45 AM, Óscar Fuentes <ofv at wanadoo.es> wrote:
> Óscar Fuentes <ofv at wanadoo.es> writes:
>
> [snip]
>
>> The real fix would be to not create an exports file for clang.exe, as
>> you suggest. It seems that the exports file is created when the
>> executable exports symbols (a Windows executable can act as a dll too.)
> [snip]
>> Inspecting clang.exe with depends.exe shows this two exported functions:
>>
>> std::_Mutex::_Mutex(enum std::_Uninitialized)
>> class std::_Init_locks & std::_Init_locks::operator=(class std::_Init_locks const &)
>>
>> No idea why they are there. Actually, it seems that most (all?)
>> executables created by the build exports those symbols and the lib
>> directory is plagued with .exp and .lib files corresponding to the LLVM
>> executables.
>
> It is a bug on VS, reported as fixed on the upcoming VS 11 (which
> doesn't help us):
>
> http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/4692205a-0296-4f41-adbb-fa8339597f5c/
>
> Defining _STATIC_CPPLIB is mentioned as a workaround, but I don't know
> all the implications.
>

Hi, I have MSVS with the Service Pack 1 (released a few weeks ago) and
I don't get  this problem.
Is VS 11 == SP1 because I really doubt there will ever be a MSVS 2011.