From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_05,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Received: by 2002:a37:9d8a:: with SMTP id g132mr52547009qke.149.1594121866192;
        Tue, 07 Jul 2020 04:37:46 -0700 (PDT)
X-Received: by 2002:a54:4e87:: with SMTP id c7mr2975774oiy.110.1594121865879;
 Tue, 07 Jul 2020 04:37:45 -0700 (PDT)
Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Tue, 7 Jul 2020 04:37:45 -0700 (PDT)
In-Reply-To: <43a34342-88a2-4af3-b146-817192dab5b7o@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: google-groups.googlegroups.com; posting-host=219.90.162.67; posting-account=d51RWwoAAADvR-x0zYAtT9z3CRxT1eXo
NNTP-Posting-Host: 219.90.162.67
References: <d2037e32-a0d4-469c-b90e-6fa22c41fda9o@googlegroups.com>
 <242465de-0171-44b1-9618-752b22c3604co@googlegroups.com> <11c21c57-69de-4fcb-9193-71a98ca93ecao@googlegroups.com>
 <126727e4-3108-46cd-acc6-e42dbdb9dd6bo@googlegroups.com> <011aef92-84e3-47e5-a558-a8c2c6504161o@googlegroups.com>
 <8959b86d-ec38-4e0b-a272-384751914732o@googlegroups.com> <16b49b03-8657-425d-bad5-67cc5fe725d2o@googlegroups.com>
 <891fe070-40a4-4ba2-a7be-a7e9c4c036a4o@googlegroups.com> <04195e55-a82f-4035-a05d-5078ea2e6259o@googlegroups.com>
 <2790711b-d169-4a19-b666-5853eb0f5268o@googlegroups.com> <7052e60c-33ad-4961-9a2c-76014bd6c516o@googlegroups.com>
 <e60818f6-4ab7-4880-bb38-5dd6c38e143fo@googlegroups.com> <6efbebf3-8dd2-4909-ab48-d57ba39dc309o@googlegroups.com>
 <7e2ea50e-412b-421a-b842-e97014043e37o@googlegroups.com> <24f16e6b-e885-4dc5-8519-05c6a786f4dfo@googlegroups.com>
 <b53c26a8-9f04-40fe-87fa-ac8c50fefd27o@googlegroups.com> <53e66aa5-c298-4b27-8718-386e7a624141o@googlegroups.com>
 <43a34342-88a2-4af3-b146-817192dab5b7o@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7eb0e148-f1b4-4df8-879a-f6fce173e4c4o@googlegroups.com>
Subject: Re: SweetAda 0.1 released
From: Roger <rogermcm2@gmail.com>
Injection-Date: Tue, 07 Jul 2020 11:37:46 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader01.eternal-september.org comp.lang.ada:59382
List-Id: <comp.lang.ada>

On Tuesday, July 7, 2020 at 6:13:15 PM UTC+10, gabriele....@gmail.com wrote=
:
>=20
> If you see the XYZ characters on a terminal, then QEMU is running fine, a=
nd you are seeing CPU sending characters through a serial port. You don't s=
ee other things because there is nothing else on the terminal, as I said Sw=
eetAda is essentially a framework and the code does very little. The main w=
indow of QEMU does display the VGA screen of the emulated platform, which i=
s not used. IOEMU should display a pulsing 8-bit register (the CPU is in a =
loop counting forever), but if it didn't maybe there are some GUI problems =
yet to solve.
>=20
> If you want to execute the toolchain directly, then you have to know exac=
tly what you want. You can call GNATMAKE, but then you have to supply the R=
TS location, compiler switches and the source files of your project. If you=
 aren't an embedded Ada developer, then there is no point in doing that.
>=20
> My feeling is that, after many test (sorry), you could have a corrupted e=
nvironment, since does sound strange to me that you have errors in running =
the new QEMU executable and the new libioemu library.
>=20
> Being said that, try to annotate your work and wait for me to collect fur=
ther info from other OSX users, so we can understand better where potential=
 QEMU problems could arise.
>=20
> I appreciate your interest.

Thanks for your advice.
I'll try and investigate further.