| Different Calling thread in build operation [message #270210] |
Sun, 05 September 2004 09:03 |
Eclipse User |
|
|
|
Originally posted by: XXX.analog.com
Hi,
I've notices that the build operation can be performed under 2 different
threads:
1. ModalContext - when the user invokes the build operation
2. UI thread (main thread) - when the auto-build option is on, and a
resource modification occurs.
I'm using an external compiler/linker tools which use the 2 default
process' streams (regular & error) to communicate. In order to work with
these tools I'm using additional threads which listen to these streams,
and dump their content into my special build-console.
When the first type of call is being used (ModalContext) there is no
problem - my printout mechanism uses the UI thread to send the printout to
the console.
But when the build is called from the UI thread - the "listening" threads
can not use the UI thread in-order to print stuff into the console, since
it is occupied by the build operation which is not finished yet (and which
is waiting for the tool process to end).
My question is - was this separation intentional ? is there a way to
overcome it by some how configuring the eclipse to make all the calls come
from a separated ModalContext thread ? does someone have a suggestion how
to solve this problem in a simple way ?
Thanks in advance,
Oded.
p.s.
I Don't know if its relevant but I've noticed that in the launch operation
there is a similar problem:
- Regular launch is called from a separated ModalContext thread
- Re-launch is called from the UI thread.
|
|
|
Powered by
FUDForum. Page generated in 0.03025 seconds
Home