User forums > Using Code::Blocks

try to compile wxWidgets samples

<< < (2/3) > >>

MoonKid:

--- Quote from: Biplab on March 02, 2007, 07:42:02 am ---The VC import seems to be broken. It fails to import Linker Include Dir and Resource Include Dir.
We'll look into it. Thanks for reporting this bug. :)
--- End quote ---

There is nothing about VC. C::B compile the samples with the default (GCC) compiler.

I do not understand the problem right!?

Auria:

--- Quote from: MoonKid on March 04, 2007, 08:38:01 pm ---
--- Quote from: Biplab on March 02, 2007, 07:42:02 am ---The VC import seems to be broken. It fails to import Linker Include Dir and Resource Include Dir.
We'll look into it. Thanks for reporting this bug. :)
--- End quote ---

There is nothing about VC. C::B compile the samples with the default (GCC) compiler.

I do not understand the problem right!?

--- End quote ---

I'm not sure, but most likely the wxWidgets samples provide VC projects, and Code::Blocks cannot read them properly.

Biplab:

--- Quote from: MoonKid on March 04, 2007, 08:38:01 pm ---There is nothing about VC.

--- End quote ---

No there is nothing about VC compiler support. But there is problem related to importing VC projects. I found that it's not reading the search directories properly.


--- Quote from: MoonKid on March 04, 2007, 08:38:01 pm ---C::B compile the samples with the default (GCC) compiler.

--- End quote ---

Are you talking about importing the VC project and then compiling it with GCC?

MoonKid:

--- Quote from: Biplab on March 05, 2007, 03:12:37 am ---No there is nothing about VC compiler support. But there is problem related to importing VC projects. I found that it's not reading the search directories properly.
--- End quote ---

Of course, the import of VC projects does not work. It just imports the name. ;)
I had to do all build settings manualy as I described in the mainpost.

But the import does not matter If I set the build options myself. The linker search dir is set as I described in the mainpost.


--- Quote from: Biplab on March 05, 2007, 03:12:37 am ---Are you talking about importing the VC project and then compiling it with GCC?
--- End quote ---

Yes.

Biplab:

--- Quote from: MoonKid on March 04, 2007, 08:38:01 pm ---There is nothing about VC. C::B compile the samples with the default (GCC) compiler.

--- End quote ---
It's very difficult to get some meaning from the statement. It seems that C::B compiles samples with GCC and not with others. Did you try with Other compilers?? I think not.

C::B presently supports GCC, MSVC, BCC, OpenWatcom for wxWidgets based app compilation. So the samples should get compiled by any of these compilers. If you do the manual settings or use C::B's support they should get compiled by all supported compilers.


--- Quote from: MoonKid on March 05, 2007, 05:37:04 am ---Of course, the import of VC projects does not work. It just imports the name. ;)

--- End quote ---
No, I can't agree with your statement. What do you mean by "name"?? If it's the project name then you are wrong. It imports a lot more than that.


--- Quote from: MoonKid on March 05, 2007, 05:37:04 am ---I had to do all build settings manualy as I described in the mainpost.

--- End quote ---

--- Quote from: MoonKid on March 05, 2007, 05:37:04 am ---
--- Quote from: Biplab on March 05, 2007, 03:12:37 am ---Are you talking about importing the VC project and then compiling it with GCC?
--- End quote ---

Yes.

--- End quote ---
The VC import is meant for importing VC projects. I don't think it'll do the compiler settings mapping. GCC and VC are different compilers and are not compiler options compatible. So if you import a VC project for GCC you have to edit it. This applies to other compilers, too.

The import works well but as I told there are bugs.

I hope you would post clearer messages in future. Some of these statements can confuse users about the ability of C::B.

Navigation

[0] Message Index

[#] Next page

[*] Previous page