From mint-bounce@lists.fishpool.fi Sun Nov 23 05:25:59 2008 X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) on WARSBL601.highway.telekom.at X-Spam-Level: From: Edgar Aichinger To: mint@lists.fishpool.fi Subject: Re: [MiNT] SV: OT Highwire Date: Sun, 23 Nov 2008 11:20:24 +0100 User-Agent: KMail/1.10.3 (Linux/2.6.25.15-jen67-rt; KDE/4.1.3; i686; ; ) References: <20081121171837.0b6393c6.mandin.patrice@orange.fr> <00324f45.019a88ca1228@smtp.freeola.net> In-Reply-To: <00324f45.019a88ca1228@smtp.freeola.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811231120.24928.edgar.aichinger@aon.at> X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: edgar.aichinger@aon.at Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Am Samstag 22 November 2008 schrieb Peter Slegg: > I'd like some better development tools. > > I'd like to be able to compile easily from my editor and quickly > jump to errors. I think this has been done in the past and might > be possible with QED and gcc but how ? > QED has a nice mechanism for this, I just don't remember well how I set it all up... IIRC I had a TosWin shell window for compiling using gcc, redirected stderr to a file I called compiler.log or similar, and QED would realize when the file contents changed. Just make sure that the error message template fits the gcc errors/warnings, and right click the error in the logfile... > Some debugging tools would be a great help. > > Peter > > > > > >