Panotools::Makefile::Utils man page on Fedora

Man page or keyword search:  
man Server   31170 pages
apropos Keyword Search (all sections)
Output format
Fedora logo
[printable version]

Panotools::Makefile::UUser(Contributed Perl DocumPanotools::Makefile::Utils(3)

NAME
       Panotools::Makefile::Utils - Makefile syntax

SYNOPSIS
       Simple interface for generating Makefile syntax

DESCRIPTION
       Writing Makefiles directly from perl scripts with print and "\t" etc...
       is prone to error, this library provides a simple perl interface for
       assembling Makefile rules.

       See Panotools::Makefile::Rule and Panotools::Makefile::Variable for
       object classes that you can use to contruct makefiles.

USAGE
       Access the current platform name (MSWin32, linux, etc...):

	 print platform;

       Define a different platform and access the new name:

	 platform ('MSWin32');
	 print platform;

       Reset platform to default:

	 platform (undef);

       Take a text string (typically a single filename or path) and
       quote/escape spaces and special characters to make it suitable for use
       as a Makefile 'target' or 'prerequisite':

	 $escaped_target = quotetarget ('My Filename.txt');
	 $escaped_prerequisite = quoteprerequisite ('My Filename.txt');

       Note that the =;:% characters are not usable as filenames, they may be
       used as control characters in a target or prerequisite.	An exception
       is the : in Windows paths such as C:\WINDOWS which is understood by gnu
       make.

       * and ? are wildcards and will be expanded.  You may find that it is
       possible to use these as actual characters in filenames, but this
       assumption will lead to subtle errors.

       $ can be used in a filename, but when used with brackets, ${FOO} or
       $(BAR), will be substituted as a make variable.

       Targets starting with . are special make targets and not usable as
       filenames, the workaround is to supply a full path instead of a
       relative path.  i.e: /foo/bar/.hugin rather than .hugin

       Additionally the ?<>*|"^\ characters are not portable across
       filesystems (e.g.  USB sticks, CDs, Windows) and should be avoided in
       filenames.

       Take a text string, typically a command-line token, and quote/escape
       spaces and special characters to make it suitable for use in a Makefile
       command:

	 $escaped_token = quoteshell ('Hello World');

perl v5.14.1			  2010-04-07	 Panotools::Makefile::Utils(3)
[top]

List of man pages available for Fedora

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net