× Help save net neutrality! Learn more.
Home / patches
Name Modified Size Downloads / Week Status
Parent folder
guile 2013-03-20 0
libtool 2013-02-03 0
ed 2013-01-19 0
msys 2013-01-15 0
automake 2013-01-09 0
autoconf 2013-01-08 0
m4 2013-01-06 0
bash 2012-12-10 0
pthreads 2012-11-22 0
tetex 2012-11-22 0
binutils 2012-11-22 0
Totals: 11 Items  
* README_EN.txt * 2014.02.10 * gnubuilds_sourceforge 1. DESCRIPTION 2. LICENSE 3. PROJECT TERMS 4. A DOWNLOAD STORE DIRECTORY TREE 5. DOWNLOAD, READ AND INSTALL SEQUENCE 6. AUTHOR EMAIL ------------------------------------------------------------------------------- 1. DESCRIPTION ------------------------------------------------------------------------------- The GnuBuilds is a project to support building of a make projects under the cygwin, msys and mingw environments. It includes script wrappers around the build and test scripts from the original source packages, and includes scripts for automation of the "patch original sources", "build sources", "pack an output binaries" and "collect dependencies" targets including automatic logging of overall process. ------------------------------------------------------------------------------- 2. LICENSE ------------------------------------------------------------------------------- The Boost license (see included text file "license.txt" or http://www.boost.org/users/license.html) ------------------------------------------------------------------------------- 3. PROJECT TERMS ------------------------------------------------------------------------------- "project build environment" - a build environment which is represented by a project build scripts directory tree, environment variables and running backend system, for example, declared in the OSTYPE variable. "build scripts base package" - a package with set of scripts, tools and configurations files which is supported the basics of a project build environement. "build scripts project package" - a package with set of the build scripts, tools and configuration files for a corresponding "build scripts base package" and which dependent on it. Represents and descrides a project you want to build. "build scripts output package" - an archive package which is a result of build a "build script project package". "original sources package" - a package with original sources which can be built by corresponding "build scripts project package". Basically includes sources of the related project distributed as is without any patched files or patches. "original sources patch package" - a package with patches for the original sources which can be built by corresponding "build scripts project package". Basically includes patches in a predefined format described inside the package and required to build original sources without critical errors or including needed functionality. ------------------------------------------------------------------------------- 4. A DOWNLOAD STORE DIRECTORY TREE ------------------------------------------------------------------------------- <StoreRoot> - a root of the store directory tree | +- archive - an archive subdirectory to store an old files from | the store +- backends - the directory for all backends required to be installed | | before the build scripts usage | +- bin - a directory where stored a backend binaries | | | | | +- cygwin - a Cygwin backend files | | | | | +- mingw - a Mingw backend files | | | | | +- msys - a Msys backend files | | | | | +- msysdvlpr - a Msysdvlpr backend files (for build the Msys itself) | | | +- src - a directory where stored a backend sources | +- build_scripts - a directory where stored all build scripts files | | | +- base - a directory where stored a build scripts base | | packages | +- projects - a directory where stored a build scripts project | packages +- packages - a directory where stored a build scripts output | packages +- patches - a directory where stored a original sources patch | packages +- sources - a directory where stored the original sources packages ------------------------------------------------------------------------------- 5. DOWNLOAD, READ AND INSTALL SEQUENCE ------------------------------------------------------------------------------- The common example of the download and read process is looks like this: 1. Download a build scripts project package. 2. Read the "INSTALLATION", the "DEPENDENT BACKENDS" and the "DEPENDENT PACKAGES" sections in the README_EN.txt file from a build scripts project package. 3. Download a dependent build scripts base package. 4. Read the "INSTALLATION" section in the README_EN.txt file from a build scripts base package. 5. Download a dependent backend package or packages. 6. Download a dependent original sources patch package if exists. 7. Download a dependent original sources package. 8. Install a dependent backend package or packages. 9. Install a dependent build scripts base package. 10. Install a build scripts project package. 11. Install a dependent original sources package. 12. Install a dependent original sources patch package if exists. NOTE: As you see the download and search of package dependencies and installation order for packages are converse to each other. ------------------------------------------------------------------------------- 6. AUTHOR EMAIL ------------------------------------------------------------------------------- andry at inbox dot ru
Source: README_EN.txt, updated 2014-02-28

Thanks for helping keep SourceForge clean.

Screenshot instructions:
Windows
Mac
Red Hat Linux   Ubuntu

Click URL instructions:
Right-click on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies
X

Briefly describe the problem (required):

Upload screenshot of ad (required):
Select a file, or drag & drop file here.

Please provide the ad click URL, if possible:

Get latest updates about Open Source Projects, Conferences and News.

No, Thank you