The most common way that I know of to get those sorts of linker errors is to declare a method in a class but forget to define it, i.e.:
class type {
public:
type();
};
//type::type() {}...
Type: Posts; User: dwks
The most common way that I know of to get those sorts of linker errors is to declare a method in a class but forget to define it, i.e.:
class type {
public:
type();
};
//type::type() {}...
Hmm, your program compiles if I add the following onto the end of srz.cpp, and remove everything from serialization.cpp:
template <class T>
T Serialization<T>::load(const string& fileName)...
Canada, actually -- but yes.
By the way:
httputil.cpp: In function ‘int UrlEncode(const char*, char*, unsigned int)’:
httputil.cpp:90: error: ‘strchr’ was not declared in this scope...
I'm working on it. Your build system doesn't seem to be the problem -- compiling it by hand generates the same errors -- though your clock is in the future compared to mine, so I had to run "touch...
I can send you my email address if you like, but it's easier if you just send me a private message with your code or whatever. You can attach any file extension if you add .c or .txt onto the end....
You're not messing around with namespaces, are you? I don't see any in your header file, but they could cause this sort of problem.
What happens if you compile some of the source files by hand,...
It looks like the code from serialize.cpp isn't being linked into your executable for some reason, because the functions defined in that source file cannot be found by the linker.
I'm not really...
You may be compiling all of the source files (i.e., generating .o files for each .cpp file), but are you linking them all together? Can you describe how you're compiling the code? If you're using...