A.3 Build and Install on Windows with Visual Studio C++ 6

Once the lyric-src-release.tar.gz is donwloaded you can extract the archive with the WinZip utility, which can be found at http://www.winzip.com. Double click on the lyric-src-release.tar.gz file where you downloaded it, and say Yes to decompress the archive in a temporary folder. Then click on the Extract button to get into the extraction dialog, as shown in Figure A.1.

Graphic browser needed to see picture

Figure A.1: WinZip extraction dialog.

In the extraction dialog, make sure that All files is selected, and that Use folder names is checked, as shown in Figure A.1. Then select a path to extract LYRIC to. Finally press the Extract button to launch the extraction.

Now open the Explorer and locate the Microsoft Visual Studio workspace file msdev6.dsw. As shown in Figure A.2, this file is located in the ports/win32/msdev6 directory in the LYRIC source hierarchy.

Graphic browser needed to see picture

Figure A.2: Path to the msdev6.dsw file.

At least Microsoft’s Visual Studio C++ package must be installed on the workstation in order be able to build LYRIC. Visit Microsoft’s site at http://www.microsoft.com if you need to purchase a legal copy of the Visual Studio C++ package.

Once Visual Studio C++ showed up select Batch Build... from the Build menu, as shown in Figure A.3.

Graphic browser needed to see picture

Figure A.3: Select Batch Build... from the Build menu.

In the Batch Build dialog that shows up, as shown in Figure A.4, select the LYRIC libraries you want to build. Check or uncheck the boxes in front of each project. Begin with unckecking all test_ projects first. These are LYRIC test projects, and of no use during the libraries building phase.

The choice of the libraries to build will vary depending on what kind of project using LYRIC you will build. Each project will compile LYRIC with different C++ code generation settings. As a rule of thumb use the LYRIC library that matches with the code generation you set in your third party project. Table A.1 gives the code generation used for each project/library.

Graphic browser needed to see picture

Figure A.4: Batch Build dialog window.

A selection like the one shown in Figure A.4 will build all available types of LYRIC libraries. All produced static libraries have the acronym of their code generation type in their name, except that the underscore has become a minus-sign, and lyric.dll and lyric.lib are reserved for the DLL and its link table.

ProjectCode Generation

dll_mt Dynamic linked library, Multithreaded
lib_mt Static library, Multithreaded
lib_mtdllStatic library, Multithreaded DLL
lib_st Static library, Single-Threaded

Table A.1: LYRIC projects explained.

You will now have to enter the various msdev6 sub-directories and copy manually the built libraries to your prefered location. Don’t descend into the Debug and/or Release sub-directories Visual Studio created during the build. The libraries are in the project directory. Debug versions of LYRIC have a -g in their name. Thus even when installed in a common directory, their will be no name clashes. You also have to copy the content of the lyric-src-version/include/lyric directory in a - for your system - sensible location.