User forums > Using Code::Blocks

[solved] CB compiles, but won't run

<< < (3/3)

TheTuxKeeper:

--- Quote from: squizzz on November 04, 2005, 06:25:11 pm ---checking for wxWidgets static library... no

--- End quote ---
That's no error. There are two types of libraries static and dynamic, normally distributions take dynamic ones.


I use Suse 10 with the original wxGTK packages and it works! You need wxGTK, wxGTK-compat, wxGTK-gl and wxGTK-devel, these are all version 2.6.1. You can download them from one of the Suse mirror server. Just add one to the Yast install sources.
FTP mirror in poland (in your profile stands that you're from poland, is this right?):
Server: ftp.man.poznan.pl
directory: pub/linux/opensuse/opensuse/distribution/SL-10.0-OSS/inst-source/

Then go to install new software in Yast and install wxGTK-devel and its dependencies.

After that try again using the source RPM. How is discribed here: Compiling Code::Blocks in RPM based distributions

Daniel

squizzz:

--- Quote from: daniel2000 on November 04, 2005, 07:11:07 pm ---I use Suse 10 with the original wxGTK packages and it works! You need wxGTK, wxGTK-compat, wxGTK-gl and wxGTK-devel, these are all version 2.6.1. You can download them from one of the Suse mirror server. Just add one to the Yast install sources.
FTP mirror in poland (in your profile stands that you're from poland, is this right?):
Server: ftp.man.poznan.pl
directory: pub/linux/opensuse/opensuse/distribution/SL-10.0-OSS/inst-source/

Then go to install new software in Yast and install wxGTK-devel and its dependencies.

--- End quote ---
Thanks a lot for the info! Didn't know that possibility (which solves a lot of trouble!). And yes, my profile info is correct.


--- Quote ---After that try again using the source RPM. How is discribed here: Compiling Code::Blocks in RPM based distributions

--- End quote ---
What can I say... It works! :)
Your source *.rpm is simply bulletproof... Thanks!

Presumably the thing I was doing wrong myself was either wrong devel packages or (VERY highly probable) that I messed sources with batch dos2unix operation...  :oops:

Thanks for everyone's replies!
Jan

rickg22:
Can you add this to the wiki? Many linux users probably got the wrong wxGTK installed, or simply don't have them installed.

grv575:
also if you want to log those error messages do:

make 2>&1 >> log.txt

means redirect file descriptor 2 to file descriptor 1 (0 = stdin, 1 = stdout, 2=stderr).  So then stdout will contain both normal stdout output plus stderr messages and append them to log.txt.

if you want to both see the compilation process and log it do:

make 2>&1 | tee -a log.txt

Navigation

[0] Message Index

[*] Previous page