User forums > Using Code::Blocks
[SOLVED] 'AM_OPTIONS_WXCONFIG' not found in library
hidefromkgb:
…Okay. After several more rebuilds I finally know what happened.
The actual culprit was wxgtk-common being incompatible with wxgtk2-dev and wxgtk3-dev.
To successfully build C::B on Arch, even if your system seems to refuse, you need to:
* Choose and install an AUR helper; I, for the time being, prefer pacaur.
* Remove WXW and C::B in their entirety:
pacaur -Rsn wxgtk-common wxgtk2 wxgtk3 codeblocks
* Compile the *-dev versions of WXW packages from AUR:
pacaur -S wxgtk-common-dev wxgtk2-dev wxgtk3-dev
* Compile an SVN C::B build from AUR:
pacaur -S codeblocks-svn
Freshest versions of autoconf, automake, and m4 known to be working:
$ autoconf --version | head -1; automake --version | head -1; m4 --version | head -1
autoconf (GNU Autoconf) 2.69
automake (GNU automake) 1.16.1
m4 (GNU M4) 1.4.18
Thanks guys!
Now I`m finally able to use shortcuts on non-Latin layouts ^__^
BlueHazzard:
I have not followed the whole thread, but it would be very nice, if you could write a little up to date, step by step tutorial how to build codeblocks on ARCH and put it in the wiki, or put it here and i will put it to the wiki...
hidefromkgb:
Okay, I`m ready to help!
This is the article to be edited, I presume?
The problem is, in Arch there is actually no need to compile C::B from source anymore unless you want the latest features right now, e.g. like I do.
Can I change the name of the article to something more general, e.g. «Installing Code::Blocks on Arch Linux» to include the easy method of pacman -S codeblocks?
BlueHazzard:
Sry, i was thinking you build from source.
You can make a new wiki page for installing, or update this. Any additional information and instruction is great!
oBFusCATed:
This page is specifically for source installations. Using pacman isn't something worth documenting.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version