Roger Mc <rogermcm2@gmail.com> writes:

> On Monday, September 26, 2022 at 11:23:35 PM UTC+10, kevc...@gmail.com wrote:
>> You can get a hello world open in gnat studio
>> with two? commands though.
>>
>> "https://alire.ada.dev/docs/#first-steps"
> Following the "first-steps", progress succeeded up to
> gnat_native=11.2.4 installed successfully but then failure:
> dyld: lazy symbol binding failed: Symbol not found:
> ___darwin_check_fd_set_overflow
> Any ideas on how to fix this:
> Thanks,
> Roger

I tried this on my mid-2012 Macbook Pro running 10.11.6 (El Capitan),
the problem arises when running gprconfig (all the Alire-provided
releases were built against a later Xcode (Google suggests 11.4 or
later??) which does provide this symbol). I dare say it'd happen running
the compiler too.

Only suggestion: install one of my builds, set it on your PATH, run alr
toolchain --select & choose the 'gnat_external' line for the
compiler. Alire then chooses a compatible gprbuild.

11.2.0 at Github:
https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-11.2.0-native

Or 12.1.0 from Github:
https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-12.1.0-x86_64

On 2022-09-27 04:35, Rick Duley wrote:
> For myself, I have two more questions:
> 1. Do I have to create a new project for every mainline I write?

no. depending scenarion (env-var) I build a different set of exes

I got this i a project of mine (50+ executables)

System_Mains := ("rpc_tracker.adb",
...
...
"poll.adb",
"login_handler.adb"
);

Stat_Mains := (
"create_cache.adb",
...
...
"lay_and_back_after_progress.adb"
);

Display_Mains := ("race_time.adb");

Other_Mains := ( "markets_sender.adb",
...
...
"price_to_tics.adb" );

Test_Programs := (); --("test_string_object.adb");

case Bot_Machine_Role is
when "PROD" => for Main use System_Mains;
when "TEST" => for Main use System_Mains;
when "SIM" => for Main use System_Mains &
Stat_Mains &
Other_Mains &
Test_Programs;
when "DISPLAY" => for Main use Display_Mains;
when "LONGPOLL" => for Main use System_Mains;
end case;

--
/Björn

On Wednesday, September 28, 2022 at 12:10:32 AM UTC+10, Simon Wright wrote:
> Roger Mc <roge...@gmail.com> writes:
>
> > On Monday, September 26, 2022 at 11:23:35 PM UTC+10, kevc...@gmail.com wrote:
> >> You can get a hello world open in gnat studio
> >> with two? commands though.
> >>
> >> "https://alire.ada.dev/docs/#first-steps"
> > Following the "first-steps", progress succeeded up to
> > gnat_native=11.2.4 installed successfully but then failure:
> > dyld: lazy symbol binding failed: Symbol not found:
> > ___darwin_check_fd_set_overflow
> > Any ideas on how to fix this:
> > Thanks,
> > Roger
> I tried this on my mid-2012 Macbook Pro running 10.11.6 (El Capitan),
> the problem arises when running gprconfig (all the Alire-provided
> releases were built against a later Xcode (Google suggests 11.4 or
> later??) which does provide this symbol). I dare say it'd happen running
> the compiler too.
>
> Only suggestion: install one of my builds, set it on your PATH, run alr
> toolchain --select & choose the 'gnat_external' line for the
> compiler. Alire then chooses a compatible gprbuild.
>
> 11.2.0 at Github:
> https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-11.2.0-native
>
> Or 12.1.0 from Github:
> https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-12.1.0-x86_64

Thanks Simon
I cloned 12.1.0 from Github then tried .doinstall in the native directory.
It gets to Do you want to proceed with installation but when I respond with Y nothing happens.

Roger Mc <rogermcm2@gmail.com> writes:

>> Only suggestion: install one of my builds, set it on your PATH, run alr
>> toolchain --select & choose the 'gnat_external' line for the
>> compiler. Alire then chooses a compatible gprbuild.
>>
>> 11.2.0 at Github:
>> https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-11.2.0-native
>>
>> Or 12.1.0 from Github:
>> https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-12.1.0-x86_64
>
> Thanks Simon
> I cloned 12.1.0 from Github then tried .doinstall in the native directory.
> It gets to Do you want to proceed with installation but when I respond
> with Y nothing happens.

I don't understand what you've done, at all. "cloned"? ".doinstall"?
"native directory"?

I see that the README at the link above (in fact like most of my
READMEs) might be thought to be less than clear; perhaps the very first
thing should be the Install section. It says

Download the binary .pkg. It's not signed, so don't double-click on
it; instead, right-click on it and Open. Accept the warning. You will
be guided through the installation.

It should also say that "the binary .pkg" is to be found by scrolling to
the bottom of the page.

On Wednesday, September 28, 2022 at 6:26:40 AM UTC+10, Simon Wright wrote:
> Roger Mc <roge...@gmail.com> writes:
>
> >> Only suggestion: install one of my builds, set it on your PATH, run alr
> >> toolchain --select & choose the 'gnat_external' line for the
> >> compiler. Alire then chooses a compatible gprbuild.
> >>
> >> 11.2.0 at Github:
> >> https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-11.2.0-native
> >>
> >> Or 12.1.0 from Github:
> >> https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-12.1.0-x86_64
> >
> > Thanks Simon
> > I cloned 12.1.0 from Github then tried .doinstall in the native directory.
> > It gets to Do you want to proceed with installation but when I respond
> > with Y nothing happens.
> I don't understand what you've done, at all. "cloned"? ".doinstall"?
> "native directory"?
>
> I see that the README at the link above (in fact like most of my
> READMEs) might be thought to be less than clear; perhaps the very first
> thing should be the Install section. It says
>
> Download the binary .pkg. It's not signed, so don't double-click on
> it; instead, right-click on it and Open. Accept the warning. You will
> be guided through the installation.
>
> It should also say that "the binary .pkg" is to be found by scrolling to
> the bottom of the page.
Many thanks, much appreciated
I confused the issue as I'm only used to downloading programs from git's " code" page.
I had no problems following your instructions above which resulted in an easy installation.
I'm currently using the 2019 version of gps for development but am investigating alr.

On Wednesday, September 28, 2022 at 10:14:33 PM UTC+10, Roger Mc wrote:
> On Wednesday, September 28, 2022 at 6:26:40 AM UTC+10, Simon Wright wrote:
> > Roger Mc <roge...@gmail.com> writes:
> >
> > >> Only suggestion: install one of my builds, set it on your PATH, run alr
> > >> toolchain --select & choose the 'gnat_external' line for the
> > >> compiler. Alire then chooses a compatible gprbuild.
> > >>
> > >> 11.2.0 at Github:
> > >> https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-11.2.0-native
> > >>
> > >> Or 12.1.0 from Github:
> > >> https://github.com/simonjwright/distributing-gcc/releases/tag/gcc-12.1.0-x86_64
> > >
> > > Thanks Simon
> > > I cloned 12.1.0 from Github then tried .doinstall in the native directory.
> > > It gets to Do you want to proceed with installation but when I respond
> > > with Y nothing happens.
> > I don't understand what you've done, at all. "cloned"? ".doinstall"?
> > "native directory"?
> >
> > I see that the README at the link above (in fact like most of my
> > READMEs) might be thought to be less than clear; perhaps the very first
> > thing should be the Install section. It says
> >
> > Download the binary .pkg. It's not signed, so don't double-click on
> > it; instead, right-click on it and Open. Accept the warning. You will
> > be guided through the installation.
> >
> > It should also say that "the binary .pkg" is to be found by scrolling to
> > the bottom of the page.
> Many thanks, much appreciated
> I confused the issue as I'm only used to downloading programs from git's " code" page.
> I had no problems following your instructions above which resulted in an easy installation.
> I'm currently using the 2019 version of gps for development but am investigating alr.

I successfully built one of my projects with alr.
Is it possible to use gps with alr?

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:

> On 2022-09-26 08:20, Rick Duley wrote:
>
>> I have Gnat Studio but I can't do anything at all unless I create a
>> Project (whatever that is). Even then, I can't write and run
>> Hello_World unless I call it Main. The concept of an IDE where I can
>> step through a program checking changes in variable values as I go
>> seems to have vanished.
>
> That concept is called debugger. GDB for GCC (GNAT Ada is based in
> GDB). GDB never ever really worked except for little exercises. It
> still does not. So, forget about it.

Dmitry is an extreme pessimist about gdb; apparently he has had bad
experience with it.

On the other hand, I used GNAT with gdb for many years at NASA,
maintaining a spacecraft simulator; I never had a problem with gdb.

>> In short, I am lost and I can't find any material to help me find my
way.

There is a tutorial in the GNAT Studio Help menu, somewhere. I haven't
looked at it for years, I don't know if it covers debugging.

AdaCore has extensive resources for learning; see
https://learn.adacore.com/

--
-- Stephe

"Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:

> On 2022-09-26 09:11, Rick Duley wrote:
>> You missed the point, Dmitry. Showing me the code for Hello_World
>> does not show me how to create the program using Gnat Studio.
>
> Hmm, programs are created by typing them in an editor...

Gnat Studio is an IDE, not just an Editor.

>> Firstly, I do not understand the concept of a _Project_.
>
> Project is an executable or shared/static library.

It is much more than that.

In technical terms, for GNAT Studio a "Project" is defined by a gnat
project file. In turn, that project file defines the list of source
directories, where to store object and executable files, the
compilation options for release and debug builds, and a few other
things.

GNAT Studio can create and edit project files for you. When you get to
more complex projects, you will want to edit them directly.

There are tutorials on using gnat studio, including debugging, at
https://www.adacore.com/gnatpro/toolsuite/gnatstudio (I found them by
searching for "GNAT Studio").

>> Until a couple of days ago I had never heard the term in reference to Ada Programming.
>
> It always existed. E.g. Ada 83 Reference Manual called it "the program
> library". See ARM 83 (10.4)

Which is literally not "project", although it is a similar concept.

"Project" is now a common term in many software tools.

>> Secondly, I can write Hello_World.adb and have it included in my
>> 'Project', I can even build it, but the only thing that will run is
>> _Main_.
>
> No, I provided the project file where the main procedure is called
> Hello_World.
>
>> I cannot find any documentation about Studio which explains
>> something as simple as the creation of Hello_World.exe. Can you do
>> that in Studio or is it purely ornamental?

Here are the steps I used to create "hello world" in Gnat Studio:

- Start gnat studio from the command line.

- If you have no previous projects, it starts a wizard that offers to
create new project from a template. You get the same wizard by selecting
File | New Project from the main GNAT Studio interface. In the wizard,
choose Basic | Simple Ada Project.

- Select a directory to hold the project files (GNAT Studio calls it
"deploy"); I created a new directory named "hello_world".

- change the project name from "default" to "Hello_World" (it must be a
valid Ada identifier).

- Change the Main Name from "main" to "hello_world". (this is the
crucial step you have been asking for).

- Now you are in the main GNAT Studio interface. Note that it has
created the "src" and "obj" directories, and src/hello_world.adb for
you. Every IDE (except Emacs :) has a default notion of the "proper"
layout for directories; some let you change that default (I don't know
if GNAT Studio does). Some build systems tolerate other directory
structures; GNAT Studio does as long as the corresponding changes are
made in the project file.

- Edit hello_world.adb to do Put_Line ("Hello_World");

- From the menu, select Build | Run | "Run main"

The project is compiled, and the program is run. However, I don't see
the output from the program in the Messages window.

And running the exectable (which is hello_word/obj/hello_world) does not
produce any output.

Ah; I just saw Dmitry's hint about Debug | Initialize. Doing that starts
the gdb interface in GNAT Stdio. Clicking the "Run" button (which looks
like a media player "play" button) runs the program, which prints Hello
World in the debugger console. Success!

I'm guessing running the executable from the command line failed because
some library was not found; GNAT Studio must set up the library search
paths.

Apparently it was compiled without debug options. But in Edit | Project
Properties, I don't see anything about Debug. And there's no way to
search for a property; does anyone know where that is?

--
-- Stephe

"Jeffrey R.Carter" <spam.jrcarter.not@spam.acm.org.not> writes:

> On 2022-09-26 11:34, Rick Duley wrote:
>> On Monday, September 26, 2022 at 5:30:14 PM UTC+8, Jeffrey R.Carter wrote:
>>>
>>> You can start GNAT Studio with a "default project". This lets you use it as an LSE.
>> What is an LSE?
>
> Sorry: Language-Sensitive Editor

LSE was the name of the fancy editor made by Digital Equipment
Corporation back when I was first learning Ada :). The editor supports
"templates" that know the language syntax; you can type i f C-e, and it
expands to "if {expression} then {statments} [else {statments}] end if;"
and each of the {} [] can be similarly expanded.

I don't know if GNAT Studio supports such templates. In Emacs they are
called "skeletons".

A better term for GNAT Studio these days is IDE (Integrated Development
Environment); it has many more features than knowing the language syntax.

--
-- Stephe

On 2022-09-28 20:28, Stephen Leake wrote:
> "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de> writes:
>
>> On 2022-09-26 09:11, Rick Duley wrote:

>>> Until a couple of days ago I had never heard the term in reference to Ada Programming.
>>
>> It always existed. E.g. Ada 83 Reference Manual called it "the program
>> library". See ARM 83 (10.4)
>
> Which is literally not "project", although it is a similar concept.
>
> "Project" is now a common term in many software tools.

Back in late 90's ObjecAda had projects. The project file had extension
literally *.prj.

The first GNAT IDE AdaGIDE also had projects and called them so. AdaGIDE
project file was *.ago.

I do not remember what DEC Ada used for the library. I remember that
Pallada Ada had some sort of project, but early Meridian Ada did not.
But that was before the dinosaurs... (:-))

--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

On Wednesday, September 28, 2022 at 10:08:23 PM UTC+2, Dmitry A. Kazakov wrote:
> Back in late 90's ObjecAda had projects. The project file had extension literally *.prj.
....and still has, by the way :-).

On 28.09.22 20:28, Stephen Leake wrote:

>>> Until a couple of days ago I had never heard the term in reference to Ada Programming.
>>
>> It always existed. E.g. Ada 83 Reference Manual called it "the program
>> library". See ARM 83 (10.4)
>
> Which is literally not "project", although it is a similar concept.

Just as you say, a project can be more than a library
(of library_items, LRM 10), but I think one can order the concepts
library and project.
A project typically uses a library from which it then picks units
to be compiled, looked up, referred to, linked...

A statement taken from the docs of a Compiler (Sofcheck)
that is also used by ObjectAda reads

"The Ada program library contains all information needed
to support the separate compilation requirements of Ada."