It appears that you don't have installed the wx-config script.
It may come in a package called wx-common or something like that (depending on your distro).
Rebuild...
g++: `wx-config: No such file or directory.Are you sure you put the two backticks aroung wx-config?
inCodeI can only see one backtick.Rebuild...
g++: `wx-config: No such file or directory.
It would be something like `wx-config --cflags`
wx-config not found as I would guess that the build system does not *expand* the `wx-config ...`.The expansion is done by the shell, so it should work. I guess you're using Bourne Shell, which supports backticks. (In Windows the expansion is emulated).
This might be a bug (I don't know what does gmake).
When I change the Compiler setup to use GMAKE I get duplicate targets...
Is it actually possible to build Code::Blocks from within Code::Blocks???Of course. Indeed, it is the build method most commonly used.
Already had "Full command line" shown... I like to see what is happening....wx-config not found as I would guess that the build system does not *expand* the `wx-config ...`.The expansion is done by the shell, so it should work. I guess you're using Bourne Shell, which supports backticks. (In Windows the expansion is emulated).
To know if the expansion is working, please switch to full command line (see the screenshot), and post it back the build log.
(http://img71.imageshack.us/img71/8613/fullcommandline9nq.png) (http://imageshack.us)This might be a bug (I don't know what does gmake).
When I change the Compiler setup to use GMAKE I get duplicate targets...Is it actually possible to build Code::Blocks from within Code::Blocks???Of course. Indeed, it is the build method most commonly used.
In the screenshot posted by Takeshi, do you see the "Shell to run compiler" ?
Change it to a shell in your system that evaluates backtick'd expressions. Try bash for example...
(Code::Blocks Version 1.0 RC2)that's the problem,
(Code::Blocks Version 1.0 RC2)that's the problem,
you need to check out a recent svn version and build that using the autotools
try it, it's not very difficult, ( when you have all necessary tools installed...)
./bootstrap
./configure
make
make install
with this generated version the `wx-config` works well,
then you can use this version in order to build
CodeBlocks with codeblock-unix.cbp
(before building delete the precompiled header *.gch)
and you get a new CodeBlocks version in src/devel
then run
src/update
and you have a working version of codeblocks installed in src/output
which you run with the ./run.sh
copy this version to your preferred ~/usr/bin or whereever you like
and use it as your working version from now on (dont forget to edit the run.sh there )
you may consider to uninstall the autotools generated version,
as you'll not need it anymore from this point on.
Currently I am stuck with a couple of unresolved externals from from AngelScript (as) library which seems to be a relatively new addition to Code::Blocks. The problem here seems to be that the build is conditional whether i386 is pre-defined or not, which does not seem to be the case for amd64 builds. I have not been able to find a solution for this problem yet.
If anyone has any idea's I sure would like to know.
Currently I am stuck with a couple of unresolved externals from from AngelScript (as) library which seems to be a relatively new addition to Code::Blocks. The problem here seems to be that the build is conditional whether i386 is pre-defined or not, which does not seem to be the case for amd64 builds. I have not been able to find a solution for this problem yet.
If anyone has any idea's I sure would like to know.
Define AS_MAX_PORTABILITY in as_config.h.
You might want to read here: http://forums.codeblocks.org/index.php?topic=2096.0
For a quick "it'll work but it's not the good way" remove all the Assertions (r>=0) in the src\sdk\as\bindings.