Hello everybody,
I have tried to find out why all plugins get Makefile's created by configure but are never built. I tried two ways to build CB: A) via Gentoo live ebuild, B) manually via bootstrap, configure and make. One example is the devpak_plugin. It gets a Makefile but isn't built by Make.
I searched the forums and the wiki, but all I found out is, that some of the plugins listed on the wiki page as contrib plugins simply aren't built.
Is this a problem with the current SVN revision or do I miss something? Honestly I suspect the latter ;)
Thanks for your help in advance!
Which parameters do you use for configure ?
The ebuild uses:./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --with-wx-config=/usr/lib64/wx/config/gtk2-unicode-release-2.8 --disable-debug --enable-pch --disable-static --with-contrib-plugins=allAnd I have manually tried out:./configure --prefix=/usr/local --with-wx-config=/usr/lib64/wx/config/gtk2-unicode-release-2.8 --with-contrib-plugins=allBoth with the same result.
Sidenote: If I just configure the package, cd into the src/plugins/contrib/DoxyBlocks folder and issue "make all", it is built. But doing so in the devpak_plugin folder results in the following:sed-notebook devpak_plugin # LC_ALL="C" make all
Making all in bzip2
make[1]: Entering directory `/var/tmp/portage/dev-util/codeblocks-9999/work/codeblocks-9999/src/plugins/contrib/devpak_plugin/bzip2'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/var/tmp/portage/dev-util/codeblocks-9999/work/codeblocks-9999/src/plugins/contrib/devpak_plugin/bzip2'
make[1]: Entering directory `/var/tmp/portage/dev-util/codeblocks-9999/work/codeblocks-9999/src/plugins/contrib/devpak_plugin'
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory `/var/tmp/portage/dev-util/codeblocks-9999/work/codeblocks-9999/src/plugins/contrib/devpak_plugin'
devpak is a windows plugin.
It has a Makefile to add it to a distribution tarball with "make dist", so the target all does nothing.
Oh, that's a pity. :-(
Quote from: Yamakuzure on December 30, 2010, 11:28:56 AM
Oh, that's a pity. :-(
Does devpak provide linux binaries ?
If yes, they will probably not be compatible with your distro, and the most open-source libs are available for almost any linux distro and there is no need for devpak.
Well, it isn't the only plugin that doesn't get built... The devpak plugin was just an example. ;)
So please name the others that does not work.