User forums > Help

wxWidgets 2.6 (MSW, GCC) installation instructions

<< < (25/29) > >>

AkiraDev:
Assuming you used the C::B project wizard for wxWidgets apps, did you choose dynamic (DLL) or static linking in the dialog?

In case you chose "static" there may be a small bug in the prototype project file: it is incorrectly stating the linker working directory as $(WX_DIR)\lib\gcc_dll instead of $(WX_DIR)\lib\gcc_lib. Correct this and it should link fine.

TDragon:
Assuming you didn't use the included wxWidgets project template, create one and compare. There are three different configuration locations that need to match up:

* Include paths,
* #defines, and
* Linked librariesYou must always have <wxwidgets>\include in your include paths.
You must also always have a configuration specific include path. If you're building with Windows DLL NON-unicode, it's <wxwidgets>\lib\<configuration>\msw; if you're building with Windows DLL Unicode, it's <wxwidgets>\lib\<configuration>\mswu.

If you're building for Windows, you must have "__WXMSW__", defined, and should have "HAVE_W32API_H" defined.
If you're building with the DLL, you must have "WXUSINGDLL" defined.
If you're building with the Unicode version, you must have "wxUSE_UNICODE" defined.

If you're building with the Windows DLL NON-Unicode, you must link with wxmsw26; if you're building with the Windows DLL Unicode, you must link with wxmsw26u.

As I mentioned before, all this is taken care of for you with the wxWidgets project template included with Code::Blocks. All you would need to change would be the paths with "gcc_dll" in them, if that isn't the name of your wxWidgets configuration (in the lib subdirectory). (And, if you're like me, delete the precompiled header.)

wittend:

--- Quote ---If you're building for Windows, you must have "__WXMSW__", defined, and should have "HAVE_W32API_H" defined.
...
If you're building with the Unicode version, you must have "wxUSE_UNICODE" defined.

--- End quote ---

Thanks! This worked! I needed "HAVE_W32API_H" and/or "wxUSEUNICODE", did a clean, & then the build worked.  I really appreciate the help from everyone!

-- dave

MortenMacFly:

--- Quote from: wittend on February 24, 2006, 09:36:19 pm ---Thanks! This worked! I needed "HAVE_W32API_H" and/or "wxUSEUNICODE", did a clean, & then the build worked.  I really appreciate the help from everyone!

--- End quote ---
Great news! ;-)
Well, I wonder if this information should be put into the WiKi then. It seems worth it.
TDragon: Will you take the chance?
Morten.

TDragon:
Maybe one of these days when I'm feeling documentative. :lol:

Come to think of it, I probably don't have modification rights on the CBwiki.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version