Searched refs:location (Results 1 – 12 of 12) sorted by relevance
79 uint32_t location : 1; ///< indicate location information member87 uint32_t location : 1; ///< indicate location information110 struct location { struct116 location() : tag(0), address(0), file(0), line(0) {} in location() argument193 const location& getLocation() const { return m_loc; } in getLocation()217 location m_loc;
37 SYST_BUILD_GTEST_DIR | File system location of the Google Test framework source code. This cod…40 CMAKE_INSTALL_PREFIX | File System location for installing the SyS-T build.51 - Point the "Where to build the binaries:" field to a temporary location. This53 installation location for the build result.59 desired install location.103 install | Install to CMAKE_INSTALL_PREFIX location, implies 'all'115 run execute the script. The BLD_ROOT variable sets the location of the build
77 generating additional location information. Location information describes84 API without location information generation100 location. This API requires the SyS-T platform feature defines115 - An optional location record153 A message can contain location information describing the position of its155 "file:line" ID pair. This location information is generated if one of the
75 - An optional [location record] (#syst_decoder_prot_location)132 mipi_syst_u32 et_location:1; /**< indicate location information */185 A SyS-T Message can contain location information describing the position of187 "file:line" ID pair. This location information is generated if one of the195 * Specify format of used message location information that is added to the246 The location information is followed by a 16-bit length field if the header bit
52 # If a relative path is entered, it will be relative to the location1068 # be used to specify the location (absolute path including file name) of1144 # be used to specify the location of Qt's qhelpgenerator.1237 # When MathJax is enabled you need to specify the location relative to the1308 # of to a relative location where the documentation can be found.1637 # tag file the location of the external documentation should be added. The1638 # format of a tag file without this location is as follows:1640 # Adding location for the tag files is done as follows:1716 # the font, which can be done by putting it in a standard location or by setting
209 explicit location information.
99 …Path prefix for the compiled library binaries and include files install location| (defined by CMak…102 | SYST_BUILD_GTEST_DIR|Installation location of Google Test sources. Set this for building the unit…105 library on a Linux console. Replace "../sys-t/library" with the location of125 and SyS-T header files to the deploy location. This location was defined143 files in the install location. The location of the install folder needs148 in a Linux console. Replace "../sys-t/examples" with the location of150 with the location of the install location from a previously built367 run execute the script. The BLD_ROOT variable sets the location of the build
24 #dynamic linking, requires location of mipi_syst.dll to be in the PATH.
547 * Enable the API variants that send file:line ID pair location records.552 * Enable the API variants that send the address of the instrumentation location.653 mipi_syst_u32 et_location : 1; /**< indicate location information */661 mipi_syst_u32 et_location : 1; /**< indicate location information */764 struct mipi_syst_msglocation systh_location; /**< location record */
264 const message::location& loc, in location2string()
267 if (dest.getHeader().field.location) { in decodeNormalMessage()
36 …TEST_DIR=${SYST_BUILD_GTEST_DIR} does not point to a Google Test source location. Unittests will n…
