gnubuilds Files

* README_EN.txt
* 2012.11.22
* pthreads-2.8.0-patches

1. DESCRIPTION
2. INSTALLATION
3. patchlist.ini format
4. AUTHOR EMAIL 

-------------------------------------------------------------------------------
1. DESCRIPTION
-------------------------------------------------------------------------------
Pthreads package patches fixing build targets under GCC v3.4.4.

-------------------------------------------------------------------------------
2. INSTALLATION
-------------------------------------------------------------------------------
Apply all files mentioned in the patchlist.ini from platform specific
subdirectory.

-------------------------------------------------------------------------------
3. patchlist.ini format
-------------------------------------------------------------------------------
Formats:
  1. [<CommandModificator>]<PatchFilePath>[:[<PatchCurDirPath>]
       [:<PatchAttributes>]]
  2. [<CommandModificator>]<PatchFilePath>:[<PatchCurDirPath>]:
       [<PatchingFileInputPath>]:<PatchingFileOutputPath>[:<PatchingFileAttr>
 <PatchFilePath>:
    Represents the patch file or the executable to run. Has 2 formats, first -
    for the patch file, second - for the executable. If the <PatchCurDirPath>
    is defined, then is uses as the current durectoty before run the
    <PatchFilePath> patch.
 <PatchCurDirPath>:
    Current directory which switched to before a run patch or executable.
    Has meaning only for the relative input/output paths.
 <CommandModificator>:
   - $:
     Enables specific parameters to evaluate before being passed into it's
     arguments.
     If defined, then ON logic is active, otherwise - OFF logic is active.
     ON logic:
     1. if the <PatchFilePath> is relative, then it does prefixed by the
        $TargetInputDirPath variable.
     2. if the <PatchingFileInputPath> is relative, then it does not prefixed.
     3. if the <PatchingFileOutputPath> is relative, then it does not prefixed.
     OFF logic:
     1. if the <PatchFilePath> is relative, then it does prefixed by the
        $TargetInputDirPath variable.
     2. if the <PatchingFileInputPath> is relative, then does prefixed by the
        $TargetInputDirPath variable.
     3. if the <PatchingFileOutputPath> is relative, then does prefixed by the
        $TargetOutputDirPath variable.
 <PatchAttributes>:
   Arguments for the patch utility in the same order.
 <PatchingFileAttr>:
   Arguments for the executable in the same order.

EXAMPLES:
 examples/patch_example.patch
 examples/patch_example.patch::-u --fuzz=0 -p0
 examples/patch_example.sh::RelativeInputPath/InputFile:RelativeOutputPath/OutputFile
 examples/patch_example.exe::/AbsoluteInputPath/InputFile:/AbsoluteOutputPath/OutputFile
 $examples/patch_example.sh::$SomeVariable1/InputPath/InoutFile:$SomeVariable2/OutputPath/OutputFile
 $examples/patch_example.sh:$TargetOutputDirPath/Subdir1:Subdir2/InoutFile:$TargetOutputDirPath/OutputPath/OutputFile

-------------------------------------------------------------------------------
4. AUTHOR EMAIL
-------------------------------------------------------------------------------
andry at inbox dot ru