diff options
| author | Ivan Maidanski <ivmai@mail.ru> | 2021-11-23 10:00:05 +0300 |
|---|---|---|
| committer | Ivan Maidanski <ivmai@mail.ru> | 2021-11-23 11:30:59 +0300 |
| commit | 14cda6536f394e841bce4b9f91a46c9b3f18217c (patch) | |
| tree | 0a851fc287e3c1f929ad2b996fdc6dc5bd9afc05 /README.md | |
| parent | 5defdcc827e78a896ea7235c9bf4560cb26697a9 (diff) | |
| download | bdwgc-14cda6536f394e841bce4b9f91a46c9b3f18217c.tar.gz | |
Reformat README.md to avoid too long lines where possible
* README.md (Installation and Portability): Reformat a paragraph about
the build process based on Makefile.direct.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 22 |
1 files changed, 11 insertions, 11 deletions
@@ -217,17 +217,17 @@ with a single compiler invocation, like this: gcc -I include -o gctest tests/test.c extra/gc.c && ./gctest -Below we focus on the collector build using classic makefile. -For the Makefile.direct-based process, typing `make check` instead of `make` -will automatically build the collector and then run `setjmp_test` and `gctest`. -`setjmp_test` will give you information about configuring the collector, which is -useful primarily if you have a machine that's not already supported. gctest is -a somewhat superficial test of collector functionality. Failure is indicated -by a core dump or a message to the effect that the collector is broken. gctest -takes about a second to two to run on reasonable 2007 vintage desktops. It may -use up to about 30 MB of memory. (The multi-threaded version will use more. -64-bit versions may use more.) `make check` will also, as its last step, -attempt to build and test the "cord" string library.) +Below we focus on the collector build using classic makefile. For the +Makefile.direct-based process, typing `make check` instead of `make` will +automatically build the collector and then run `setjmp_test` and `gctest`. +`setjmp_test` will give you information about configuring the collector, which +is useful primarily if you have a machine that's not already supported. +gctest is a somewhat superficial test of collector functionality. Failure is +indicated by a core dump or a message to the effect that the collector is +broken. gctest takes about a second to two to run on reasonable 2007 vintage +desktops. It may use up to about 30 MB of memory. (The multi-threaded +version will use more. 64-bit versions may use more.) `make check` will also, +as its last step, attempt to build and test the "cord" string library.) Makefile.direct will generate a library libgc.a which you should link against. Typing "make cords" will build the cord library (libcord.a). |