Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
batchbuild issues with backticked commands
takeshimiya:
Sorry to ruin the party, I'm at Rev. 3086 and here it builds fine both from the IDE and from Build from explorer, using same wx-config exe from http://wxconfig.googlepages.com/) .
HOWEVER, I must note something is wrong with C::B file associations: when I do a double click on any CBP I get a Windows cannot find 'path\to\file.cbp'...
Something strange?
Log I get when I use batch builds:
-------------- Build: Release-wxdll in autobuildnumber ---------------
mingw32-g++.exe -fexpensive-optimizations -Os -Wall -mthreads -DHAVE_W32API_H -D__WXMSW__ -ID:\Develop\src\wxWidgets-2.6.3\lib\gcc_dll\msw -ID:\Develop\src\wxWidgets-2.6.3\include -DWXUSINGDLL -Wno-ctor-dtor-privacy -pipe -fmessage-length=0 -ID:\Develop\bin\mingw345\include -ID:\Develop\MyPaks\include -ID:\Develop\DevPaks\include -ID:\cbbb\ -c autobuildnumber.cpp -o .objs\autobuildnumber.o
mingw32-g++.exe -LD:\Develop\bin\mingw345\lib -LD:\Develop\MyPaks\lib -LD:\Develop\DevPaks\lib -o autobuildnumber.exe .objs\autobuildnumber.o -s -mthreads -LD:\Develop\src\wxWidgets-2.6.3\lib\gcc_dll -lwxmsw26 -lwxtiff -lwxjpeg -lwxpng -lwxzlib -lwxregex -lwxexpat -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwxregex -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32
autobuildnumber.cpp: In function `void IncrementVersion(const wxString&, wxString*, const wxString&)':
autobuildnumber.cpp:286: warning: int format, long int arg (arg 2)
Process terminated with status 0 (0 minutes, 5 seconds)
0 errors, 1 warnings
Log when I use the IDE:
-------------- Build: Release-wxdll in autobuildnumber ---------------
mingw32-g++.exe -fexpensive-optimizations -Os -Wall -mthreads -DHAVE_W32API_H -D__WXMSW__ -D_UNICODE -ID:\Develop\src\wxWidgets-2.6.3\lib\gcc_dll\mswu -ID:\Develop\src\wxWidgets-2.6.3\include -DWXUSINGDLL -Wno-ctor-dtor-privacy -pipe -fmessage-length=0 -ID:\Develop\bin\mingw345\include -ID:\Develop\MyPaks\include -ID:\Develop\DevPaks\include -ID:\cbbb\ -c autobuildnumber.cpp -o .objs\autobuildnumber.o
mingw32-g++.exe -LD:\Develop\bin\mingw345\lib -LD:\Develop\MyPaks\lib -LD:\Develop\DevPaks\lib -o autobuildnumber.exe .objs\autobuildnumber.o -s -mthreads -LD:\Develop\src\wxWidgets-2.6.3\lib\gcc_dll -lwxmsw26u -lwxtiff -lwxjpeg -lwxpng -lwxzlib -lwxregexu -lwxexpat -lkernel32 -luser32 -lgdi32 -lcomdlg32 -lwxregexu -lwinspool -lwinmm -lshell32 -lcomctl32 -lole32 -loleaut32 -luuid -lrpcrt4 -ladvapi32 -lwsock32
Process terminated with status 0 (0 minutes, 5 seconds)
0 errors, 0 warnings
EDIT: if this is a bug and was introduced in some rev. between 3086~3105, then at a first glance 3099 or 3094 seems the most likely.
tiwag:
i found the reason
the problem is, that wx-config doesn't return anything to stdout, when it errors out,
this obviously confuses the backticked-command expander
the reason, why it behaves different when using from the IDE or from batchbuild
is obviously located in the environment variables plugin.
normally i don't have an environment variable WXWIN defined,
but i defined it to a valid value in the environmentvariables plugin,
which works fine with wx-config when using from the ide
defined in environment variables: WXWIN=D:\wx263
`wx-config --cxxflags` expands fine to shared ansi release wx-library
when batchbuilding the same project, CB hangs because `wx-config --cxxflags` doesn't return anything
evidence:
when using `wx-config --prefix=d:\wx263 --cxxflags` instead, then the project builds fine from the IDE and
from batch-build.
conclusion:
wx-config should return at least an error message if it couldn't find the requested wx-library
CB should check if there was any character returned and handle the case if no chars are coming instead of hanging around lazy :P
CB environment variables plugin should also work in batch-build mode !!!!
brgds, tiwag
MortenMacFly:
--- Quote from: tiwag on October 18, 2006, 09:39:39 pm ---but it doesn't explain, why it freezes CB only when batch-building ?!
wx-config doesn't freeze CB when you build a project normally from the IDE ?!
--- End quote ---
No, actually this I didn't try - until now. The project I used for testing previously did not use wx-config.
So yes: Using wx-config also freezes C::B in non-batch-build-mode, but only if using wx-config. Any other tools I enter just works fine (but of course causes a compilation error).
@Takeshi: Could you try another C::B with a higher revision, please? Maybe we can narrow down when this happened - so obvioulsy between 3086 and 3003... or what?! ;-)
With regards, Morten.
tiwag:
--- Quote from: MortenMacFly on October 18, 2006, 09:59:29 pm ---...Any other tools I enter just works fine (but of course causes a compilation error)...
--- End quote ---
try any other tool which doesn't return anything to stdout
MortenMacFly:
--- Quote from: tiwag on October 18, 2006, 09:57:41 pm ---conclusion:
wx-config should return at least an error message if it couldn't find the requested wx-library
CB should check if there was any character returned and handle the case if no chars are coming instead of hanging around lazy :P
CB environment variables plugin should also work in batch-build mode !!!!
--- End quote ---
Our posts have crossed - sorry for that. But what I don't get: I don't have a WXWIN variable defined in the envvar plugin thus if I use wx-config it also freezes the IDE during non-batch-build-mode build. Did you say it doesn't freezes your IDE in non-batch-build-mode? Could you try what happens if you remove the WXWIN envvar and try to compile this project from the IDE (in non-batch-build-mode)?
With regards, Morten.
Ps.: You said previously that you've disabled all plugins for the batch-build. How should the envvar plugin work then?!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version