Im not sure if that is available on the version of MSVC I am using.. But Ill
take a look.. Thanks
-Original Message-
From: David Cole [mailto:dlrd...@aol.com]
Sent: Wednesday, May 21, 2014 9:45 AM
To: Scott Aron Bloom; cmake@cmake.org
Subject: Re: [CMake] PDB generation
> However, if th
On Wed, May 21, 2014 at 12:21 PM, Scott Aron Bloom <
scott.bl...@onshorecs.com> wrote:
> At some point in the 2.8 lifecycle, the choice was made to no longer
> copy the .pdb files on windows builds with the .lib that is generated.
>
>
>
> I found a note somewhere, that there was “good” reasoning
> However, if the target of your project IS a static library that you
> supply to customers for integration into their toosl, you NEED to
> supply the pdb otherwise they are stuck getting the “pdb not found”
> warning message.
Rather than having a separate pdb file, for debug static libraries, yo
At some point in the 2.8 lifecycle, the choice was made to no longer copy the
.pdb files on windows builds with the .lib that is generated.
I found a note somewhere, that there was "good" reasoning for it.. And in
general, I agree, for many applications you don't need the pdb files for static
l
Additional info on versions:
c++ --version:
Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix
OS X Mavericks 10.9.2
SDK used 10.9
Regards
/Robert
Robert Bielik skrev 2014-05-21 10:22:
> c++ --version:
> Apple LLVM version 5.1
>
c++ --version:
Apple LLVM version 5.1
Problem description:
Linking always fails in Release build:
Warning: Option -s is obsolete and being ignored
with the following error:
Internal error: atom not found in symbolIndex() for architecture ...
If I remove the -s option from linking (tried it wi
