After olympus is compiled, it is a platform that will let other application can run. so we can get some examples from this SVN:
And ravenclaw has wiki page to teach two tutorials at here:
So let us take a look how to run applications.
1. After go through the example-systems codes, in all branch folders we can see the 2.0, 2.1, 2.5. 2.6 etc. These folders in fact are different application matches to the version of the olympus version. So as our olympus compiled is 2.6.1, so we only need to look for the 2.6 folders. Only two are in the examples:
2. Let us try the MeetingLine as example, build it first:
It will use the code of olympus and tools there to build this application.
3. After MeetingLine is built, let us make sure our speaker and micro working fine. and then we can just run it:
or SystemRun-JavaTTY.bat (This one runs through TTY, no sound I think.)
4. MeetingLine will open a GUI dashboard should come up, and all modules should be green.
Click “TTYRecognitionServer” and then type init_session into the input box.
The system should greet you by voice. and then you can then either type into the input box or speak into a connected microphone.
5. Tutorial1 and Tutorial2 both can run in same way, but they do not have 2.6 version folder in the branch folder.
So I use trunk folder version code to compile for 2.6 and it can compiled.
So you can try out each example by trunck version code to see if they are latest version is for 2.6 version or not.
Some notes about the Visual Studio versions and where is the MSBuild.exe location :
OlympusBuild.pm need these knowledge to debug.
What is Visual Studio version means
http://en.wikipedia.org/wiki/Microsoft_Visual_Studio#History – Visual Studio
Visual Studio 6.0 (1998)
Visual Studio .NET (2002) = version 7
Visual Studio .NET 2003 = version 7.1
Visual Studio 2005 = version 8
Visual Studio 2008 = version 9
Visual Studio 2010 = version 10
Visual Studio 2012 = version 11
Visual Studio 2013 = version 12
Visual Studio 2015 = version 14
Visual Studio 2017 = version 15
MSBuild in the previous versions of .NET Framework was installed with it but, they decided to install it with Visual Studio or with the package BuildTools_Full.exe.
The path for .NET framework installation is C:\Windows\Microsoft.NET\Framework[64 or empty][framework_version] The path when Visual Studio is installed is C:\Program Files (x86)\MSBuild[version]\Bin for x86 and, C:\Program Files (x86)\MSBuild[version]\Bin\amd64 for x64.
The path when BuildTools_Full.exe is installed is the same as when MSBuild is installed with Visual Studio.
As of 2013 msbuild ships with Visual Studio:
C:\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe
C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe
Before that msbuild shipped with the .NET Framework, up to version 4.5.1:
Just to add more information to the answer, in Windows 8.1, mine show up under
C:\Program Files (x86)\MSBuild\12.0\Bin
C:\Program Files (x86)\MSBuild\12.0\Bin\amd64
Don’t forget, older MSBuild versions are also updated when newer .NET frameworks are installed. For example, .NET Framework 4.5.1 also updates the .NET Framework 4.0 MSBuild version to 4.0.30319.18408