/usr/include/votca/csg/version.h is in libvotca-csg2-dev 1.2.4-2.1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 | /*
* Copyright 2009-2011 The VOTCA Development Team (http://www.votca.org)
*
* Licensed under the Apache License, Version 2.0 (the "License");
* you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an "AS IS" BASIS,
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
* See the License for the specific language governing permissions and
* limitations under the License.
*
*/
/**
\mainpage VOTCA C++ reference
\section intro_sec Introduction
This page is the C++ code documentation of the VOTCA package (http://www.votca.org). The main target of
VOTCA is the implementation of systematic coarse-graining techniques. However, it offers a powerful,
object-oriented framework to develop analysis tools for particle based molecular simulations.
\section started_sec Getting started
To start developing custom analysis tools, a good place to start is the csgapps repository:
http://code.google.com/p/votca/source/browse/?repo=csgapps
It contains several small analysis tools which were implemented based upon the VOTCA framework. We highly
recomment to use an IDE such as Netbeans for development since it offers lots of guides to get started
with new code (code completion, code documentation popups, navigation thourh code, ...).
The main container for the whole structure is the Topology, so it is a good advise to get comfortable with
this class. Also the standard applications in csg/src/tools might help.
\section beginner_sec For beginners: how to avoid frustration
For those not familiar with object oriented code: don't try to dig into every single function in order to understand
what exactly is going on. This strategy only works for very small projects and is not intended for oject oriented programs.
Think about the code in layers of abstraction! Your main focus should be on the global structure and understand how
objects relate to each other. The code was designed that you don't have to redo and understand all the nasty details!
*/
#ifndef _csg_version_H
#define _csg_version_H
#include <string>
namespace votca { namespace csg {
const std::string & CsgVersionStr();
void HelpTextHeader(const std::string &tool_name);
}}
#endif /* _tools_version_H */
|