Re: Porting Ada code to Linux

[Michael Bode <m.g.bode@web.de>]

"Howard" <Howard.Parrish@peterson.af.mil> writes:

> The Ada libs are;
>
> Win32
> Win32-Utils
> Win32-Winbase (pragmas to VCPP winbase.h lib)
> Win32-Windef
> Win32-Winnt
>
> Stdarg
> Stdarg-Impl
> Stdarg-Inst
> Stdarg-Machine
>
> These are all Ada packages, and these name represent specs, and bodies,
> so named.
>
> So, we are going to have to compile the Ada code, then link it with the
> new C++ code.  We are using the Gnu-G++ compiler linker, and we will
> need to be able to link in the Ada object files with our C++ files.  We
> have to find a way to replace, or port, the mentioned Ada libs.
>
> The "Winbase" dependancy on the Visual C++ files is problematic, at
> best...

The Win32... things are bindings to the Windows API. You need to find
out what Windows functions your app needs and then find equivalent
Linux (or POSIX) APIs (Florist is an Ada binding to POSIX). These will
probably not be 1:1 equivalences (creating a file in Win32 is
different from creating a file in POSIX).  

The Win32 functions could e.g. be GUI functions (create a window,
handle windows message, draw a line, create a dialog box). Then you
have to decide if you want to implement that functionality using raw
X11 or some GUI toolbox like GTK+ (GtkAda is an Ada binding to
GTK+). Or it could be registry access functions. There is no registry
in Linux.

-- 
Michael Bode