User forums > Using Code::Blocks

A little step by step tutorial, please [SOLVED]

<< < (2/5) > >>

thomas:

--- Quote ---The problem is that the template from which wxSmith generated is buggy (ie. it doesn't knows anything about unicode, it's a bit outdated also), so that's very likely the problem.
--- End quote ---
It is not. Read the original post.

takeshimiya:

--- Quote from: thomas on March 24, 2006, 09:57:51 am ---It is not. Read the original post.

--- End quote ---
Regardless, it is buggy yet...

thomas:
But you are confusing him even more with something that is completely unrelated.
As you can see from the build log, he was trying to build using the wxstatic template. This does not work because the headers cannot be found. This is what he needs to fix.
Throwing in wxSmith as the likely problem (which is not true) leads onto a wrong path, so he'll never get it to work.

takeshimiya:
I already gave the instructions, try with the C::B template first, if that works, try next with wxSmith.

If the wxSmith generated project doesn't works (DLL), it's probable because missing unicode flags and 'u'.

byo:
wxSmith project wizard works for me out of box. It's just a matter of proper wxWidets compilation.
I think that the problem is somewhere else - We can configure libraries using global variables but there's no standard saying how global variable should describe any library (or maybe I missed something).
And in fact library setings like directories are configured inside project file using global variables as base information only. So we have lot of includes, lib dirs etc specific for used library which may confuse new user.
And when next wxWidgets version is released all wxWidgets project may be outdated (just like it was in case of switching between wx2.4 and wx2.6).

My proposition is to extend functionality of global variables (f.ex. add ability to use more than one include dir etc, add library profiles like ansi/unicode) and make some standard of describing library using global variables.

In such case when global variable is properly configured, user just select what libraries to use inside project and all is done. Project templates won't outdate too often and C::B will get easy to use library managment system. Such solution may also remove incompatibilities between windows / linux projects, so You will need only one for both environments since differences will be stored in global-variables level.

Navigation

[0] Message Index

[#] Next page

[*] Previous page