file : README.flite.msvc.txt

2010-12-30 - Build using MSVC8 (2005), in XP - WIN32

Source : http://www.speech.cs.cmu.edu/flite/download.html

flite-1.4-release October 2009, clustergen voices, source 
 and Windows Mobile example app

25/12/2010 12:32 15,163,897 flite-1.4-release.tar.bz2

The source has a MSVC sln/vcproj file set, but these appeared
to take a multiple DLL approach. In this case I wanted a single
static library, for testing at least... so set about building
my own MSVC build file set.

Although the building was intended for MSVC8 (2005), the build files
are of MSVC6 format - DSW/DSP. Later versions of MSVC can read,
and convert these to its own format.

So the MSVC build steps are -
1. Load lib_flite.dsw into MSVC6,7,8,9,10,... of your choice.
2. Allow it to convert the files to its own format.
3. Build the project

Testing:

To run a test -

> bin\flite_main "Say this phrase for me"

or try the test-flite.bat batch file, and it should work. ;=))

Some History:

I had intended to use my 'amsrcs' scripts to build these build
files, but unforunately the source does not include the configure.ac,
and Makefile.am files, so was nearly impossible.

Instead I used my 'createdsp' scripts, to create the DSP files
for the project components I wanted, of course, beginning with
a static lib_flite.lib containing 'most' of the 'flite' code,
and adding executables, as desired...

This script takes an input file, and generates an appropriate
DSP file for that item, so the raw build consists of a set of
input file (*.inp) - 
lib_flite.inp  flite_main.inp flite_time_main.inp t2p_main.inp
These are run successifly by the 'buldme.bat' file. This generates
the set of DSP files, and then the DSW is hand crafted.

Added a flite_voice_list.c source to the 'flite_main' project. This
file is script generated in unix.

As stated, this source also includes the last DSW/DSP set I used, so you
can start building with those. Just load lib_flite.dsw into
MSVC (of your choice), and allow it to convert the files. It
should build pratically out-of-the-box...

The static library is stored in 'lib' directory, for use with
other applications, if, as, needed... The exectuables are stored
in 'bin'. In each case the Debug build has a 'd' appended to the
file name title.

Regards,
Geoff.
2010-12-30

msvc folder contents:
=========================================================

README.flite.msvc.txt - this file.
buildme-failed.bat - an attempt to use 'amsrcs' - failed
flite.inp

buildme.bat - using 'createdsp' to build dsp files using
lib_flite.inp - support for 4 english voices included
flite_main.inp - test application
other tests flite_time_main.inp, t2p_main.inp

response input files used to build -
lib_flite.dsw
flite_main.dsp flite_time_main.dsp lib_flite.dsp t2p_main.dsp

unistd.h - dummy, rather than altering the source

These could/should probably be located elsewhere...
flite_version.h
flite_voice_list.c

flite-1.4-patch.txt - diff to flite-1.4-release.tar.bz2

test-flite.bat - run some quick tests after the build.

==========================================================

Other Programmer Notes:
-----------------------

In the linux build, the created config/config contains the default
language, voice, and lexicon - say
FL_LANG = usenglish
FL_VOX  = cmu_us_kal
FL_LEX  = cmulex
and from config/default.lv
LEXES = cmulex
LANGS = usenglish
VOXES = cmu_us_kal cmu_time_awb cmu_us_kal16 \
 cmu_us_awb cmu_us_rms cmu_us_slt
and then in main/Makefile:VOICES=$(VOXES)
lang/Makefile:BUILD_DIRS = $(LEXES) $(LANGS) $(VOXES)

Then VOICES is fed to tools/make_voice_list - manually
code for 4 four us voices - kal, kal16, awb, slt

# eof - README.flite.msvc.txt
