Author Topic: Has the importing VS solution functionality been improved in CB 1.0rc2?  (Read 3032 times)

Offline Michael

  • Lives here!
  • ****
  • Posts: 1608
Hello,

I have tried to import a MS Visual C++ .NET 2003 solution (RakNet, http://www.rakkarsoft.com/) within the new CB 1.0rc2, but it seems that nothing or quite has changed since the previous release of CB.

Has the importing functionality been improved since the last release or will be improved in a further release? If I remember from a previous post, improvements to this feature were in progress (http://forums.codeblocks.org/index.php/topic,696.0.html).

The problems that I have are the following: libraries imported without the extension .lib, sometimes additional paths to the same library are inserted and problems with pdb files that generate link errors (but, just in debug mode).

If you want to try, just download RakNet, import its solution in CB and compile one or more projects (by using the VC Toolkit 2003 compiler).

Thank you very much.

Best wishes,
Michael

Offline zieQ

  • Almost regular
  • **
  • Posts: 155
Re: Has the importing VS solution functionality been improved in CB 1.0rc2?
« Reply #1 on: October 31, 2005, 11:22:14 am »
Yep, nothing has changed... I've not much time to improve it now. In fact, we're are stuck with the current design choice, so it's a pain to deal with command-line options. Anyway, if you have a bug, please point me to the post, i can't remember what is wrong with importers.

Offline Michael

  • Lives here!
  • ****
  • Posts: 1608
Re: Has the importing VS solution functionality been improved in CB 1.0rc2?
« Reply #2 on: October 31, 2005, 12:33:13 pm »
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.html

The 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