From mint-bounce@lists.fishpool.fi Wed Dec 9 09:37:16 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=pk5foqqxgO3xAsZgF21kIhJDvTgiQuckq70DMU1jKqA=; b=ZY6dtU3I5ba8kwOPbpZ/8BdsdYXCeFhbs7PLo0mNtbFs5c0rqlOf99Y3FnWXuIysS4 VNXnt4AFI+gSxurm4gmMGwSpmoUaeZcxzMqRqlmh+bKmY+KH3XE8k5HSjyCz6cHmtAZR 4DKkK5155Isy/DVAVEqGYi1LLm+tJx5P0WvJI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=NNHVoUAeOgm4HDycz+GTgP/OOYly0j0cuvDhaF+39b7lLiGz0RPxRyhwBzBkMEneEE 4PuSYbh6u5q1K+usDTef/N/fQYoSxvRq9MDQXAZvHWCy/YMuxnqZ6KjX6J3QBawGEbg2 yhgWTF959KKuDBqK5/Gq+OaY3JtIe+mF/MBTs= MIME-Version: 1.0 In-Reply-To: References: <11a6f2b10911270646s6ceab50i915d71aeb27f6be9@mail.gmail.com> <1260278588.20336.221.camel@jetpack.demon.co.uk> <4B1E5596.9010300@freesbee.fr> <200912082209.08699.oak@helsinkinet.fi> <4B1FAB84.1000009@atari-source.org> <4B1FB1D4.70704@freesbee.fr> Date: Wed, 9 Dec 2009 15:34:39 +0100 Message-ID: Subject: Re: [MiNT] XaAES sources for FreeMiNT 1.16.3 From: Miro Kropacek To: Jo Even Skarstein Cc: mint@lists.fishpool.fi Content-Type: multipart/alternative; boundary=00032555aa7e344df3047a4c97e8 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: miro.kropacek@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --00032555aa7e344df3047a4c97e8 Content-Type: text/plain; charset=ISO-8859-1 > > was poking around XaAES about a year ago, doing some minor modifications > just to get familiar with the code. I gave up. I make too many errors while > typing, and spent too much time waiting for gcc to tell me that something is > wrong, but it can't tell me where. It's easier with Pure C. Alt+C, and in a > second I get a long, nice list of my errors, with (correct!) line-numbers > and all. I guess the reason why you don't want to use cross compiler are Atari feelings related, right? :) Because thanks to Vincent's work on gcc and Aranym guys' on Aranym, you can not only develop code faster and more comfortable but you can also faster _test_ it. For example, when I'm doing some freemint related stuff, I set up KDevelop (with all that Alt+C, nice list of errors, line numbers and all :), output path is set exactly to the place where aranym is looking for it, so it's just matter of compile / switch to aranym / restart the aranym operation. 10 seconds at most. What could be more comfortable? -- MiKRO / Mystic Bytes http://mikro.atari.org --00032555aa7e344df3047a4c97e8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
was poking aroun= d XaAES about a year ago, doing some minor modifications just to get famili= ar with the code. I gave up. I make too many errors while typing, and spent= too much time waiting for gcc to tell me that something is wrong, but it c= an't tell me where. It's easier with Pure C. Alt+C, and in a second= I get a long, nice list of my errors, with (correct!) line-numbers and all= .
I guess the reason why you don't want to use cross compiler are At= ari feelings related, right? :) Because thanks to Vincent's work on gcc= and Aranym guys' on Aranym, you can not only develop code faster and m= ore comfortable but you can also faster _test_ it. For example, when I'= m doing some freemint related stuff, I set up KDevelop (with all that Alt+C= , nice list of errors, line numbers and all :), output path is set exactly = to the place where aranym is looking for it, so it's just matter of com= pile / switch to aranym / restart the aranym operation. 10 seconds at most.= What could be more comfortable?


--
MiKRO / Mystic Bytes
http://mikro.atari.org
--00032555aa7e344df3047a4c97e8--