Use tabulations to indent CMake files, and remove trailing spaces
Merge pull request #72 from tpaviot/review/whitespace-cleanup

Whitespace cleanup
Let TKernel depend on ${CMAKE_DL_LIBS}

dlopen(), dlclose(), etc. are used in src/OSD/OSD_SharedLibrary.cxx,
thus TKernel must depend on ${CMAKE_DL_LIBS}.

This is not a problem just now because TKernel depends on Xmu which
itself links against libdl, but indirect dependencies cause trouble
and must be avoided.

Closes issue #78
Drop dependency of DRAWEXE against ${CMAKE_DL_LIBS}

It had been added in c3cc969, but log message does not explain why.
Remove it now, it should no more be needed thanks to ca78eea.
Merge pull request #80 from tpaviot/review/TKernel-depends-on-dl

Let TKernel depend on ${CMAKE_DL_LIBS}
Change OSD_FontMgr.cxx so that TKernel does not depend on X11

This class uses X11 calls to get the list of available fonts,
which is then used by OpenGl_FontMgr.cxx; see
  http://www.opencascade.org/org/forum/thread_21351/
for details about why this is a bad idea.

Here we use an environment variable to get the list of directories
where fonts have to be looked for.  If it is unset, default paths
are set when compiling:
 * On Darwin, /usr/X11/lib/X11/fonts:/Library/Fonts:/System/Library/Fonts
 * On other Unix, /usr/share/X11/fonts:/usr/share/fonts/X11

Closes issue #12.

Tkernel indirectly depends on libdl through libX11, so this commit
must be applied after ca78eea, otherwise applications may have
unresolved symbols when linking against TKernel.
Merge pull request #81 from tpaviot/review/TKernel-drop-X11-dependency

Change OSD_FontMgr.cxx so that TKernel does not depend on X11
Let TKService depend on X11 only when visualization component is compiled

This allows building OCAF and Data Exchange on computers without X11.

Closes issue #36.
Remove option OCE_VISUALISATION

This module contains only 3 components, it is unlikely that it
is needed alone.  It is pulled in by other modules, so make it
a pure dependency instead of an option, and rename it into
OCE_VISU_DEP.

This allows renaming OCE_VISUALISATION_FULL into OCE_VISUALISATION.
Rename OCE_VISUALISATION_FULL option into OCE_VISUALISATION
Merge pull request #82 from tpaviot/review/TKService-lower-depends-X11

Link TKService against X11 only when visualization component is compiled
Change installation path of CMake files

Hopefully we are now compliant with what is described at
  http://www.cmake.org/cmake/help/cmake-2-8-docs.html#command:find_package
and users will be able to run FIND_PACKAGE(OCE) to find OCE without
tweaking their configuration.
Added some BRepGProp and BRepAlgoAPI unit tests
Added GoogleTest 1.6.0 src

This commit follows GoogleTest project recommendation available
at: http://code.google.com/p/googletest/wiki/V1_6_FAQ
Item: "Why is it not recommended to install a pre-compiled copy
of Google Test (for example, into /usr/local)?"

The answer is reproduced below:
"""
In the early days, we said that you could install compiled Google Test
libraries on *nix systems using make install. Then every user of your
machine can write tests without recompiling Google Test.

This seemed like a good idea, but it has a got-cha: every user needs to
compile his tests using the same compiler flags used to compile the
installed Google Test libraries; otherwise he may run into undefined
behaviors (i.e. the tests can behave strangely and may even crash for no
obvious reasons).

Why? Because C++ has this thing called the One-Definition Rule: if two C++
source files contain different definitions of the same class/function/variable,
and you link them together, you violate the rule. The linker may or may not
catch the error (in many cases it's not required by the C++ standard to
catch the violation). If it doesn't, you get strange run-time behaviors that
are unexpected and hard to debug.

If you compile Google Test and your test code using different
compiler flags, they may see different definitions of the same
class/function/variable (e.g. due to the use of #if in Google Test).
Therefore, for your sanity, we recommend to avoid installing pre-compiled
Google Test libraries. Instead, each project should compile Google Test
itself such that it can be sure that the same flags are used for both
Google Test and the tests.
"""
Added an empty directory where GTest compile libraries will be built
Updated CMake builder to gtest-1.6.0 location
Added instructions to built gtest
oops, fixed wrong folder location
Merge branch 'tp/testsuite-work'
Change installation paths

 * header files: include/oce
 * env.{sh,csh}: lib/oce-X.Y.Z
 * src: share/oce-X.Y.Z

Rationale: These paths are more standard, at least on Unix.
Version is added to paths of runtime files, so that users may
have two different OCE versions, this may be needed if they
have one program linked against OCE X1.Y1.Z1 and another one
against OCE X2.Y2.Z2.

On the other hand, header files and .cmake files are not
versioned, because it would then be difficult to know which
version to use.

Closes issue #2.