revi-archive/xz-archive
1
0
Fork 0
mirror of https://git.tukaani.org/xz.git synced 2024-04-04 12:36:23 +02:00
Code Activity
xz-archive/debug
History
Lasse Collin f9907503f8 Build: Remove the static/dynamic tricks. 
Most distros want xz linked against shared liblzma, so
it doesn't help much to require --enable-dynamic for that.
Those who want to avoid PIC on x86-32 to get better
performance, can still do it e.g. by using --disable-shared
to compile xz and then another pass to compile shared liblzma.

Part of these static/dynamic tricks were needed for Windows
in the past. Nowadays we rely on GCC and binutils to do the
right thing with auto-import. If the Autotooled build system
needs to support some other toolchain on Windows in the future,
this may need some rethinking.
2010-10-05 14:13:16 +03:00
..
crc32.c Update the debug programs so that they compile again. 2009-11-14 19:45:39 +02:00
full_flush.c Rename MIN() and MAX() to my_min() and my_max(). 2010-05-26 10:36:46 +03:00
hex2bin.c Put the interesting parts of XZ Utils into the public domain. 2009-04-13 11:27:40 +03:00
known_sizes.c Fix compilation of debug/known_sizes.c. 2010-05-26 10:30:20 +03:00
Makefile.am Build: Remove the static/dynamic tricks. 2010-10-05 14:13:16 +03:00
memusage.c Update the debug programs so that they compile again. 2009-11-14 19:45:39 +02:00
README Added the debug directory and the first debug tool 2008-01-18 20:18:08 +02:00
repeat.c Put the interesting parts of XZ Utils into the public domain. 2009-04-13 11:27:40 +03:00
sync_flush.c Rename MIN() and MAX() to my_min() and my_max(). 2010-05-26 10:36:46 +03:00
translation.bash Add translations.bash and translation notes to README. 2010-09-23 14:03:10 +03:00

README 

Debug tools
-----------

    This directory contains a few tiny programs that may be helpful when
    debugging LZMA Utils.

    These tools are not meant to be installed. Often one needs to edit
    the source code a little to make the programs do the wanted things.
    If you don't know how these programs could help you, it is likely
    that they really are useless to you.

    These aren't intended to be used as example programs. They take some
    shortcuts here and there, which correct programs should not do. Many
    possible errors (especially I/O errors) are ignored. Don't report
    bugs or send patches to fix this kind of bugs.