How to create doc for C++/JAVA code in eclipse

The common tools that we used in the eclipse is deoxygen

The good point for this one is that it can be used in both JAVA and C/C++ project. So for misc projects, this one maybe the best choice. In fact, it is really hard to find a workable free UML tool in Eclipse C++ to turn your code into the class hierarchy diagram. But this one can give this feature plus the auto index the docs.

Usage for it also is very easy.

1. Just install it in my ubuntu.

sudo apt-get install doxygen

2. And then in the eclipse install one plugin for doxygen: Eclox

3. Under the eclipse project create a folder of doc.

4. New -> other file-> others….. to create a doxyfile under this folder. Then you can use context menu to edit this file and make your selection for configuration for doxygen.

5: Common configurations summary here:

Input of source files folder (h, cpp, java etc.)

output folder

HTML with search and frame selected

Diagrams: use dot tool from the GraphViz….

Extraction mode: all entities and with crosss reference source-code…

6. Just use context menu “build documentation”, then you will get html/latex/rtf etc version docs for your code.

7. Then find the index.html in the created doc html folder to read the docs.






How to build and run the CMU Olympus-Ravenclaw dialog system framework – 2 ?

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:
cd .\MeetingLine\branches\2.6

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 : need these knowledge to debug.
What is Visual Studio version means – 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

How to build and run the CMU Olympus-Ravenclaw dialog system framework – 1 ?

CMU has developed many speech related projects and you can take a look from these two places:
Olympus is one of them.

Olympus dialog system is a speech system envoling from CMU Communictor in history. Current wiki page are at here:

From SVN and wiki, we can know Olympus ended around 2015. From SVN history log of the Olympus, most of the components in Olympus were done around 2000-2006. This project stop major work at 2010. From 2010, they almost do nothing anymore on project code level.

To know about the Olympus, it is better to make it run and test it out, here I will note down how to to make the Olympus runs.


0. Take some time reading the wiki pages to get some clues, but if you try it out by wiki instructions, you will faces many difficuties as wiki, code and enviroment are very outdate and mismatched, these will bring you many issues.

1. Install a windows 7 computer, try to get an old computer having windows 7. it only can run at win 7 .

2. Download and install tortoisesvn, this one you can choose latest version:

3. Get CMake use the exe install for windows , I choose 3.4.0 version at here, do not choose latest version, it maybe cause issues.

4. Install ActivePerl from ActiveState – i choose 5.22 version

5. Install Python 2.7

6. Install java 8 with netbeans IDE (must with netbean!), MUST install it under default folder, as later olympus script can only looking for ant of netbean under the default folders:
C:\Program Files…..


7. Install Visual Studio – this is a bit troublesome, I tested VS 2010, it must have the SP1 to work with CMake :


VS 2012 version should be better. later you will know reason.

8. Intall TTS Flite – this step I do not think it is useful, as olympus has the flite in already. Maybe very very old version use this step.

9. Now, all software are ready, we need to config system environment:

Set the windows ENV for these:
OLYMPUS_ROOT = C:\CMU\olympus\2.6.1
LOGIOS_ROOT = C:\CMU\olympus\2.6.1\Tools\logios

Second LOGIOS_ROOT maybe no need anymore.

10. So, now we cna check out code to C:\CMU\olympus\2.6.1

I alos check out the example and tutorials to some folders


11. I before start build there are some perl module need be installed:
ppm install Win32::RunAsAdmin
ppm install Win32::Env

12. Enter the powershell, try to build the source:

cd C:\CMU\olympus\2.6.1

OlympusBuild.bat has a bug on source, you should change its content to this:
perl Build\
So I just use OlympusRebuild.bat to build it.

12. If you are lucky, then your build could be success. But most of chance you will get some errors. As this system is very old and it is very sensitive to software versoins.

Appears successful…

13. As I use the VS 2010 (10.0), so I need to open the file to change some text there.

$self->{‘BuildSysExe’} = $msbuildpath.’v4.0.30319/’.’MSBuild.exe’; # v 11.0
$vers = ‘10.0’; // here change 11 to 10 to match my VS version

MSBuild.exe location is at v4.0.30319/ folder for both VS 11 and 10, so I need to change $vers in this script to match with my VS version 10. This in fact a bug in this file.

14. OK now we have the Olympus compiled and installed, and next step to to run some examples to see how it works.