Source string Read only

(itstool) path: sect1/para
205/2050
Context English State
<literal>cargo</literal>
Possible arguments: (none)
Uses Cargo for configuring, building, and testing. It can be used to port Rust applications that use the Cargo build system. For more information see <xref linkend="using-cargo"/>.
<literal>charsetfix</literal>
Prevents the port from installing <filename>charset.alias</filename>. This must be installed only by <package role="port">converters/libiconv</package>. <varname>CHARSETFIX_MAKEFILEIN</varname> can be set to a path relative to <varname>WRKSRC</varname> if <filename>charset.alias</filename> is not installed by <filename>${WRKSRC}/Makefile.in</filename>.
<literal>cmake</literal>
Possible arguments: (none), <literal>insource</literal>, <literal>noninja</literal>, <literal>run</literal>
Uses <application>CMake</application> for configuring and building.
By default an out-of-source build is performed, leaving the sources in <varname>WRKSRC</varname> free from build artifacts. With the <literal>insource</literal> argument, an in-source build will be performed instead. Setting it should be the exception when a regular out-of-source build does not work.
By default <application>Ninja</application> is used for the build. In some cases this does not work correctly. With the <literal>noninja</literal> argument, the build will fallback to using regular <command>make</command> for builds. It should only be used if a <application>Ninja</application>-based build does not work.
With the <literal>run</literal> argument, a run dependency is registered in addition to a build dependency.
For more information see <xref linkend="using-cmake"/>.
<literal>compiler</literal>
Possible arguments: (none), <literal>env</literal> (default, implicit), <literal>c++17-lang</literal>, <literal>c++14-lang</literal>, <literal>c++11-lang</literal>, <literal>gcc-c++11-lib</literal>, <literal>c++11-lib</literal>, <literal>c++0x</literal>, <literal>c11</literal>, <literal>openmp</literal>, <literal>nestedfct</literal>, <literal>features</literal>
Determines which compiler to use based on any given wishes. Use <literal>c++17-lang</literal> if the port needs a C++17-capable compiler, <literal>c++14-lang</literal> if the port needs a C++14-capable compiler, <literal>c++11-lang</literal> if the port needs a C++11-capable compiler, <literal>gcc-c++11-lib</literal> if the port needs the <command>g++</command> compiler with a C++11 library, or <literal>c++11-lib</literal> if the port needs a C++11-ready standard library. If the port needs a compiler understanding C++0X, C11, OpenMP, or nested functions, the corresponding parameters should be used.
Use <literal>features</literal> to request a list of features supported by the default compiler. After including <filename>bsd.port.pre.mk</filename> the port can inspect the results using these variables:
<varname>COMPILER_TYPE</varname>: the default compiler on the system, either gcc or clang
<varname>ALT_COMPILER_TYPE</varname>: the alternative compiler on the system, either gcc or clang. Only set if two compilers are present in the base system.
<varname>COMPILER_VERSION</varname>: the first two digits of the version of the default compiler.
<varname>ALT_COMPILER_VERSION</varname>: the first two digits of the version of the alternative compiler, if present.
<varname>CHOSEN_COMPILER_TYPE</varname>: the chosen compiler, either gcc or clang
<varname>COMPILER_FEATURES</varname>: the features supported by the default compiler. It currently lists the C++ library.
<literal>cpe</literal>
Include Common Platform Enumeration (<acronym>CPE</acronym>) information in package manifest as a <acronym>CPE</acronym> 2.3 formatted string. See the <link xlink:href="http://scap.nist.gov/specifications/cpe/"><acronym>CPE</acronym> specification</link> for details. To add <acronym>CPE</acronym> information to a port, follow these steps:
Search for the official CPE entry for the software product either by using the NVD's <link xlink:href="http://web.nvd.nist.gov/view/cpe/search"><acronym>CPE</acronym> search engine</link> or in the <link xlink:href="http://static.nvd.nist.gov/feeds/xml/cpe/dictionary/official-cpe-dictionary_v2.3.xml">official <acronym>CPE</acronym> dictionary</link> (warning, very large <acronym>XML</acronym> file). <emphasis>Do not ever make up <acronym>CPE</acronym> data.</emphasis>
Add <literal>cpe</literal> to <varname>USES</varname> and compare the result of <command>make -V CPE_STR</command> to the <acronym>CPE</acronym> dictionary entry. Continue one step at a time until <command>make -V CPE_STR</command> is correct.
If the product name (second field, defaults to <varname>PORTNAME</varname>) is incorrect, define <varname>CPE_PRODUCT</varname>.
If the vendor name (first field, defaults to <varname>CPE_PRODUCT</varname>) is incorrect, define <varname>CPE_VENDOR</varname>.
If the version field (third field, defaults to <varname>PORTVERSION</varname>) is incorrect, define <varname>CPE_VERSION</varname>.
If the update field (fourth field, defaults to empty) is incorrect, define <varname>CPE_UPDATE</varname>.
If it is still not correct, check <filename>Mk/Uses/cpe.mk</filename> for additional details, or contact the Ports Security Team <email>ports-secteam@FreeBSD.org</email>.

Loading…

No matching activity found.

Browse all component changes

Glossary

English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect1/para
Flags
read-only
Source string location
book.translate.xml:22468
String age
a year ago
Source string age
a year ago
Translation file
books/porters-handbook.pot, string 4576