[AWS] make gnatsockets, and "std" and SOCKET in makefile.conf, on Windows

Jocelyn Paine popx at j-paine.org
Wed Aug 20 15:24:45 CEST 2008


In makefile.conf in the top-level AWS directory, there are these lines:
  # AWS supports SSL (Secure Socket Layer). The SSL support is always built-in
  # AWS. To build AWS's demos will SSL support you need to set SOCKET to ssl, in
  # this case you must have installed OpenSSL on you computer. OpenSSL libraries
  # are distributed on Windows platforms therefore the SSL mode is the default
  # on this platform. (note that below ssl and openssl are aliases).
  #
  # SOCKET = [std/openssl/gnutls]
  #
  SOCKET	= std

The comment says "note that below ssl and openssl are aliases". But there
isn't an "ssl" in the list of permitted values, or anywhere else below.
Should this read "note that below std and openssl are aliases"?

Also, the comment says "To build AWS's demos will SSL support you need to
set SOCKET to ssl". Does the value of SOCKET affect anything apart from
the demos?

I'm confused, because of what I reported in my post at
http://lists.adacore.com/pipermail/aws/2008-August/000924.html . I
built AWS there using SOCKET = std; the makefile.conf comment suggested
the demos wouldn't then need SSL support; but the compiler complained
because it couldn't find ssl-thin.ads .

And one other question. In the AWS User's Guide at
https://libre.adacore.com/aws/aws-gpl-2.3.0.html#AWS_002eNet_002eStd ,
Section 2.2 says that to select the default implementation of sockets for
use with AWS.Net.Std, which is GNAT.Sockets (as opposed to AdaSockets),
one must give the command:
  make gnatsockets

I found out from
http://osdir.com/ml/lang.ada.sockets/2007-11/msg00017.html what the
difference between GNAT.Sockets and AdaSockets is, so I can see why
GNAT.Sockets is the default. But when I gave the command "make
gnatsockets" (from the top-level AWS directory), I got the error "No rule
to make target 'gnatsockets'".

Jocelyn Paine
http://www.spreadsheet-parts.org
+44 (0)7768 534 091



More information about the AWS mailing list