Changeset 7ed0e9d
- Timestamp:
- 11/18/2015 05:29:40 AM (8 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 7.10, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 2cd6717
- Parents:
- 6b241ec
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/cmake.xml
r6b241ec r7ed0e9d 119 119 120 120 <para> 121 To test the results, issue: 122 <command>bin/ctest -j<replaceable><N></replaceable> -O 123 ../cmake-&cmake-version;-test.log</command>, 124 where 121 To test the results, issue: <command>bin/ctest 122 -j<replaceable><N></replaceable> -O 123 cmake-&cmake-version;-test.log</command>, where 125 124 <replaceable><N></replaceable> is an integer between 1 and the 126 number of threads of your processor, inclusive. For some systems, it may 127 be necessary to run the tests only for Qt4 using 128 <command>source setq4</command>, then 129 <command>export CXXFLAGS="-std=c++11"</command> (just before 130 <command>./bootstrap ...</command>) and remember to unset it after 131 finishing, with 132 <command>unset CXXFLAGS</command>. 133 The worst case we have obtained in problematic systems, without those 134 extra commands, was 98% of 447 tests passed. 135 <!-- Please, don't remove this comment, needed if tests start to fail 125 number of system cores. For some systems, it may be necessary to run 126 the tests only for Qt4 using <command>source setq4</command>, then 127 <command>export CXXFLAGS="-std=c++11"</command> before the 128 <command>./bootstrap ...</command>) command. If used, be sure to 129 <command>unset CXXFLAGS</command> after the tests. All the 130 problematic tests relate to the test procedures finding the correct 131 Qt files. Five of 447 test are known to fail under some circumstances. 132 133 <!-- Please, don't remove this comment, needed if tests start to fail 136 134 again. If you want to investigate a problem with a given "problem1-test", 137 135 use <command>bin/ctest -R "problem1-test"</command> and, to omit it, use
Note:
See TracChangeset
for help on using the changeset viewer.