Hello,
i don't know if only i have this bug, but backtick execution isn't working for me in the actual nightly build (8484) on Windows 7.
I use the backtick execution for wx-config. Under Build Options -> Compiler Settings -> Other options i have written
`wx-config --cflags --unicode=yes --wxcfg=gcc_dll\mswud`
-posix
but the wx-config is never called as shown in the build log:
mingw32-g++.exe -std=c++0x -Wall -posix -std=gnu++0x -D__GNUWIN32__ -D__WXMSW__ -DUNICODE -g -D_GLIBCXX_DEBUG -Iinclude -Iutils\rapidxml-1.13 -I..\boost_1_50_0 -Iutils\libusbx\include\libusbx-1.0 -I XXXX -c XXXX -o XXXX
if i call wx-config in the cmd:
wx-config --cflags --unicode=yes --wxcfg=gcc_dll\mswud
-mthreads -DHAVE_W32API_H -D__WXMSW__ -D__WXDEBUG__ -D_UNICODE -Ic:\wxWidgets-2.
9.4\lib\gcc_dll\mswud -Ic:\wxWidgets-2.9.4\include -DWXUSINGDLL -Wno-ctor-dtor-p
rivacy -pipe -fmessage-length=0 -posix
So is this my fault, or is it a bug?
Think of a large wxWidgets project like C::B.
Without caching we would need to call wx-config for (nearly) each compiled filed and that would surely slow down compiling a lot.
i didn't thought about that...
I put the comand line in pre-build and it fails also....
Execution of 'wx-config.exe --cflags --unicode=yes --wxcfg=gcc_dll/mswud' in 'E:\XXXX' failed.
my wx-config is in the c:/windows/system32 folder, and this folder is in the path ;)
I copied wx-config to the root directory of c::b and now it is working...
there seems something wrong with the search path of executables.
anyway, thank you all
for the awesome IDE and fast support!