The problem is you are not linking against the Ws2_32.lib library. To fix this you can add that to your additional dependencies tab of linker/Input settings for your project. Alternatively (as pointed out by SChepurin in the comments) you can add #pragma comment(lib, “Ws2_32.lib”) to a source file of your project.
The documentation does mention an important drawback to /bigobj: Linkers that shipped prior to Visual C++ 2005 cannot read .obj files that were produced with /bigobj. So, setting this option by default would restrict the number of linkers that can consume the resulting object files. Better to activate it on a need-to basis.
Go into your Projects settings and remove the excess Frameworks paths in there that you don’t need. Here’s what it looks like when I open my project’s build settings: Click on “Framework Search Paths” and you should find the bogus paths listed in there, which you can delete.
It is because the unit generated by MOC isn’t included in the linking process. Or maybe it isn’t generated at all. The first thing I’d do is to put the class declaration in a separate header file, perhaps the build system isn’t scanning implementation files. Another possibility is that the class in question once didn’t … Read more
Any time you add a new call to the Q_OBJECT macro, you need to run qmake again. The vtables issue you’re referring to is directly related to that. Just run qmake and you should be good to go assuming there are no other issues in your code.
Don’t define variables in headers. Put declarations in header and definitions in one of the .c files. In config.h extern const char *names[]; In some .c file: const char *names[] = { “brian”, “stefan”, “steve” }; If you put a definition of a global variable in a header file, then this definition will go to … Read more
After struggling with this same problem and following all the accepted answers of updating build settings, clearing the linker search path, etc.. I finally discovered an answer that worked for me. Before building, make sure you select right type (iPhone Simulator) instead of iOS Device. Then rebuild. Otherwise, you’re trying to use a library built … Read more
Look up the symbol (kUTTypeImage) and locate the image/library it should exist in (MobileCoreServices.framework in this case). Then link your binary with that framework.
You may find that you have to link with the math libraries on whatever system you’re using, something like: gcc -o myprog myprog.c -L/path/to/libs -lm ^^^ – this bit here. Including headers lets a compiler know about function declarations but it does not necessarily automatically link to the code required to perform that function. Failing … Read more
The trick here is to put the library AFTER the module you are compiling. The problem is a reference thing. The linker resolves references in order, so when the library is BEFORE the module being compiled, the linker gets confused and does not think that any of the functions in the library are needed. By … Read more