Menu
▾
▴
#115 Cancel compilation doesn't work
My project uses boost and spirit libraries and it takes a
long time to compile the main file (about 4-6 min). If after
compilation starts I press the "Cancel" button inside
the "Compile Progress" dialog the compilation doesn't
stop. It takes about the same time to stop as to compile
this file. (Compilation stops though if I manually kill the
cc1plus.exe process). This feature is extremly annoying
especially when the source code contains some errors
which are printed much earlier than compilation stops
and there is no practical way to stop the compilation.
Regards,
Pavel
Logged In: YES
user_id=859472
The Cancel always works for me...
Could you please tell us what version are you using.
Logged In: NO
To reproduce this problem compile a file that takes more than
2 min to compile and right after compilation starts try to
cacnel it. (Almost any sample from the Spirit library can be
used).
Regarding version I use. I don't remember. I switched to
msvc++ 7.1 which works far better and faster for me.
Logged In: YES
user_id=682737
By the way, the cancel button is disabled during the
dependency checking (which can also take a long time in some
circumstances).
If I actually wanted to do a full rebuild, I have really no
chance to stop it during the dependency checking.
Logged In: YES
user_id=735003
I have observed that "Cancel" only takes effect between
"make" steps. This may be a "make" problem or a problem
with the interface between "make" and "Dev-Cpp"... I
imagine that "make" is in a hard wait for its sub-task to
complete and doesn't receive the stop message until the
subtask exits.
Logged In: NO
Have you tried to reproduce the problem as I described in the
bug report? (BTW thanks for such fast reply. WIll wait for
another one in 2 years:)
Pavel
Logged In: YES
user_id=735003
Paval:
Please understand that I am NOT (yet) one of the maintainers.
I did indeed reproduce your problem in the way you
described. (Actually I simply observed that the problem you
described matched what happened when I canceled in the
middle of a fairly long compilation. I also observed that
you can not cancel the dependency scan.) I happen to
understand a bit of what is going on behind the sceens and
restated the problem in terms of that understanding. I'm
not sure that anything can really be done about the problem
since it may lie outside the scope of Dev-Cpp. I've seen
almost the exact same problem with CodeWarrior Pro. I'm not
sure if I saw the problem with VS; it's been quite a while
since I used it. I've also seen something like this
behavior on kernel builds for linux which is why I suspect a
'make' problem.
If I'm going to work on this problem I'll need to:
0) Check with sepcu and company to see if this is something
they think I can handle.
1) Find the dependency checking code and put an cancel check
there.
2) Check 'make' to see how it wants to be aborted. It's
sub-tasks really should have a chance to clean up after
themselves. Leaving a screwed up .o file (or any other kind
of generated file for that matter) around just isn't 'on'.
3) If a different way of stopping make looks feasable, code
it and try it. If not, put up a note that 'make' has been
told to stop and that it may take a little while for 'make'
to comply.
Don't expect a rapid response on this. This is a
frustrator, not a show stopper. Things do stop eventually
when you push cancel; it just takes a bit of time.