view release on metacpan or search on metacpan
A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.
]
INSTALLATION
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Algorithm/Voting/Plurality.pm view on Meta::CPAN
=pod
=head1 NAME
Algorithm::Voting::Plurality - use "Plurality" to decide the sole winner
=head1 SYNOPSIS
# construct a "ballot box"
use Algorithm::Voting::Ballot;
lib/Algorithm/Voting/Plurality.pm view on Meta::CPAN
=head1 METHODS
=head2 Algorithm::Voting::Plurality->new(%args)
Constructs a "ballot box" object that will use the Plurality criterion to
decide the winner. Optionally, specify a list of candidates; any ballot added
to the box that does not indicate one of the listed candidates throws an
exception.
Example:
view all matches for this distribution
view release on metacpan or search on metacpan
t/Relativity.test view on Meta::CPAN
to its structure the largest possible logical unity. The practice, for
example, of seeing in a "distance" two marked positions on a
practically rigid body is something which is lodged deeply in our
habit of thought. We are accustomed further to regard three points as
being situated on a straight line, if their apparent positions can be
made to coincide for observation with one eye, under suitable choice
of our place of observation.
If, in pursuance of our habit of thought, we now supplement the
propositions of Euclidean geometry by the single proposition that two
points on a practically rigid body always correspond to the same
t/Relativity.test view on Meta::CPAN
of these operations required is the numerical measure of the distance
AB. This is the basis of all measurement of length. *
Every description of the scene of an event or of the position of an
object in space is based on the specification of the point on a rigid
body (body of reference) with which that event or object coincides.
This applies not only to scientific description, but also to everyday
life. If I analyse the place specification " Times Square, New York,"
**A I arrive at the following result. The earth is the rigid body
to which the specification of place refers; " Times Square, New York,"
is a well-defined point, to which a name has been assigned, and with
which the event coincides in space.**B
This primitive method of place specification deals only with places on
the surface of rigid bodies, and is dependent on the existence of
points on this surface which are distinguishable from each other. But
we can free ourselves from both of these limitations without altering
t/Relativity.test view on Meta::CPAN
Square, London". We have changed this to "Times Square, New York", as
this is the most well known/identifiable location to English speakers
in the present day. [Note by the janitor.]
**B It is not necessary here to investigate further the significance
of the expression "coincidence in space." This conception is
sufficiently obvious to ensure that differences of opinion are
scarcely likely to arise as to its applicability in practice.
*** A refinement and modification of these views does not become
necessary until we come to deal with the general theory of relativity,
t/Relativity.test view on Meta::CPAN
SPACE AND TIME IN CLASSICAL MECHANICS
The purpose of mechanics is to describe how bodies change their
position in space with "time." I should load my conscience with grave
sins against the sacred spirit of lucidity were I to formulate the
aims of mechanics in this way, without serious reflection and detailed
explanations. Let us proceed to disclose these sins.
It is not clear what is to be understood here by "position" and
"space." I stand at the window of a railway carriage which is
t/Relativity.test view on Meta::CPAN
Lightning has struck the rails on our railway embankment at two places
A and B far distant from each other. I make the additional assertion
that these two lightning flashes occurred simultaneously. If I ask you
whether there is sense in this statement, you will answer my question
with a decided "Yes." But if I now approach you with the request to
explain to me the sense of the statement more precisely, you find
after some consideration that the answer to this question is not so
easy as it appears at first sight.
After some time perhaps the following answer would occur to you: "The
t/Relativity.test view on Meta::CPAN
in which the conception " simultaneous " plays a part. The concept
does not exist for the physicist until he has the possibility of
discovering whether or not it is fulfilled in an actual case. We thus
require a definition of simultaneity such that this definition
supplies us with the method by means of which, in the present case, he
can decide by experiment whether or not both the lightning strokes
occurred simultaneously. As long as this requirement is not satisfied,
I allow myself to be deceived as a physicist (and of course the same
applies if I am not a physicist), when I imagine that I am able to
attach a meaning to the statement of simultaneity. (I would ask the
reader not to proceed farther until he is fully convinced on this
t/Relativity.test view on Meta::CPAN
places A and B, where the lightning occurs, meet each other at the
mid-point M of the length A arrow B of the embankment. But the events
A and B also correspond to positions A and B on the train. Let M1 be
the mid-point of the distance A arrow B on the travelling train. Just
when the flashes (as judged from the embankment) of lightning occur,
this point M1 naturally coincides with the point M but it moves
towards the right in the diagram with the velocity v of the train. If
an observer sitting in the position M1 in the train did not possess
this velocity, then he would remain permanently at M, and the light
rays emitted by the flashes of lightning A and B would reach him
simultaneously, i.e. they would meet just where he is situated. Now in
t/Relativity.test view on Meta::CPAN
of transmission c relative to the embankment and relative to the train
? This question leads to a quite definite positive answer, and to a
perfectly definite transformation law for the space-time magnitudes of
an event when changing over from one body of reference to another.
Before we deal with this, we shall introduce the following incidental
consideration. Up to the present we have only considered events taking
place along the embankment, which had mathematically to assume the
function of a straight line. In the manner indicated in Section 2
we can imagine this reference-body supplemented laterally and in a
vertical direction by means of a framework of rods, so that an event
t/Relativity.test view on Meta::CPAN
THE BEHAVIOUR OF MEASURING-RODS AND CLOCKS IN MOTION
Place a metre-rod in the x1-axis of K1 in such a manner that one end
(the beginning) coincides with the point x1=0 whilst the other end
(the end of the rod) coincides with the point x1=I. What is the length
of the metre-rod relatively to the system K? In order to learn this,
we need only ask where the beginning of the rod and the end of the rod
lie with respect to K at a particular time t of the system K. By means
of the first equation of the Lorentz transformation the values of
these two points at the time t = 0 can be shown to be
t/Relativity.test view on Meta::CPAN
man walking along the carriage, or of the moving point in the present
section. If we denote the velocity of the light relative to the tube
by W, then this is given by the equation (A) or (B), according as the
Galilei transformation or the Lorentz transformation corresponds to
the facts. Experiment * decides in favour of equation (B) derived
from the theory of relativity, and the agreement is, indeed, very
exact. According to recent and most excellent measurements by Zeeman,
the influence of the velocity of flow v on the propagation of light is
represented by formula (B) to within one per cent.
t/Relativity.test view on Meta::CPAN
it has considerably simplified the theoretical structure, i.e. the
derivation of laws, and -- what is incomparably more important -- it
has considerably reduced the number of independent hypothese forming
the basis of theory. The special theory of relativity has rendered the
Maxwell-Lorentz theory so plausible, that the latter would have been
generally accepted by physicists even if experiment had decided less
unequivocally in its favour.
Classical mechanics required to be modified before it could come into
line with the demands of the special theory of relativity. For the
main part, however, this modification affects only the laws for rapid
t/Relativity.test view on Meta::CPAN
The principle of relativity requires that the law of the concervation
of energy should hold not only with reference to a co-ordinate system
K, but also with respect to every co-ordinate system K1 which is in a
state of uniform motion of translation relative to K, or, briefly,
relative to every " Galileian " system of co-ordinates. In contrast to
classical mechanics; the Lorentz transformation is the deciding factor
in the transition from one such system to another.
By means of comparatively simple considerations we are led to draw the
following conclusion from these premises, in conjunction with the
fundamental equations of the electrodynamics of Maxwell: A body moving
t/Relativity.test view on Meta::CPAN
physical description of natural processes, neither of the reference
bodies K, K1 is unique (lit. " specially marked out ") as compared
with the other. Unlike the first, this latter statement need not of
necessity hold a priori; it is not contained in the conceptions of "
motion" and " reference-body " and derivable from them; only
experience can decide as to its correctness or incorrectness.
Up to the present, however, we have by no means maintained the
equivalence of all bodies of reference K in connection with the
formulation of natural laws. Our course was more on the following
Iines. In the first place, we started out from the assumption that
t/Relativity.test view on Meta::CPAN
are constrained to imagine -- after the manner of Faraday -- that the
magnet always calls into being something physically real in the space
around it, that something being what we call a "magnetic field." In
its turn this magnetic field operates on the piece of iron, so that
the latter strives to move towards the magnet. We shall not discuss
here the justification for this incidental conception, which is indeed
a somewhat arbitrary one. We shall only mention that with its aid
electromagnetic phenomena can be theoretically represented much more
satisfactorily than without it, and this applies particularly to the
transmission of electromagnetic waves. The effects of gravitation also
are regarded in an analogous manner.
t/Relativity.test view on Meta::CPAN
In the first place, it can be compared with the reality. Although a
detailed examination of the question shows that the curvature of light
rays required by the general theory of relativity is only exceedingly
small for the gravitational fields at our disposal in practice, its
estimated magnitude for light rays passing the sun at grazing
incidence is nevertheless 1.7 seconds of arc. This ought to manifest
itself in the following way. As seen from the earth, certain fixed
stars appear to be in the neighbourhood of the sun, and are thus
capable of observation during a total eclipse of the sun. At such
times, these stars ought to appear to be displaced outwards from the
sun by an amount indicated above, as compared with their apparent
t/Relativity.test view on Meta::CPAN
experiment, we recognise that there must also be cases in which the
experiment would be unsuccessful. We shall suppose that the rods "
expand " by in amount proportional to the increase of temperature. We
heat the central part of the marble slab, but not the periphery, in
which case two of our little rods can still be brought into
coincidence at every position on the table. But our construction of
squares must necessarily come into disorder during the heating,
because the little rods on the central region of the table expand,
whereas those on the outer part do not.
With reference to our little rods -- defined as unit lengths -- the
t/Relativity.test view on Meta::CPAN
the variably heated marble slab, and if we had no other means of
detecting the effect of temperature than the geometrical behaviour of
our rods in experiments analogous to the one described above, then our
best plan would be to assign the distance one to two points on the
slab, provided that the ends of one of our rods could be made to
coincide with these two points ; for how else should we define the
distance without our proceeding being in the highest measure grossly
arbitrary ? The method of Cartesian coordinates must then be
discarded, and replaced by another which does not assume the validity
of Euclidean geometry for rigid bodies.* The reader will notice
that the situation depicted here corresponds to the one brought about
t/Relativity.test view on Meta::CPAN
space-measurements by means of measuring-rods, as a litttle
consideration will show.
The following statements hold generally : Every physical description
resolves itself into a number of statements, each of which refers to
the space-time coincidence of two events A and B. In terms of Gaussian
co-ordinates, every such statement is expressed by the agreement of
their four co-ordinates x[1], x[2], x[3], x[4]. Thus in reality, the
description of the time-space continuum by means of Gauss co-ordinates
completely replaces the description with the aid of a body of
reference, without suffering from the defects of the latter mode of
t/Relativity.test view on Meta::CPAN
But speculations on the structure of the universe also move in quite
another direction. The development of non-Euclidean geometry led to
the recognition of the fact, that we can cast doubt on the
infiniteness of our space without coming into conflict with the laws
of thought or with experience (Riemann, Helmholtz). These questions
have already been treated in detail and with unsurpassable lucidity by
Helmholtz and Poincaré, whereas I can only touch on them briefly here.
In the first place, we imagine an existence in two dimensional space.
Flat beings with flat implements, and in particular flat rigid
measuring-rods, are free to move in a plane. For them nothing exists
t/Relativity.test view on Meta::CPAN
SIMPLE DERIVATION OF THE LORENTZ TRANSFORMATION
(SUPPLEMENTARY TO SECTION 11)
For the relative orientation of the co-ordinate systems indicated in
Fig. 2, the x-axes of both systems pernumently coincide. In the
present case we can divide the problem into parts by considering first
only events which are localised on the x-axis. Any such event is
represented with respect to the co-ordinate system K by the abscissa x
and the time t, and with respect to the system K1 by the abscissa x'
and the time t'. We require to find x' and t' when x and t are given.
view all matches for this distribution
view release on metacpan or search on metacpan
A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.
]
INSTALLATION
view all matches for this distribution
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use File::Path ();
use vars qw{$VERSION $MAIN};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '1.03';
view all matches for this distribution
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use File::Path ();
use vars qw{$VERSION $MAIN};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '1.08';
view all matches for this distribution
view release on metacpan or search on metacpan
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the
Library.
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
view all matches for this distribution
view release on metacpan or search on metacpan
corpus/libpalindrome/config.guess view on Meta::CPAN
pc:*:*:*)
# Left here for compatibility:
# uname -m prints for DJGPP always 'pc', but it prints nothing about
# the processor, so we play safe by assuming i586.
# Note: whatever this is, it MUST be the same as what config.sub
# prints for the "djgpp" host, or else GDB configure will decide that
# this is a cross-build.
echo i586-pc-msdosdjgpp
exit ;;
Intel:Mach:3*:*)
echo i386-pc-mach3
view all matches for this distribution
view release on metacpan or search on metacpan
- Add use strict and warnings to generated Install/Files.pm
modules (gh#17)
1.12 2020-02-02 06:00:12 -0700
- Add List::Util and Text::ParseWords prereqs back.
They were accidentally removed from prereqs in 1.10.
(gh#16)
1.11 2020-01-31 13:52:17 -0700
- Remove test dependency on Acme::Alien::DontPanic
(it should be optional) introduced in 1.10.
view all matches for this distribution
view release on metacpan or search on metacpan
- Document Inline 0.56 or better required for Inline integration
0.005_02 Sep 23, 2014
- silence Archive::Extract deprecation warning
(we explicitly specify it as a prereq)
- remove accidental undeclared dependency on YAML introduced in 0.005_01
- fixed test failures introduced in 0.005_01
0.005_01 Sep 22, 2014
- fixes with static library detection when pkg-config is not available (plicease gh#79, gh#75)
- support for Inline 'with' (plicease gh#71, gh#77, gh#78)
view all matches for this distribution
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
use vars qw{$VERSION};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '0.78';
view all matches for this distribution
view release on metacpan or search on metacpan
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
view all matches for this distribution
view release on metacpan or search on metacpan
property right claims or to contest validity of any such claims; this section has
the sole purpose of protecting the integrity of the free software distribution
system, which is implemented by public license practices. Many people have
made generous contributions to the wide range of software distributed through
that system in reliance on consistent application of that system; it is up to the
author/donor to decide if he or she is willing to distribute software through any
other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a
consequence of the rest of this License.
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alien/Build/Git.pm view on Meta::CPAN
This module is documentation only for how to use C<git> as a download source
from L<alienfile> + L<Alien::Build>. Depending on the project source that you
are using and the way your L<alienfile> is structured, you will want to use
one of three modules that come with the distribution C<Alien-Build-Git>.
See the synopsis above and the modules in the SEE ALSO section below. To decide
which you need.
Also please carefully consider NOT using one of these modules. If you can,
using http or ftp to download your target project will probably require fewer
and less error-prone dependencies.
view all matches for this distribution
view release on metacpan or search on metacpan
Revision history for Alien-Build-Plugin-Build-Make
0.02 2017-08-14 05:01:22 -0400
- Remove accidnetal dependency on Alien::gmake
0.01 2017-08-13 08:19:47 -0400
- initial version
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alien/Build/Plugin/Probe/GnuWin32.pm view on Meta::CPAN
sub init
{
my($self, $meta) = @_;
# we may decide to take this module out of core.
$meta->add_requires( 'configure' => 'Alien::Build::Plugin::Probe::GnuWin32' => 0 );
if($^O eq 'MSWin32')
{
$meta->register_hook(
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alien/Build.pm view on Meta::CPAN
sub build
{
my($self) = @_;
# save the evironment, in case some plugins decide
# to alter it. Or us! See just a few lines below.
local %ENV = %ENV;
my $stage = _path($self->install_prop->{stage});
$stage->mkpath;
view all matches for this distribution
view release on metacpan or search on metacpan
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
view all matches for this distribution
view release on metacpan or search on metacpan
property right claims or to contest validity of any such claims; this section has
the sole purpose of protecting the integrity of the free software distribution
system, which is implemented by public license practices. Many people have
made generous contributions to the wide range of software distributed through
that system in reliance on consistent application of that system; it is up to the
author/donor to decide if he or she is willing to distribute software through any
other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a
consequence of the rest of this License.
view all matches for this distribution
view release on metacpan or search on metacpan
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
view all matches for this distribution
view release on metacpan or search on metacpan
cp/codepress/index.html view on Meta::CPAN
<html>
<head>
<title>CodePress - Real Time Syntax Highlighting Editor written in JavaScript</title>
<style>
body {color:#000;background-color:white;font:15px georgia, "Lucida Grande", "Lucida Sans Unicode", Arial, Helvetica, sans-serif; letter-spacing:0.01em;margin:15px;}
p {margin:0 0 15px 0;}
a,a:visited {color:#7f0055;}
select {background:#ffffe1;}
button {margin-top:5px;}
button.actions {width:171px;font-family:arial;}
cp/codepress/index.html view on Meta::CPAN
/* CSS comment */
body {
color:#000;
background-color:white;
font:15px Georgia, "Lucida Grande", Arial, sans-serif;
letter-spacing:0.01em;
margin:15px;
}
p {
view all matches for this distribution
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
use vars qw{$VERSION $MAIN};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '0.91';
view all matches for this distribution
view release on metacpan or search on metacpan
function interface, you should look into FFI::Platypus, which uses the
more robust and currently maintained libffi, rather than the older ffcall.
This Alien package, built on Alien::Base, provides the FFCall library. FFCall
has been surpassed by libffi and is rather hard to obtain these days, but Perl's
original FFI module is built upon FFCall, so I decided to make it easy to distribute
FFCall on CPAN.
INSTALLATION
To install this module, run the following commands:
view all matches for this distribution
view release on metacpan or search on metacpan
src/Source/LibJXR/LICENCE
src/Source/LibJXR/README
src/Source/LibOpenJPEG/AUTHORS
src/Source/LibOpenJPEG/bio.c
src/Source/LibOpenJPEG/bio.h
src/Source/LibOpenJPEG/cidx_manager.c
src/Source/LibOpenJPEG/cidx_manager.h
src/Source/LibOpenJPEG/cio.c
src/Source/LibOpenJPEG/cio.h
src/Source/LibOpenJPEG/dwt.c
src/Source/LibOpenJPEG/dwt.h
src/Source/LibOpenJPEG/event.c
view all matches for this distribution
view release on metacpan or search on metacpan
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the
Library.
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
view all matches for this distribution
view release on metacpan or search on metacpan
doc/html/ChoiceList.html view on Meta::CPAN
<div class="TN_node" id="onPing">
<h3 class="TN_label">onPing</h3>
<div class="TN_content">
<p>This event is triggered when a choice in the list is "ping-ed", i.e.
either by clicking or by pressing the <code>RETURN</code> key.
Usually this means "select", but it is up to the event handler to decide
how to interpret the event.
The event handler may use <code>event.index</code> to know the index of the
ping-ed choice.</p>
</div>
view all matches for this distribution
view release on metacpan or search on metacpan
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
view all matches for this distribution
view release on metacpan or search on metacpan
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
view all matches for this distribution
view release on metacpan or search on metacpan
patches/Makefile_cd.mingw view on Meta::CPAN
CF_cd_pdflib = -c -Wall -O2 -Ipdflib/font -Ipdflib/pdcore -Ipdflib/pdflib -I../../zlib/include $(CF_cd_pdflib_EXTRA)
LF_cd_pdflib = -lzlib1 -lkernel32 -luser32 -lgdi32 -lwinspool -lcomdlg32 -ladvapi32 -lshell32 -luuid -loleaut32 -lole32 -lcomctl32 $(LF_cd_pdflib_EXTRA)
SLIB_cd_pdflib = ../lib/$(BUILDNICK)/libpdflib.a
DLIB_cd_pdflib = ../lib/$(BUILDNICK)/libpdflib.dll.a
ILIB_cd_pdflib = ../lib/$(BUILDNICK)/pdflib_alien_.dll
OBJS_cd_pdflib = ../obj/$(BUILDNICK)/cd_pdflib/pdflib.o ../obj/$(BUILDNICK)/cd_pdflib/p_3d.o ../obj/$(BUILDNICK)/cd_pdflib/p_actions.o ../obj/$(BUILDNICK)/cd_pdflib/p_afm.o ../obj/$(BUILDNICK)/cd_pdflib/p_annots.o ../obj/$(BUILDNICK)/cd_pdflib/p_bloc...
../obj/$(BUILDNICK)/cd_pdflib/pdflib.o : ./pdflib/pdflib/pdflib.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_3d.o : ./pdflib/pdflib/p_3d.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_actions.o : ./pdflib/pdflib/p_actions.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_afm.o : ./pdflib/pdflib/p_afm.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_annots.o : ./pdflib/pdflib/p_annots.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_block.o : ./pdflib/pdflib/p_block.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_bmp.o : ./pdflib/pdflib/p_bmp.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_ccitt.o : ./pdflib/pdflib/p_ccitt.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_cid.o : ./pdflib/pdflib/p_cid.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_color.o : ./pdflib/pdflib/p_color.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_document.o : ./pdflib/pdflib/p_document.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_draw.o : ./pdflib/pdflib/p_draw.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_encoding.o : ./pdflib/pdflib/p_encoding.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/p_fields.o : ./pdflib/pdflib/p_fields.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
patches/Makefile_cd.mingw view on Meta::CPAN
../obj/$(BUILDNICK)/cd_pdflib/pc_scope.o : ./pdflib/pdcore/pc_scope.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/pc_string.o : ./pdflib/pdcore/pc_string.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/pc_unicode.o : ./pdflib/pdcore/pc_unicode.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/pc_util.o : ./pdflib/pdcore/pc_util.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/pc_xmp.o : ./pdflib/pdcore/pc_xmp.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/ft_cid.o : ./pdflib/font/ft_cid.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/ft_corefont.o : ./pdflib/font/ft_corefont.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/ft_font.o : ./pdflib/font/ft_font.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/ft_hostfont.o : ./pdflib/font/ft_hostfont.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/ft_pdffont.o : ./pdflib/font/ft_pdffont.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
../obj/$(BUILDNICK)/cd_pdflib/ft_truetype.o : ./pdflib/font/ft_truetype.c ; gcc $(CF_ALL) $(CF_cd_pdflib) $^ -o $@
view all matches for this distribution
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
view all matches for this distribution