賴軟體包）。然而，你還是應該用 aptitude show package 或者 dpkg -s package 來檢查一下。（譯註：apt show PACKAGE 亦可） 在你的開發環境中，需要安裝的最重要的軟件包是 build-essential。一旦你嘗試安裝該包，它將 拉來其他基本構 建環境所需的基本軟件。 對於某些類型的軟件，以上的就是所需要的全部。然而還有一組軟件包雖不是對於所有軟件包都必須，卻可能對你有 用或被你的軟件包所需要： pbuilder - 此軟體包提供了建立和維護 chroot 環境的工具。在它的 chroot 環境中編譯 Debian 軟體包可以檢查編譯 依賴是否合適，並避免 FTBFS (Fails To Build From Source，原始碼編譯失敗) 的 Bug。(參看 pbuilder(8) 和 pdebuild(1)) • perl - Perl 是現今類 Unix 系統中使用最普遍的解釋型腳本語言，它常被稱作 重要的文檔，你應該在讀本文檔時同時參看它們： • Autotools Tutorial (http://www.lrde.epita.fr/~adl/autotools.html) 為 the GNU Build System known as the GNU Autotools 中 最重要的工具——Autoconf、Automake、Libtool 和 gettext 提供了很好的文件。 • gnu-standards

開發必需之工具 ▶ 一台能以 root 權限存取的 Debian (or Ubuntu) 系統 ▶ 一些必需套件: ▶ build-essential: 和 Debian 套件有相依性並假定已安裝在開發者的機 器上 (不需在套件中的 control 欄位特別指定 Build-Depends: ) ▶ 相依 dpkg-dev 套件, 其中包含基本 Debian 特定工具, 以便於製 作 Debian 上傳(dput) Debian 套件打包教學指南 9 / 90 範例: 重包 dash 套件 1 安裝重包 dash 套件所需的必要套件以及 devscripts 套件 sudo apt-get build-dep dash (需要將deb-src 設定到 /etc/apt/sources.list) sudo apt-get install --no-install-recommends devscripts Kothe Homepage: http :// www.gnu.org/software/wget/ Standards -Version: 3.8.4 Build -Depends: debhelper (>> 5.0.0) , gettext , texinfo , libssl -dev (>= 0.9.8) , dpatch , info2man Checksums

Command-line option changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.5 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.6 New library followed by pre-release and build alpha- numeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Command-line option changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.5 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1676 104.6 New library followed by pre-release and build alpha- numeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2041 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2042 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

歡迎瞭解 Chromium 中的 Rust 221 40 設定 222 41 比較 Chromium 和 Cargo 的生態系統 224 42 Chromium Rust 政策 226 43 Build rules 227 43.1 包含 unsafe Rust 程式碼 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 43 43.3 Visual Studio Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 43.4 Build rules exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228 44 測試 230 44.1 rust_gtest_interop 結語 351 67 謝謝！ 352 68 詞彙解釋 353 69 其他 Rust 資源 355 70 出處清單 357 9 歡迎參加 Comprehensive Rust 課 程 build passing contributors 303 stars 28k 這個免費的 Rust 課程是由 Google 的 Android 團隊負責開發。本課程涵蓋 Rust 的全部內容，從基礎語

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1987 108.7 New library followed by pre-release and build al- phanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor version 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful

Multi-threading changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.6 Build system changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039 109.7 New library followed by pre-release and build alphanumeric annotations. For example, v"0.2.1-rc1+win64" is broken into major version 0, minor ver- sion 2, patch version 1, pre-release rc1 and build win64. When entering version number is optional, therefore e.g. v"0.2" is equivalent to v"0.2.0" (with empty pre- release/build annotations), v"2" is equivalent to v"2.0.0", and so on. VersionNumber objects are mostly useful