User forums > Help

cannot find -lwxmsw26

(1/1)

hforbess:
I found another post that explains that I need to take the -l from -lwxmsw26 and all my libraries, but I dont see where to do this.

im using WinXP
Gnu GCC compiler
C::B v1.0 rc2

anybody have any idea?

cyberkoa:

--- Quote from: hforbess on November 18, 2005, 05:48:30 pm ---I found another post that explains that I need to take the -l from -lwxmsw26 and all my libraries, but I dont see where to do this.

im using WinXP
Gnu GCC compiler
C::B v1.0 rc2

anybody have any idea?

--- End quote ---
I try to understand your problem ..

is this problem appear when you are building a wx-widgets program or running Codeblocks ?

If is building/linking a program , you need to go to Project/Build Option/ Directory > Linker to check your linker path settings.

And you need to build your own wxwidgets if you do not want to use the wxmsw that come with CB .

thomas:
It depends what you do. You can either tell the linker what you want using the "Link libraries" field to the left, or to "Other linker options" to the right.

Using "Link libraries", you have to remove the -l. Using the "Other linker options" field, you must have it:



Note that the image shows both options, you obviously only need one of them (using "Link libraries" is recommended).

EDIT:
This assumes you have set up the linker's directories properly, if that is not the case, the linker won't find anything either, of course.

hforbess:
apparently, I had to compile these myself.
http://wiki.codeblocks.org/index.php/Compiling_wxWidgets_2.6.1_to_develop_Code::Blocks_%28MSW%29

Then I just tossed the dll's into C:\windows\system32

Works fine now. :D

Thanks

thomas:

--- Quote from: hforbess on November 18, 2005, 07:49:47 pm ---Then I just tossed the dll's into C:\windows\system32
--- End quote ---
Although this works, it is a Bad Idea®.

Better keep them in the wxWidgets directory along with the headers and set the compiler/linker paths correctly. This is safer, cleaner, and more flexible. Tossing stuff into Windows' path can have unforeseen nasty side effects, too, so avoid that whenever you can.

Navigation

[0] Message Index