Building and Installing SVMT

Building the SVMT client and server applications require to have the source code of Stellarium and SVMT itself. Both code trees are managed by the bazaar VCS and hosted launchpad (https://launchpad.net/stellarium and https://launchpad.net/svmt). In order to build you need to install the bzr tool, the cmake tool (> 2.6) and the Qt library (> 4.7.0).

Building and packaging the binary SVMT client

After installing the dependencies, follow the following instructions to build the Client:

• Get the last version of the source code from the trunk:

  bzr co lp:stellarium
  bzr co lp:svmt
  

• Compile stellarium as described on the Stellarium wiki for linux, windows or MacOSX with the difference that you have to tell cmake to build the SVMT plugin as well by setting the USE_PLUGIN_SVMT variable to true, and setting the SOURCE_SVMT_PATH to the full path pointing to the svmt directory that you just checked out from bzr.
• This technical documentation can also be generated by running the make svmtapidoc command in the build directory.

You should now have a running Stellarium binary which automatically includes the SVMT client plugin.

Packaging

TODO

Building and deploying the SVMT Web Service

It is recommended to build the queryEngine cgi directly on the server where it will be used (to be binary compatible).

Get the last version of the source code from the trunk:

bzr co lp:stellarium
bzr co lp:svmt

and compile the qmake based project located in svmt/SVMTServer/:

cd svmt/SVMTServer
qmake
make

this should produce a queryEngine binary which is actually a cgi.

In order to obtain a fully functional SVMT Web Service, we now need to deploy all the elements needed by the client on our web server so that it matches the directory tree described in the architecture section, that is:

{rootDir}/1.0.1/gui/
{rootDir}/1.0.1/fieldsList.json
{rootDir}/1.0.1/queryEngine

the gui/ directory should contain all the content of the svmt/data/gui directory (.qml and .png files), the file fieldsList.json should be a copy of the svmt/data/fieldsList.json file.

Finally, the queryEngine is the binary cgi what we have compiled in the previous step. However in an usual apache configuration, cgi programs cannot be placed in the same directory as for static content but rather in the cgi-bin/ directory. One way to deal with that is to modify the apache config file as described below. Also it is a usefull optimization to allow the deflate plugin to compress data, as this is supported by the client.

ScriptAliasMatch ^/1.0.1/queryEngine /path/to/cgi-bin/1.0.1/queryEngine

<Directory "/path/to/cgi-bin">
    AddOutputFilterByType DEFLATE text/plain
    AllowOverride None
    Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
    Order allow,deny
    Allow from all
</Directory>