I do not know MSVC but my idea is that you do not need to "convert" anything. You should be able to use the .dll and .lib files as they are.
Be sure to include in your C-program:
#define BCCWIN // or define it somewhere in projectproperties
#define LITTLENDIAN // or define it somewhere in projectproperties
#include "nodave.h"
#include "opensocket.h"
I should also recommend to try first to compile one of the test program in MSVC.
If you do C++, you may need to define
extern "C" {
#include "nodave.h"
#include "opensocket.h"
}
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can only tell you tha the library itself and the test programs have been compiled with BorlandC from the Fre Commandline Tools.
You may try them.
If you look into the Makefile.mak (which is the one I used under Windows), you may note that libnodave.lib is generated from libnodave.dll by some tool. Maybe If MSVC thinks libnodave.lib is corrupt, you could try to regenerate it using the equivalent MS tool?
Anyone else using MSVC?
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can only tell you tha the library itself and the test programs have been compiled with BorlandC from the Fre Commandline Tools.
You may try them.
If you look into the Makefile.mak (which is the one I used under Windows), you may note that libnodave.lib is generated from libnodave.dll by some tool. Maybe If MSVC thinks libnodave.lib is corrupt, you could try to regenerate it using the equivalent MS tool?
Anyone else using MSVC?
Thomas
PS: I'm writing this again after logging in. Strangely, I see my previous post when I'm logged in but not, when I'm not...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried to convert the lib and dll files to work with MSVC but I failed.
Is there anyone running MSVC and libnodave?
Best regards,
Johan
I do not know MSVC but my idea is that you do not need to "convert" anything. You should be able to use the .dll and .lib files as they are.
Be sure to include in your C-program:
#define BCCWIN // or define it somewhere in projectproperties
#define LITTLENDIAN // or define it somewhere in projectproperties
#include "nodave.h"
#include "opensocket.h"
I should also recommend to try first to compile one of the test program in MSVC.
If you do C++, you may need to define
extern "C" {
#include "nodave.h"
#include "opensocket.h"
}
I tried some diffrent settings but the closest I get to a working exe is, I think;
Linking...
libnodave.lib : fatal error LNK1136: invalid or corrupt file
Error executing link.exe.
This is in MSVC 6 but it appears to be the same in MSVC 7.
It could be intresting to know what tools others are using with libnodave on windows.
I can only tell you tha the library itself and the test programs have been compiled with BorlandC from the Fre Commandline Tools.
You may try them.
If you look into the Makefile.mak (which is the one I used under Windows), you may note that libnodave.lib is generated from libnodave.dll by some tool. Maybe If MSVC thinks libnodave.lib is corrupt, you could try to regenerate it using the equivalent MS tool?
Anyone else using MSVC?
Thomas
I can only tell you tha the library itself and the test programs have been compiled with BorlandC from the Fre Commandline Tools.
You may try them.
If you look into the Makefile.mak (which is the one I used under Windows), you may note that libnodave.lib is generated from libnodave.dll by some tool. Maybe If MSVC thinks libnodave.lib is corrupt, you could try to regenerate it using the equivalent MS tool?
Anyone else using MSVC?
Thomas
PS: I'm writing this again after logging in. Strangely, I see my previous post when I'm logged in but not, when I'm not...
1. Add some preprocessor definitions: /D "DOEXPORT" /D "LITTLE_ENDIAN" /D "BCCWIN"
Maybe I forgot someone. Have a look into the MAKEFILE.VC
2. Remove the preprocessor definition: /D "WIN32"
3. Add the ws2_32.lib to your library modules in the linker section.
That's all!?