[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.

[hidefromkgb]

The article should be as follows:

Initial preparations

It is better to remove the old versions of both C::B and WXW before trying to build.
To do that, run Bash and paste this to the command prompt:

Code Select Expand

pkglist=""
for pkg in codeblocks wxgtk3 wxgtk2 wxgtk-common; do pkglist+="$(pacman -Qi $pkg | grep -i "^ *name *:" | cut -d: -f2-) "; done
[ -n "$(tr -d " " <<<"$pkglist")" ] && sudo pacman -Rsn $pkglist


Option 1. Building without an AUR wrapper

First, install the prerequisites:

Code Select Expand

sudo pacman -S curl zlib gcc-libs expat gtk2 gtk3 gst-plugins-base-libs libsm libxxf86vm libnotify valgrind bzip2 hicolor-icon-theme gamin hunspell webkit2gtk

Then, go to /tmp/ and build a development version of WXW and then an SVN revision of C::B:

Code Select Expand

cd /tmp/
root="https://aur.archlinux.org/cgit/aur.git/plain/PKGBUILD?h="
for pkg in wxgtk-common-dev wxgtk2-dev wxgtk3-dev codeblocks-svn; do rm -rf $pkg; mkdir $pkg; cd $pkg; curl -o PKGBUILD "$root$pkg"; makepkg --noconfirm; sudo pacman -U *.pkg.tar.xz || exit 1; cd ..; done

Done.

Option 2. Building with an AUR wrapper

Here I assume that the AUR wrapper installed on the target Arch machine is Pacaur.
If it`s not the case then please translate the given commands to your favourite wrapper`s format manually, it should be straightforward.

Build a development version of WXW and then an SVN revision of C::B:

Code Select Expand

pacaur -S wxgtk-common-dev wxgtk2-dev wxgtk3-dev codeblocks-svn

Done.

I`ll modify the article once I finish testing the first approach.