Lines Matching refs:Build
132 provide all of the tools required to build such functionality. LibTomCrypt was designed to be a flexible library that
154 configurable in terms of its build options. Out of the box the library will build with any modern version of GCC
158 On top of making the build simple and the API approachable I've also attempted for a reasonably high level of
194 They can be removed from a build by simply commenting out the two appropriate lines in \textit{tomcrypt\_custom.h}. The rest
657 Note that \textit{Twofish} has additional configuration options (Figure \ref{fig:twofishopts}) that take place at build time. These options are found in
667 \index{Twofish build options} \index{TWOFISH\_SMALL} \index{TWOFISH\_TABLES}
680 \caption{Twofish Build Options}
2871 to work with most cipher and hash combos based on which you have chosen to build into the library.} while
3630 supported by any conforming math plugin. It is enabled by defining \textbf{MECC\_FP} during the build, such as
3636 which will build LTC using the TFM math library and enabling this new feature. The feature is not enabled by default as it is \textbf{NOT} thread
4194 and reflects if the particular member of a list was the decoded data type. To help build the lists in an orderly fashion the macro
4548 that the build platform honours the run--time platforms character conventions.
4572 that the build platform honours the run-time platforms character conventions.
5032 the build process to make a smaller library. This is particularly useful for shared libraries.
5034 As of v1.06 of the library, the build
5037 The build process now consists of installing a math library first, and then building and installing LibTomCrypt with a math library
5039 build, or run time for the application. LibTomCrypt comes with three math descriptors that provide a standard interface to math
5044 All GNU driven makefiles (including the makefile for ICC) use a set of common variables to control the build and install process. Most of the
5056 \begin{flushleft} will build and install the libraries with the \textit{gmake} tool. Similarly, \end{flushleft}
5062 \begin{flushleft} will build the library using \textit{arm--gcc} as the compiler and \textit{arm--ar} as the archiver. \end{flushleft}
5097 This will build the library and install it to the directories under \textit{/home/tom/project/}. e.g.
5158 That will build LibTomCrypt (including the TomsFastMath descriptor), and install it in the default locations indicated previously. You can enable
5159 the built--in LibTomMath descriptor as well (or in place of the TomsFastMath descriptor). Similarly, you can build the library with no built--in
5166 In this case, no math descriptors are present in the library and they will have to be made available at build or run time before you can use any of the
5188 This will build and install the library and link the shared object against the TomsFastMath library (which must be installed as a shared object as well). The
5189 shared build process requires libtool to be installed.
5192 The file \textit{tomcrypt\_cfg.h} is what lets you control various high level macros which control the behaviour of the library. Build options are also
5230 During the build if LTC\_NO\_FILE is defined then any function in the library that uses file I/O will not call the file I/O
5239 When this has been defined the various self--test functions (for ciphers, hashes, prngs, etc) are included in the build. This is the default configuration.
5285 When defined the library is configured to build fewer algorithms and modes. Mostly it sticks to NIST and ANSI approved algorithms. See
5287 build to the most minimum of useful functionality.
5318 Generally the rule of thumb is to setup the tables once at startup and then leave them be. This added build flag simply makes updating
5342 That will build and install the library with all descriptors (and link against all), but only use TomsFastMath in the timing demo.
5348 to be highly portable and easy to build out of the box on pretty much any platform. As such there are no assembler inlines throughout the code, I make no assumptions
