Hello,
Thank you very much for your reply.
The import functionality is not so bad, especially if you know what you have to modify to successfully compile/link your project. The problems, I have met until now are:
1) The extension .lib is not imported. For example, you can have ws2_32 instead of ws2_32.lib. CB seems to search for an object file ws2_32 instead of a library.
2) In some cases, a the path and name of a library is imported twice, but with a small difference. In the debug mode, the Debug is included into the path and in release the Release is included in the path. So, if I have this library:
./../../../lib/RakNetLibStaticDebug.lib
in debug mode, I will also have a ./Debug/../../lib/RakNetLibStaticDebug.lib (I am not 100% sure that the path name is exactly this. Anyway, it is something similar).
This library (path + name) has to be deleted.
3) I have sometimes problems with pdb files. Some projects refuse to link in debug mode, because a (some) object file(s) is (are) missing. By deleting the following: /pdb:Debug\ReliableOrderedTest.pdb, the project link fine.
You can find more info by looking at this post:
http://forums.codeblocks.org/index.php/topic,696.0.htmlThe better solution will be to download RakNet and import its solution file in CB. Then by looking at "Project's Build options" under linker, you will remark the problems listen above (at least 1) and 2). For the 3) you have to compile/link one or more projects).
To download RakNet:
http://www.rakkarsoft.com/Best wishes,
Michael