. . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 13 Howtos 183 13.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 13.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Static or shared library are not settings that apply to all packages. Some can be header only libraries while others packages can be just data, or package executables. Packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 13 Howtos 181 13.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 13.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Static or shared library are not settings that apply to all packages. Some can be header only libraries while others packages can be just data, or package executables. Packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 170 12 Howtos 171 12.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 12.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Being a static or shared library is not something that applies to all packages. Some can be header only libraries. Other packages can be just data, or package executables. Or packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 12 Howtos 173 12.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 12.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Static or shared library are not settings that apply to all packages. Some can be header only libraries while others packages can be just data, or package executables. Packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 157 12 Howtos 163 12.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 12.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Being a static or shared library is not something that applies to all packages. Some can be header only libraries. Other packages can be just data, or package executables. Or packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 13 Howtos 185 13.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 13.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Static or shared library are not settings that apply to all packages. Some can be header only libraries while others packages can be just data, or package executables. Packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 13 Howtos 193 13.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 13.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Static or shared library are not settings that apply to all packages. Some can be header only libraries while others packages can be just data, or package executables. Packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 13 Howtos 175 13.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 13.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Being a static or shared library is not something that applies to all packages. Some can be header only libraries. Other packages can be just data, or package executables. Or packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 13 Howtos 213 13.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 13.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Static or shared library are not settings that apply to all packages. Some can be header only libraries while others packages can be just data, or package executables. Packages can contain

. . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 13 Howtos 203 13.1 How to package header-only libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203 13.2 How generated. By the way, “binary package” is in quotes because, strictly, it is not necessarily a binary. A header-only library, for example, will contain just the headers in the “binary package”. All the binary configuration. Static or shared library are not settings that apply to all packages. Some can be header only libraries while others packages can be just data, or package executables. Packages can contain