Lines Matching full:build
25 Q3.1 Do I need to build library to use STLport?
113 was build with SAME STLport headers---otherwise problems possible;
252 Now build library from a.cpp with string implementation Impl1;
253 then build application with b.cpp that use string implementation Impl2,
305 - build STLport library
306 - build STLport unit tests
309 build instructions (in most cases you definitely should reread
311 'file not found' message). Build instructions you can found in files
312 INSTALL, doc/README.*, build/README*, build/test/unit/README*.
324 after build/install compiler (i.e. paths from compiler origo).
333 - build and install compiler
341 Q3.1 Do I need to build a library to use STLport?
367 A3.3 See report about results of regression tests here: build/test/unit/STATUS.
375 (./configure --target=${CROSSTARGET}; cd build/lib; \
415 2. Ensure that you correctly built STLport---build and run unit tests
416 (build/test/unit) first with default settings, then with your settings
421 5. Compare your results with reported runs of unit tests (build/test/unit/STATUS).
