Building Socket Programs

on:

• Linux with Eclipse,
• Mac OS X with Xcode, or
• Windows 10 with Visual Studio 2015.

Sockets come standard with Linux. You should be able to just type "make" with the support code of this course and everything should work "out of the box."

Eclipse 3.6.1 project (graphical step-by-step):

• Start up Eclipse and choose your workspace, click "OK" (Fig. 1)

• Open the C/C++ perspective: on the main menu select "Window→Open Perspective→C/C++" (Fig. 2)

• Create a new project:
  • Select "File→New→C++ Project" (Fig. 3)
  • Give the project a name, e.g., "server". In the panels below, specify project type, "Executable→Empty Project", and select the appropriate toolchain (make, gcc, ld, etc.). Since we're not cross compiling, I choose the "Linux GCC" toolchain. Click "Finish" (Fig. 4)

• Add source files:
  • Right click on "server" on the first line of the "Project Explorer" tab on the left and select "Import" (Fig. 5)
  • On the "Select" page, choose "General→File System" and click "Next >" (Fig. 6)
  • On the "File system" page, either type in the directory where your source file resides, or click the "Browse" button next to "From directory:" to choose the directory (Fig. 7). In browsing for the directory, remember that you're telling eclipse the directory where your source files are, not the source files themselves.
  • Once the directory is identified, click on all the source files on the right pane you want imported, for example, the provided server.c (or click the directory name on the left pane to import all files in the directory), and click "Finish" (Fig. 8)

• Build and run the program:
  • On the main menu, select "Project→Build All" (Fig. 9)
  • Under the play button on the second menu bar (   ), click on the drop-down menu and select "Run Configurations..."" (Fig. 10)
  • On the "Create, manage, and run configurations" page, double click on "C/C++ Application" (Fig. 11). It will create a "server Debug" application.
  • On the "server Debug" configuration page, check "Enable auto build" and click "Run" (Fig. 12)
  • Click on the "Console" tab on the lower part of the central pane to view the console output of the program. Click on the red square to stop the program. (Fig. 13).

Sockets come standard with Mac OS X. You should be able to just type "make" with the support code of this course and everything should work "out of the box."

Xcode 5.0.2 project (graphical step-by-step):

• Create a new project:
  • Select "File→New→New Project" (Fig. 14).
  • Choose a template for your new project under OSX (not iOS):
    "Application→Command Line Tool" and click "Next" (Fig. 15).
  • Give your project a "Product Name", an "Organization Name", and a "Company Identifier", then select "Type" "C++", and click "Next" (Fig. 16).
  • A window pops up to prompt you where you want to put the new project folder. In this example I've decided to put the project folder on my Desktop. (Check "Create git repository on [My Mac]" if you want it.) Then click "Create" (Fig. 17).
  • In the leftmost pane, under "server" select "main.cpp" and "server.1" and right click to Delete them (Fig. 18). Click "Move to Trash" on the confirmation dialog box.

• Add source files:
  Right click on "server" at the top of the left most pane and select "Add Files to 'server'" (Fig. 19), select your file, for example, the provided server.c. You can choose whether to copy added items into the project folder. I've chosen not to make a copy but to leave them in the project folder instead, in this example. Click "Add" (Fig. 20).

• Click on the "play" icon at the top left corner to build and run the program (Fig. 21).
• For future reference: if your program requires command-line options (neither the server nor the client sample code requires command-line option): click your project name next to the "play" and "stop" icons on the top-line menu and select "Edit Scheme..." (Fig. 22) Go to the "Arguments" tab and click the '+' sign below "Arguments Passed On Launch". Type in your command-line options (Fig. 23).

• Installation/verification:
  Winsock has been part of standard Windows release since Windows NT 3.5 (late 1994). You can find Winsock files at the following locations on your system:
  • runtime libraries:
    C:\Windows\System32\ws2_32.dll
    on 64-bit Windows, additionally:
    C:\Windows\SysWOW64\ws2_32.dll


  • header files:
    C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include\WinSock2.h
["Program Files" for 32-bit Windows]

  • linker library:
    C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Lib\WS2_32.Lib
["Program Files" for 32-bit Windows]

• Later in your source files, include the following line:
  #include <winsock2.h>
#include <ws2tcpip.h>
  See sample code for an example of how to set up and use the Windows Sockets API (WSA) within your code.

• Visual Studio 2015 project (graphical step-by-step):
  • Create a new project:
    • Select "File→New→Project" (Fig. 24)
    • Choose a template for your new project:
      "Visual C++→Win32→Win32 Console Application", give the project a name, e.g., "server", along with location and solution name. Then click "OK" (Fig. 25)
    • On the "Welcome to the Win32 Application Wizard" page, click "Next >" (Fig. 26)
    • On the "Application Setting" dialog box, under "Additional options" tick "Empty project", then click "Finish" (Fig. 27)

  • Add source files:
    Right click on your project, for example, "server", on the third line of the "Solution Explorer" pane on the right to "Add→Existing Item" (Fig. 28),
    select your source and header file(s), for example, the provided server.c, and click "Add"

  • Add libraries:
    • Right click on "server" again and select "Properties" to tell the linker which libraries need to be added (Fig. 29)
    • At the very top of the "Property Pages", next to "Configuration:" choose "All Configurations" (Fig. 30)
    • Select "Configuration Properties→Linker→Input" on the left pane. Then in the "Additional Dependencies" field at the top of the right pane enter:

      ws2_32.lib;

      Double check that there are no spaces before or after the semicolon. Hit RETURN and then click "Apply" (Fig. 31).

  • To prevent the compiler from complaining of this or that API being deprecated, set the following compiler flags:
    • Staying in the "Property Pages", select "Configuration Properties→C/C++→Command Line" on the left pane. Then in the "Additional Options" box at the bottom of the right pane enter:

      /D_CRT_SECURE_NO_WARNINGS /D_WINSOCK_DEPRECATED_NO_WARNINGS

      Click "Apply".

  • Close the "Property Pages" pane by clicking "Ok", then click on the play button on the second menu bar (   ) to build and run the program. If you print out messages to the console, run the program using Ctl-F5 instead, to keep the cmd window from exiting after the program exits.

• OpenSSL for Windows: if your project needs to use OpenSSL functions, such as SHA1(), on Windows, you'll need to install OpenSSL. Download the developer, not the "Light," version of OpenSSL binaries for Windows (v1.0.2e as of this writing). The 32-bit and 64-bit choices here and below refer to the architecture you want to build for. Even if you're running 64-bit Windows, you can build for 32-bit architecture. (Since Visual Studio defaults to 32-bit (x86) configuration, it's simpler to just choose 32-bit everywhere and build for 32-bit.) For EECS 489, we only use the SHA1() function, so when prompted by the installer, you can install OpenSSL in your Desktop, for example. When prompted whether you want to copy OpenSSL DLLs to Windows system directory or the OpenSSL binaries directory, choose the latter. Once installed, you can distribute the OpenSSL files as follows:
  • 32-bit:
    • runtime libraries/dlls from OpenSSL-Win32\ (top folder) to:

      C:\Program Files (x86)\Microsoft Visual Studio *\VC\bin\

      We only need libeay32.dll, so you can choose to copy only that file.

    • linker libraries from OpenSSL-Win32\lib\ folder to:

      C:\Program Files (x86)\Microsoft Visual Studio *\VC\lib\

      Again, we only need libeay32.lib, so you can choose to copy only that file.

    • header files: copy the whole folder OpenSSL-Win32\include\openssl to:

      C:\Program Files (x86)\Microsoft Visual Studio *\VC\include\

  • 64-bit:
    • runtime libraries/dlls from OpenSSL-Win64\ (top folder) to:

      C:\Program Files (x86)\Microsoft Visual Studio *\VC\bin\amd64\

      We only need libeay32.dll, so you can choose to copy only that file.

    • linker libraries from OpenSSL-Win64\lib\ folder to:

      C:\Program Files (x86)\Microsoft Visual Studio *\VC\lib\amd64\

      Again, we only need libeay32.lib, so you can choose to copy only that file.

    • header files: copy the whole folder OpenSSL-Win64\include\openssl to:

      C:\Program Files (x86)\Microsoft Visual Studio *\VC\include\

      Only the header file opensslconf.h differs between the 32-bit and 64-bit versions.

  • You can then uninstall OpenSSL to remove the OpenSSL folder from your Desktop and Windows registry.

  To use SHA1() you must #include <openssl/sha.h> in your source file. Then in VS, append "libeay32.lib;" to your "Additional Dependencies" under "Configuration Properties→Linker→Input" for "All Configurations". Be sure not to include the quotes nor any spaces before or after libeay32.lib;.

  If you're using Cygwin, use Cygwin's setup program to install the "Devel→openssl-devel" package, then just type make to make the support code provided for this course.

References not cited:

• O'Steen's Transitioning from UNIX to Windows Socket Programming
• Tangentsoft's Winsock Programmer's FAQ