From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 2002:a02:b895:: with SMTP id p21mr50041023jam.80.1556657847206; Tue, 30 Apr 2019 13:57:27 -0700 (PDT) X-Received: by 2002:a9d:3f4b:: with SMTP id m69mr39341062otc.246.1556657846884; Tue, 30 Apr 2019 13:57:26 -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.166.215.MISMATCH!b2no15869itd.0!news-out.google.com!v82ni16ita.0!nntp.google.com!136no15361itk.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Tue, 30 Apr 2019 13:57:26 -0700 (PDT) In-Reply-To: <30e9156c-193e-459d-987c-06182f78ae89@googlegroups.com> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=72.46.200.130; posting-account=4XtIhQoAAACVLe8W-swsgut7CQByKD3Y NNTP-Posting-Host: 72.46.200.130 References: <13ce24c7-2cfd-4c77-8e4f-2aba216d9ca9@googlegroups.com> <12955098-0ae7-4e2e-b4dd-050620a1f039@googlegroups.com> <22ad2bb3-4d6e-48f0-9f72-ea2464390b13@googlegroups.com> <3d9b62c5-6461-420a-b051-132618c40369@googlegroups.com> <67e68b33-4fa1-45fc-aac5-3294258bb4da@googlegroups.com> <30e9156c-193e-459d-987c-06182f78ae89@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: ANN: VisualAda (Ada Integration for Visual Studio 2017 & 2019) release 1.1.12 From: Greg Injection-Date: Tue, 30 Apr 2019 20:57:27 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:56214 Date: 2019-04-30T13:57:26-07:00 List-Id: Alex, 1. I think I had canceled a build earlier, which is why we didn't see those= two "missing" adb files.=20 2. Forgotten that SYSTEM paths come before USER paths in Windows, so added = some entries to SYSTEM path for MSYS and rebooted. 3. Created a new XAML app in VS 2019 called "RaceDirector" (which is what "= RD" stood for, just got lazy.) 4. In VS project properties, "C:\MSYS64\..." picked up correctly for the 3 = "Gnat Root" directories. 5. Consequently, I proceeded to build the solution WITHOUT a change to the = project properties. 5. Built "RaceDirectorXaml" fine. 6. Building "RaceDirector" yields this: 1>------ Build started: Project: RaceDirector, Configuration: Debug x64 ---= --- 1>Compile 1> [Ada] racedirector.adb 1> [Ada] appoverrides.adb 1> [Ada] winmainstartup.adb 1> [Ada] guitask.adb 1> [Ada] locatortask.adb 1> [Ada] racedirectorxaml.adb 1>Bind 1> [gprbind] racedirector.bexch 1> [Ada] racedirector.ali 1>MSBUILD : error MSB4166: Child node "2" exited prematurely. Shutting down= . Diagnostic information may be found in files in "C:\Users\Dad\AppData\Loc= al\Temp\" and will be named MSBuild_*.failure.txt. This location can be cha= nged by setting the MSBUILDDEBUGPATH environment variable to a different di= rectory. 1>A task was canceled. 1>A task was canceled. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Build: 0 succeeded, 1 failed, 0 up-to-date, = 0 skipped =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Notice I did NOT get the ... 1>gprbind: invocation of gnatbind failed=20 1>gprbuild: unable to bind rd.adb=20 ... but still a build error. And still cannot find a MSBuild_*.failure.txt = in the indicated directory. NEXT ... Launched a x64 Native VS2019 command prompt: gprbuild -f -v -p -P RaceDirector.gpr =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3DError messages for file: C:\home\= dad\dev2\RaceDirector\RaceDirector\RaceDirector\RaceDirector.gpr 4. with "WinRt.gpr"; >>> unknown project file: "WinRt.gpr" gprbuild: "RaceDirector.gpr" processing failed So this has GOT to be a directory/path I'm not setting somewhere. Onward, SO close :) Greg