Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

building CodeBlocks with M$ VC++ Toolkit 2003

<< < (7/9) > >>

tiwag:

--- Quote from: CrazyAbbot ---... ok i just managed to get the codeblocks.dll to build and i managed to link it with the codeblocks.exe  (albiet with 600+ warnings, but working none the less)...
--- End quote ---


Great !
can you upload the diffs & project files somewhere ?
i would like to have a closer look too.

thanks, tiwag

rickg22:

--- Quote ---
in the file startherepage.cpp what is this class for?

--- Code: ---
class DLLIMPORT MyHtmlWin : public wxHtmlWindow

--- End code ---

I had to remove the DLLIMPORT macro for it to compile

--- End quote ---


You're right! DLLIMPORT should only be used for files belonging to the SDK! I'm gonna remove it right now. I'm also adding the DLLIMPORT to messagemanager.

As a final note, can you report a bug ( Correction: feature request) at sourceforge about the 600 warnings? Please upload a file, too. Thanks :)

mandrav:

--- Quote from: rickg22 ---As a final note, can you report a bug at sourceforge about the 600 warnings? Please upload a file, too. Thanks
--- End quote ---

This is not a bug Rick!
It's the code he edited to compile with an unsupported (yet) compiler. What makes you think I should be hunting down bugs from source code outside the CVS tree, instead of fixing existing (and real) bugs?

Yiannis.

rickg22:
Oh, sorry. Then it should be a feature request then. Anyway I'm installing the MSVC Toolkit. Actually I'm beginning to think I should have installed it from the beginning (as to give more support to VC++ users). I got this curiosity for since the bug reports about importing msvc projects.

This way, I think I could offer windows support as Yiannis' field is Linux :)

Anyway - Tiwag, mind giving me a hand with this? You were the one who started this whole "compiling with msvc" business. And you're OBVIOUSLY a msvc++ user, so.... :)

CrazyAbbot:
Well, it is the code from the CVS, I just had to fix a few bugs to get it to compile.

Anyway there are a few major types of warnings that appear:

Implict cast from size_t to int (nothing important)
Calling the SANITY_CHECK() macro, but not giving it any parameters.
Cast from pointer to a long.
Using magic numbers, instead of a boolean true or false

and the main one with making codeblocks.dll

Take this bit of code from configmanager.h

--- Code: ---
WX_DECLARE_OBJARRAY(ConfigurationPath, Configurations);

--- End code ---


I ran the header file through the preprocessor to see what it did and this is the declaration of the class it generated


--- Code: ---
class Configurations : protected wxArrayPtrVoid

--- End code ---


so this macro is creating a class called Configurations.

If a class is declared as being exportable (in this case, ConfigManager), then all the member classes of that class must be exportable as well (class Configurations).

so MSVC wants this class to be declared as DLLEXPORT.  however it seems to be working fine without it.  is class Configurations ever used from OUTSIDE the dll?  if it's only for internal use (IE, within the DLL) then that is probably ok.


I will try to stuff about with the wx widgets header files to get their macro to declare the class as DLLEXPORT and see if that stops the compiler warnings.

rickg22:  What do you want me to upload?

Navigation

[0] Message Index

[#] Next page

[*] Previous page