Problems with wxWidgets Applications

[tiwag]

RKCole
we can try another 100 guesses or just look what's wrong, it's up to you

when you get a linker error like wxmsw26 not found, it's unlikely that the pch has something to do with

[addendum]
please post the exact version of CodeBlocks you are using

go to Help->About->Information-tab and post what is written there

[RKCole]

I agree, tiwag.  Thanks for the help.

[attachment deleted by admin]

[RKCole]

Sorry, missed the addendum.

Code::Blocks version 1.0 RC2
Build: Oct 24 23:49:28 - wx-2.6.1 (Windows, ANSI)

[tiwag]

ok - i ran your project with CodeBlocks 1.0RC2 and beside the fact, that i have my wxWidgets installed in D:\wx262 and therefore adjusted the custom variable WX_DIR to my needs, your project built perfectly. ( using Build->Rebuild or Ctrl-F11 )

can you please look, what files you have in your
C:\wxWidgets-2.6.2\lib\gcc_dll
directory ?

post the output-file (mylibs.txt) of
dir C:\wxWidgets-2.6.2\lib\gcc_dll > mylibs.txt

which you run in a command window

[RKCole]

In the gcc_dll folder there is a folder called "msw" with a "build.cfg" file in it.  There is a folder in this directory called "wx" with the "setup.h" file in it.  I did not see a mylibs.txt file, though.

[sethjackson]

In the gcc_dll folder there is a folder called "msw" with a "build.cfg" file in it.  There is a folder in this directory called "wx" with the "setup.h" file in it.  I did not see a mylibs.txt file, though.

He means run this in the command prompt (he says to in the last line of his post).  :wink:

Code

dir C:\wxWidgets-2.6.2\lib\gcc_dll > mylibs.txt

[tiwag]

He means run this in the command prompt (he says to in the last line of his post).  :wink:

Code

dir C:\wxWidgets-2.6.2\lib\gcc_dll > mylibs.txt

exactly , thx seth !

[sethjackson]

He means run this in the command prompt (he says to in the last line of his post).  :wink:

Code

dir C:\wxWidgets-2.6.2\lib\gcc_dll > mylibs.txt

exactly , thx seth !

Yeah. np  I almost missed that you said to run in command prompt myself. 

[RKCole]

Sorry guys...guess I'm not fully here today...Have had a headache all day...

[attachment deleted by admin]

[tiwag]

i don't wonder, why your project doesn't build,

you don't have any wxWidgets library at all in your libs directory

Volume in drive C has no label.
 Volume Serial Number is 4C72-D410

 Directory of C:\wxWidgets-2.6.2\lib\gcc_dll

01/27/2006  03:42 PM    <DIR>          .
01/27/2006  03:42 PM    <DIR>          ..
01/27/2006  03:20 PM    <DIR>          msw
               0 File(s)              0 bytes
               3 Dir(s)  71,395,835,904 bytes free



[edit]

in your case, ANSI build only, it should look like

Directory of C:\wxWidgets-2.6.2\lib\gcc_dll

2005.12.30  01:07    <DIR>          .
2005.12.30  01:07    <DIR>          ..
2006.01.01  17:25    <DIR>          msw
2006.01.01  17:27           158.734 libwxexpat.a
2006.01.01  17:26           146.784 libwxjpeg.a
2006.01.01  17:52        13.106.452 libwxmsw26.a
2006.01.01  17:26           169.592 libwxpng.a
2006.01.01  17:26            79.110 libwxregex.a
2006.01.01  17:26           327.646 libwxtiff.a
2006.01.01  17:26            73.036 libwxzlib.a
2006.01.01  17:53         9.577.786 wxmsw26_gcc.dll



[edit2]
if you have the wxwidgets object files still on your harddisk,
open a command prompt,
navigate to
C:\wxWidgets-2.6.2
and run the make process again
cd build\msw
mingw32-make -f makefile.gcc BUILD=release SHARED=1 MONOLITHIC=1 USE_XRC=1 UNICODE=0


this will rebuild the libraries

[RKCole]

That's odd...I wonder what happened...Everything worked just fine yesterday...

Should I just try to build wxWidgets again and see what the result is?

Thanks for taking the time to help me with this.

[tiwag]

maybe you ran a "make clean" on your wxWidgets, this deletes all output files

[RKCole]

I may have...I will give this another try and post back later.

Thanks for all of the help, tiwag.

[RKCole]

I believe that tiwag was correct in me running a "make clean" command.  I'm very unfamiliar with working with MingW in the command prompt, so I believe this was the cause of the problem.

Everything is working just fine now.

Thanks for all of the help.

Take care.