Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

Diff of /vxl-users-faq.html [d78633] .. [db1c4a] Maximize Restore

  Switch to unified view

a/vxl-users-faq.html b/vxl-users-faq.html
...
...
34
<hr>
34
<hr>
35
35
36
    </li>
36
    </li>
37
37
38
    <li>
38
    <li>
39
      <p class="question">I followed the VXL installation documentation, but found that some of the entries in the
39
      <p class="question">I followed the VXL installation documentation, but
40
        <code>
40
    found that the configuration output and/or entries in the
41
        CMakeCache.txt</code> file say that CMake could not find programs, paths, etc. Is this a problem?</p>
41
    <code>CMakeCache.txt</code> file say that CMake could not find programs,
42
      <p class="answer">No. VXL needs very little to build correctly (only a C/C++ compiler at worst), however it can make use of
42
    paths, etc. Is this a problem?</p>
43
      <p class="answer">No. VXL needs very little to build correctly (only a
44
    C/C++ compiler at worst), however it can make use of various system
43
  various system provided libraries, rather than build its own versions. CMake also looks for lots of system tools
45
    provided libraries, rather than build its own versions. CMake also looks
44
  so that it can understand the environment it is in. So having lots of <code>NOTFOUND</code> entries is quite normal. There is
46
    for lots of system tools so that it can understand the environment it is
47
    in. So having lots of <code>NOTFOUND</code> entries, or "<code>Could NOT
48
    find</code>" reports is quite normal. There is no need to worry unless
45
  no need to worry unless CMake displays a warning or error message while it runs.</p>
49
    CMake displays a warning or error message while it runs.</p>
46
50
47
<hr>
51
<hr>
48
52
49
    </li>
53
    </li>
50
54