Lines Matching refs:C
82 syntax must be used, which means that the slash C</> must be used as
89 Comments are any line that start with a hash sign (C<#>). The hash
102 For example, if we say that we want to produce a program C<foo>, it
107 However, the program filename may end up being just C<foo> (typical
108 for Unix), or C<foo.exe> (typical for Windows), or even C<BLAH$FOO.EXE>
140 This says that we want to build programs C<foo> and C<bar>, the
141 libraries C<libpoly> and C<libcookie>, an awesome plugin module
142 C<awesome-plugin>, a couple of scripts C<tool1> and C<tool2>, and
144 C<dir1> and C<dir2>.
152 This says that the program C<foo> is built from the source files
154 C<libcookie> (in other words, the library will be included when
191 This says that the static library C<libtestutil.a> should not be
192 installed (C<noinst>), and that it includes an object file that has
193 the C<main> symbol (C<has_main>). Most platforms don't need to know
195 for C<main> in libraries unless it's explicitly told so, so this is
211 The end result is that the library C<libwhatever> will have the
212 attributes C<noinst> and C<has_main> attached to it.
220 quoted with double (C<">) or single (C<'>) quotes.
226 This says that we sant to build three programs, C<foo>, C<space cadet>
227 and C<bar>.
302 Perl nuggets are anything between C<{-> and C<-}>, and whatever the
332 If the condition is true (represented as C<1> here), everything
337 If the condition is false (represented as C<0> here), everything
377 With those two lines, the program C<foo> will not have the attribute
378 C<noinst>, while the program C<bar> will.
385 form. However, if a name ends with C<.a>, only the static form will
389 plain name, or the name including the ending C<.a>. If given without
390 the ending C<.a>, any form available will be used, but if given with
391 the ending C<.a>, the static library form is used unconditionally.
399 With those two lines, the library C<libfoo> will not have the
400 attribute C<noinst>, while the library C<libbar> will.
412 With those two lines, the module C<foo> will not have the attribute
413 C<noinst>, while the module C<bar> will.
427 With those two lines, the script C<foo> will not have the attribute
428 C<noinst>, while the script C<bar> will.
449 "pipe" character), C<|>. For example:
459 With those statements, the dependency between C<libfoo.a> and
460 C<libmandatory.a> is strong, while the dependency between C<libfoo.a>
461 and C<libbar.a> and C<libcookie.a> is weak. See the description of
477 Currently, they at least recognise files ending in C<.pl>, and will
478 execute them to generate the I<item>, and files ending in C<.in>,
501 With those statements, the association between C<prog> and C<prog_a.c>
502 comes with no extra attributes, while the association between C<prog>
503 and C<prog_b.c> as well as C<prog_c.c> comes with the extra attribute
504 C<check>.
513 ending with C<.a>, the filenames will be ignored.
524 example, these pairs should become C macro definitions whenever a
525 C<.c> file is built into an object file.
566 like this, means that if C<libfoo.a> appears in a linking command
567 line, so will C<libmandatory.a>:
572 like this, means that if I<both> C<libfoo.a> and C<libmandatory.a>
580 used as alternatives for each other. In this example, C<lib1.a> and
581 C<lib2.a> have alternative implementations of the same thing, and
582 C<libmandatory.a> has unresolved references to that same thing, and is
631 C<perldoc -o man util/perl/OpenSSL/Template.pm>
