linker-warning

I have a dll project in which, when in Release configuration I build the project, I get the following warning: MSVCRT.lib(cinitexe.obj) : warning LNK4098: defaultlib 'msvcrtd.lib' conflicts with use of other libs; use /NODEFAULTLIB:library It's just a warning but I dunno if this should be taken into account. For what I've found out, they are both multithread libs, normal and debugging versions. My dll uses multithreading and I can debug it, although I use boost:thread for it, so I really dunno if I need this Windows specific libraries for debugging or Release building... Kind regards, Alex

In my current Swift project, I have a 3rd party static library, added through the Build Phases > "Link Binary With Libraries" section. After updating to xcode 8.3, this library started throwing some linker warnings (e.g.: pointer not aligned at address 0x00000 from libraryFile.a) As pointed out by other answers ( https://stackoverflow.com/a/8580123/2754958 and https://stackoverflow.com/a/6921972/2754958 ), the compiler warnings could be ignored by adding a flag to the library code. However, in my case, the libraries are static, and the warning are from the linker. Is there a way to disable

When I am trying to sourceCpp , it gives a warning: ld: warning: text-based stub file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation.tbd and library file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation are out of sync. Falling back to library file for linking. But the function actually works. Just wondering how to solve this warning. jiyongdong I had this problem while compiling Go code on my Mac too. The tld files were out of sync in /System/Library/Frameworks/ . The solution : Just links the recent frameworks from MacOSX.sdk to /Library/Frameworks/

I have a dynamic framework that is shared between an iOS application and an extension. There is some code in that framework that references UIApplication , that is of course, not usable in an extension. Those calls are completely isolated and so I am not worried about them causing problems with my extension. Since there isn't a flag specified in the warning message, perhaps there isn't way to do it, but how do I suppress warning: linking against dylib not safe for use in application extensions when building my project? For your watch/today-widget extension target (so not your app or libray

I am using android NDK- r10d to build Android x86 executable (shared linking) that runs on adb shell. On run time, I am getting the following warning: WARNING: linker: ./myapp: **unused DT entry:** type 0x1d arg 0x4a604 I am using a rooted Nexus Player to test the executable. And my build machine is Ubuntu 14.04 (also tried on Fedora 14 machine). What are "unused DT entry" errors? If you have reached this page, it's probably because you have compiled or attempted to run some binaries on your ARM based Android system, with the result that your binary/app crashes or generates a lot of warnings

I simply want to rid of the warnings that pop up like these: ld: warning: directory not found for option '-F/Users/m/Desktop/FacebookSDK' ld: warning: directory not found for option '-F/Users/m/Desktop/FacebookSDK/FBAudienceNetwork' ld: warning: directory not found for option '-F/Users/gavin/Downloads/shaffiulla11-bat-b86d81d8adc6' ld: warning: directory not found for option '-F/Users/gavin/Desktop/shaffiulla11-bat-b86d81d8adc6' ld: warning: ignoring file /Users/Gavin/Desktop/FacebookSDK/Bolts.framework/Bolts, missing required architecture x86_64 in file /Users/Gavin/Desktop/FacebookSDK/Bolts