Free how do you make wine software for linux

GNU make is a tool which controls the generation of executables and other non-source files of a program from the programs source files.
Make gets its knowledge of how to build your program from a file called the makefile, which lists each of the non-source files and how to compute it from other files. When you write a program, you should write a makefile for it, so that it is possible to use Make to build and install the program.
Capabilities of Make
- Make enables the end user to build and install your package without knowing the details of how that is done -- because these details are recorded in the makefile that you supply.
- Make figures out automatically which files it needs to update, based on which source files have changed. It also automatically determines the proper order for updating files, in case one non-source file depends on another non-source file.
As a result, if you change a few source files and then run Make, it does not need to recompile all of your program. It updates only those non-source files that depend directly or indirectly on the source files that you changed.
- Make is not limited to any particular language. For each non-source file in the program, the makefile specifies the shell commands to compute it. These shell commands can run a compiler to produce an object file, the linker to produce an executable, ar to update a library, or TeX or Makeinfo to format documentation.
- Make is not limited to building a package. You can also use Make to control installing or deinstalling a package, generate tags tables for it, or anything else you want to do often enough to make it worth while writing down how to do it.
Make Rules and Targets
A rule in the makefile tells Make how to execute a series of commands in order to build a target file from source files. It also specifies a list of dependencies of the target file. This list should include all files (whether source files or other targets) which are used as inputs to the commands in the rule.
Here is what a simple rule looks like:
target: dependencies ...
commands
...
When you run Make, you can specify particular targets to update; otherwise, Make updates the first target listed in the makefile. Of course, any other target files needed as input for generating these targets must be updated first.
Make uses the makefile to figure out which target files ought to be brought up to date, and then determines which of them actually need to be updated. If a target file is newer than all of its dependencies, then it is already up to date, and it does not need to be regenerated. The other target files do need to be updated, but in the right order: each target file must be regenerated before it is used in regenerating other targets.
Advantages of GNU Make
GNU Make has many powerful features for use in makefiles, beyond what other Make versions have. It can also regenerate, use, and then delete intermediate files which need not be saved.
GNU Make also has a few simple features that are very convenient. For example, the -o file option which says ``pretend that source file file has not changed, even though it has changed. This is extremely useful when you add a new macro to a header file. Most versions of Make will assume they must therefore recompile all the source files that use the header file; but GNU Make gives you a way to avoid the recompilation, in the case where you know your change to the header file does not require it.
However, the most important difference between GNU Make and most versions of Make is that GNU Make is free software.
Enhancements:
- Major bugfixes

Parallel Port Make project is a tool to build FreeBSD ports in parallel to fully take advantage of modern multi-core and processor machines.

Default: pportmake.py --clean -- cleanup --install -job=2 [port1] [portn]

Example: pportmake.py irc/irssi irc/epic

Advanced: pportmake.py -rSvD -j 10 irc/irssi

-h --help Show this help usage message
-c --clean Clean port before compiling
-C --cleanup Clean port after compiling
-d --deinstall Deinstall ports, implied by reinstall
-f --force Force a port and all dependancies to be installed
-G --noconfig Dont recursively configure options
-i --install Install port (default)
-j n --jobs=n Number of threads to use, 1 or 2 per CPU core
is recommended
Default is 2
-O args --options=foo List of arguments to pass to make.
E.g. -O -DX11=yes -DFOO
-r --reinstall Reinstall port and ALL dependancies
-S --maxspeed Try and speed up by maximising CPU usuage.
This may break some ports, use with caution
-w --noclean Dont make clean before compiling
-W --nocleanup Dont make clean after compiling
-v --verbose Be extra verbose
-V --version Show version information
-D --debug Show some debugging info
-P --pretend Dont actually alter the ports

NOTES: It is currently only safe to run 1 copy of this and not have other ports compiling simultaneously

DPKG::Make is a Perl module for cleanly generate an Debian package (.dpkg).

SYNOPSIS

use DPKG::Make;

# The "Manifest": list of files that will comprise the software package.
my @filelist=(tmproot/file1.txt,
tmproot/file2.txt,
tmproot/file3.txt,
tmproot/file4.txt);

my %doc; my %conf; my %metadata;

# Define special handling of files.
$doc{tmproot/file1.txt}=1;
$conf{tmproot/file2.txt}=1;

# Bare minimum metadata (descriptive data of the software package).
my $pathprefix=tmproot;
my $tag=test; # cannot use uppercase characters
my $version=0.1;
my $release=1;

# Highly descriptive metadata.
%metadata=(
vendor=>Excellence in Perl Laboratory,
summary=>a Test Software Package,
name=>$tag,
copyrightname=>...,
group=>base,
AutoReqProv=>no,
requires=>[()],
email=>joe@somewhere.com,
description=>This package is generated by DPKG::Make. .
This implements the .$tag. software package,
pre=>echo "You are installing a package built by DPKG::Make; .
DPKG::Make is available at http://www.cpan.org/.",
);

# Temporary "sandbox" (this should not be /tmp because this is deleted!).
my $buildloc=TempBuildLoc;

# The "execute" subroutine coordinates all of the DPKG building steps.
DPKG::Make::execute($tag,$version,$release,$arch,$buildloc,$pathprefix,
@filelist,%doc,%conf,
%metadata);

# You can also build a DPKG in more atomic steps; these three smaller
# steps are equivalent to the execute command.

# Step 1: Generate the rpm source location.
DPKG::Make::dpkgsrc($tag,$version,$release,$arch,$buildloc,$pathprefix,
@filelist,%doc,%conf,
%metadata);

# Step 2: Build the rpm and copy into the invoking directory.
DPKG::Make::compiledpkg($buildloc,$metadata{name},$version,
$release,$arch,
$currentdir,$invokingdir);

# Step 3: clean the location used to gather and build the rpm.
DPKG::Make::cleanbuildloc($buildloc);

makeutil is a set of portable public domain programs designed to support C/C++ projects. It provides tools for build operations outside of the normal compile/link pipeline.
It is designed to be unobtrusively included directly in your own software development project.
Here is a brief description of each tool:
- config: choose file based on platform
- ccinfo: name compiler used to compile program
- mksystype: determine operating system
- mkarray: convert input file to C array
- mkstring: convert input line to C string
- armor: convert binary file to ascii
- dearmor: convert encoded ascii file to binary
- textpack: compress files with precompiled frequency table
- textpand: uncompress files with precompiled frequency table
- ckey: create frequency table from input
- extract: extract files from an extract format text archive
- retract: create an extract format text archive
- addcr: add a t before every n
- delcr: delete the r from every rn
- unmake: process include directives in a Makefile