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

building CodeBlocks with M$ VC++ Toolkit 2003

<< < (8/9) > >>

rickg22:
CrazyAbbot: Actually just the info about the warnings, but it seems you just listed it here.

The macros declare arrays, so i don't think it'll be a problem. They're data-only classes and they're MSVC-safe.

Anyway I modified the latest CVS with some of your dllimport modifications.

Hey, I have an idea  that Yiannis might like. In the stdafx.h we could check for NULL and define it as 0L depending on the configuration, if it's not set.

NOTE:
Regarding my installation of the platform SDK, it seems i'm the first to experience an awful error with windows installer 3.1v2. No matter what package i'm installing, it aborts unexpectedly. It could be something in my config, or it could be one of the infamous "updates". Until Microsoft fixes this issue (i submitted an automated report), I'm afraid I won't be able to install the platform SDK nor try to compile codeblocks by myself. Sorry, you're on your own for now :(

tiwag:

--- Quote from: rickg22 ---... I modified the latest CVS ...
--- End quote ---


Would it be possible to create and maintain a web-log where one can read about the latest cvs-changes ?

or is it possible to automatically create a log of all check-in comments of  all newly modified files ?

@rick: what kind of help do you need regarding MSVC ?

mandrav:

--- Quote from: CrazyAbbot ---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.
--- End quote ---

Try replacing
--- Code: ---WX_DECLARE_OBJARRAY(ConfigurationPath, Configurations)
--- End code ---
with
--- Code: ---WX_DECLARE_USER_EXPORTED_OBJARRAY(ConfigurationPath, Configurations, DLLIMPORT)
--- End code ---
and see if it works.

Yiannis.

CrazyAbbot:
rickg22:  What are you talking about with the null macro? every compiler i've seen defines it, its in the standard library.


mandrav:
That fixed it

Would you mind if I went through the source code and fixed just about all the warnings that MSVC is generating? and put a few pragmas in to turn off the size_t cast warnings?

It shouldn't cause the GCC compile to break, and I can always test it and fix that.

mandrav:

--- Quote from: CrazyAbbot ---Would you mind if I went through the source code and fixed just about all the warnings that MSVC is generating? and put a few pragmas in to turn off the size_t cast warnings?

It shouldn't cause the GCC compile to break, and I can always test it and fix that.
--- End quote ---

Patches are always welcome ;)
Just make sure you work on recent CVS.

Yiannis.

Navigation

[0] Message Index

[#] Next page

[*] Previous page