| The most annoying CDT bug [message #217960] |
Thu, 26 June 2008 10:06  |
Eclipse User |
|
|
|
Originally posted by: schabi.logix-tt.com
Hi,
I'm using eclipse 3.3.2 with CDT 4.0.3 and some other plugins.
The project is configured to run a custom build command (which runs our
scons based build with some additional parameters), and "build
automatically" is activated in the project menu.
Now, wenever I modify more than one file before saving, and then press
Ctrl-Shift-S to save all those files, it saves one file and starts
building. After building, it saves the next file, and builds again
etc., and it shows a window that the save operation is waiting for the
build to finish.
Stopping the build operation sometimes allows one or two files to be
saved before the next build starts.
The JDK part does handle this much nicer, there all files are saved
before the build starts.
My current workaround is to disable autobuild at all, and run manual
builds every time I save. But I think that this is ugly.
My wish would be that all files are saved before the build starts, and
when editing and saving a file while a build runs, that the build is
interrupted instead of having the save operation wait and bloking the
whole UI.
Is there any solution for my problem?
Thanks,
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
|
|
|
| Re: The most annoying CDT bug [message #217985 is a reply to message #217960] |
Fri, 27 June 2008 07:56  |
| Eclipse User |
|
|
|
Markus Schaber wrote:
> Hi,
>
> I'm using eclipse 3.3.2 with CDT 4.0.3 and some other plugins.
>
> The project is configured to run a custom build command (which runs our
> scons based build with some additional parameters), and "build
> automatically" is activated in the project menu.
>
> Now, wenever I modify more than one file before saving, and then press
> Ctrl-Shift-S to save all those files, it saves one file and starts
> building. After building, it saves the next file, and builds again
> etc., and it shows a window that the save operation is waiting for the
> build to finish.
>
> Stopping the build operation sometimes allows one or two files to be
> saved before the next build starts.
>
> The JDK part does handle this much nicer, there all files are saved
> before the build starts.
>
> My current workaround is to disable autobuild at all, and run manual
> builds every time I save. But I think that this is ugly.
>
> My wish would be that all files are saved before the build starts, and
> when editing and saving a file while a build runs, that the build is
> interrupted instead of having the save operation wait and bloking the
> whole UI.
>
>
> Is there any solution for my problem?
> Thanks,
It is true that Build Automatically does not scale well for C/C++ projects.
How about the following:
In the Preferences under General > Workspace
- Disable Build automatically
- Enable Save automatically before build
User Ctrl+B to start a build and have all files saved before the build
starts.
HTH
--
Anton Leherbauer
Wind River CDT Team, Austria
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.24268 seconds
Home