Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: freepro on March 06, 2013, 01:00:56 pm
-
I installed wxWidgets-2.9.4 and wx-config --version also is 2.9.4, but the CodeBlocks-12.11 use wx-2.8 to compile wxWidgets program.
What happened? How i should to do?
Thank you!
PS:
bill@freepro:~$ wx-config --cflags
-I/usr/local/lib/wx/include/gtk2-unicode-2.9 -I/usr/local/include/wx-2.9 -D_FILE_OFFSET_BITS=64 -DWXUSINGDLL -D__WXGTK__ -pthread
bill@freepro:~$ wx-config --libs
-L/usr/local/lib -pthread -lwx_gtk2u_xrc-2.9 -lwx_gtk2u_html-2.9 -lwx_gtk2u_qa-2.9 -lwx_gtk2u_adv-2.9 -lwx_gtk2u_core-2.9 -lwx_baseu_xml-2.9 -lwx_baseu_net-2.9 -lwx_baseu-2.9
-
How and where do you call in C::B.
Was C::B while installng wx2.9.4 ? The result of calling a backticked expression is cached as long as C::B is open.
-
How and where do you call in C::B.
Was C::B while installng wx2.9.4 ? The result of calling a backticked expression is cached as long as C::B is open.
I'm so sorry, my english is poor.
I use CodeBlocks-12.11 to write wxWidgets program . and my Linux installed wxWidgets-2.9.4, but CodeBlocks use wx-2.8 to compile program.
-
Was C::B opened while installing wx2.9.4 ?
Sorry my fault, I missed a word in my previous post.
Can you attach the project file you use, or send it via mail to me?
jens at codeblocks dot org
-
Was C::B opened while installing wx2.9.4 ?
Sorry my fault, I missed a word in my previous post.
Can you attach the project file you use, or send it via mail to me?
jens at codeblocks dot org
I'v send email to you.
-
The file looks good.
Again my question:
Was C::B opened while installing wx2.9.4 ?
If wx-config for 2.9 is used from console, it should also be used from inside C::B.
You can try to add --version=2.8 to the calls of wx-config in the build-options.
-
The file looks good.
Again my question:
Was C::B opened while installing wx2.9.4 ?
If wx-config for 2.9 is used from console, it should also be used from inside C::B.
You can try to add --version=2.8 to the calls of wx-config in the build-options.
Can you tell me how to do?
-
The file looks good.
Again my question:
Was C::B opened while installing wx2.9.4 ?
If wx-config for 2.9 is used from console, it should also be used from inside C::B.
You can try to add --version=2.8 to the calls of wx-config in the build-options.
Can you tell me how to do?
Not before you answer the question, I asked three times now !
-
The file looks good.
Again my question:
Was C::B opened while installing wx2.9.4 ?
If wx-config for 2.9 is used from console, it should also be used from inside C::B.
You can try to add --version=2.8 to the calls of wx-config in the build-options.
Can you tell me how to do?
Not before you answer the question, I asked three times now !
I'm so sorry, i forgot!
I first installed the C::B, and then installed wx.
I 'm using ./confiure make make install ldconfig to install wx.
-
Still not answered !
Was C::B opened while installing wx2.9.4 ?
If yes close and reopen it, if not, what's the output of wx-config --list ?
-
Still not answered !
Was C::B opened while installing wx2.9.4 ?
If yes close and reopen it, if not, what's the output of wx-config --list ?
Sorry did not understand what you mean before.
Now, i understand it.
the C::B was closed when installing wx-2.9.4.
this is wx-config --list output:
bill@freepro:~$ wx-config --list
Default config is gtk2-unicode-2.9
Default config will be used for output
-
I need help, please! :'(
-
I need help, please! :'(
You can try a complete rebuild.
And you can also put wx-config --list in the prebuild steps of the project (right-click the project, chose "Build options -> Pre/Post build steps -> Pre-build steps" and put it there) to see what is used by C::B when you build the project.
-
I need help, please! :'(
You can try a complete rebuild.
And you can also put wx-config --list in the prebuild steps of the project (right-click the project, chose "Build options -> Pre/Post build steps -> Pre-build steps" and put it there) to see what is used by C::B when you build the project.
This is output:
-
I'm about to collapse!
What happened? :'(
-
If both wx-config outputs are from the same machine and the same user, C::B and the console must run with different environments.
If your wx-config for wx2.9 is not in /usr/bin, but e.g. in /usr/local/bin, you might need to use the absolute path for it in the compiler and linker options.
C::B puts the compilers search path (usually /usr/bin) in the front of the path it uses for building to ensure the correct compiler is used.
-
If both wx-config outputs are from the same machine and the same user, C::B and the console must run with different environments.
If your wx-config for wx2.9 is not in /usr/bin, but e.g. in /usr/local/bin, you might need to use the absolute path for it in the compiler and linker options.
C::B puts the compilers search path (usually /usr/bin) in the front of the path it uses for building to ensure the correct compiler is used.
Oh, i understand it! the question was solved!
Thank you very carefully to the answers! :D