← Back to branch summary

~larryprice/libertine-scope/fix-desktop-scope-load

« back to all changes in this revision

Viewing changes to README.md

  • Committer: Larry Price
  • Date: 2016-07-26 14:40:43 UTC
  • mfrom: (50.1.7 devel)
  • Revision ID: larry.price@canonical.com-20160726144043-zmpucgrx21d1a7wu
merge

Show diffs side-by-side

added added

removed removed

Lines of Context:
README.md
19
19
Testinmg the Scope
20
20
------------------
21
21
 
22
 
To test the built scope, it needs to be be installed into a staging area first.
23
 
That's because the Unity test tools have rigid assumptions about the layout of various
24
 
installed data files, and the division between the sources and the built
25
 
artifacts that the CMake toolchain delivers do not meet those assumptions.  SO
26
 
be it:  installing into a staging area is no great hassle, but if you forget to
27
 
do it in your compile/install/run cycle you will meet with frustration.
28
 
 
29
22
Without system installation, you can test the scope using the unity-scope-tool
30
23
package available in the Ubuntu archives.
31
24
 
32
 
Here's the typical build/install/test cycle.
33
 
 
34
 
    make install DESTDIR=/tmpstaging/
35
 
    unity-scope-tool /tmp/staging/usr/local/lib/unity-scopes/libertine-scope/libertine-scope.ini
36
 
 
 
25
    unity-scope-tool build/scope/apps/libertine-scope.ubuntu_libertine-scope.ini