SHARE
TWEET

Untitled

a guest Jan 17th, 2017 114 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. bernardo@bernardo-ThinkCentre-Edge72:~$ cd yocto/
  2. bernardo@bernardo-ThinkCentre-Edge72:~/yocto$ source poky-krogoth/oe-init-build-env bbb-periphery
  3. You had no conf/local.conf file. This configuration file has therefore been
  4. created for you with some default values. You may wish to edit it to, for
  5. example, select a different MACHINE (target hardware). See conf/local.conf
  6. for more information as common configuration options are commented.
  7.  
  8. You had no conf/bblayers.conf file. This configuration file has therefore been
  9. created for you with some default values. To add additional metadata layers
  10. into your configuration please add entries to conf/bblayers.conf.
  11.  
  12. The Yocto Project has extensive documentation about OE including a reference
  13. manual which can be found at:
  14.     http://yoctoproject.org/documentation
  15.  
  16. For more information about OpenEmbedded see their website:
  17.     http://www.openembedded.org/
  18.  
  19.  
  20. ### Shell environment set up for builds. ###
  21.  
  22. You can now run 'bitbake <target>'
  23.  
  24. Common targets are:
  25.     core-image-minimal
  26.     core-image-sato
  27.     meta-toolchain
  28.     meta-ide-support
  29.  
  30. You can also run generated qemu images with a command like 'runqemu qemux86'
  31. bernardo@bernardo-ThinkCentre-Edge72:~/yocto/bbb-periphery$ devtool add c-periphery https://github.com/vsergeev/c-periphery.git
  32. NOTE: Creating workspace layer in /home/bernardo/yocto/bbb-periphery/workspace
  33. NOTE: Enabling workspace layer in bblayers.conf
  34. NOTE: Using default source tree path /home/bernardo/yocto/bbb-periphery/workspace/sources/c-periphery
  35. NOTE: Using source tree as build directory since that would be the default for this recipe
  36. NOTE: Recipe /home/bernardo/yocto/bbb-periphery/workspace/recipes/c-periphery/c-periphery_git.bb has been automatically created; further editing may be required to make it fully functional
  37. bernardo@bernardo-ThinkCentre-Edge72:~/yocto/bbb-periphery$ nano conf/local.conf
  38. bernardo@bernardo-ThinkCentre-Edge72:~/yocto/bbb-periphery$ cat conf/local.conf
  39. #
  40. # This file is your local configuration file and is where all local user settings
  41. # are placed. The comments in this file give some guide to the options a new user
  42. # to the system might want to change but pretty much any configuration option can
  43. # be set in this file. More adventurous users can look at local.conf.extended
  44. # which contains other examples of configuration which can be placed in this file
  45. # but new users likely won't need any of them initially.
  46. #
  47. # Lines starting with the '#' character are commented out and in some cases the
  48. # default values are provided as comments to show people example syntax. Enabling
  49. # the option is a question of removing the # character and making any change to the
  50. # variable as required.
  51.  
  52. #
  53. # Machine Selection
  54. #
  55. # You need to select a specific machine to target the build with. There are a selection
  56. # of emulated machines available which can boot and run in the QEMU emulator:
  57. #
  58. #MACHINE ?= "qemuarm"
  59. #MACHINE ?= "qemuarm64"
  60. #MACHINE ?= "qemumips"
  61. #MACHINE ?= "qemumips64"
  62. #MACHINE ?= "qemuppc"
  63. #MACHINE ?= "qemux86"
  64. #MACHINE ?= "qemux86-64"
  65. #
  66. # There are also the following hardware board target machines included for
  67. # demonstration purposes:
  68. #
  69. #MACHINE ?= "beaglebone"
  70. #MACHINE ?= "genericx86"
  71. #MACHINE ?= "genericx86-64"
  72. #MACHINE ?= "mpc8315e-rdb"
  73. #MACHINE ?= "edgerouter"
  74. #
  75. # This sets the default machine to be qemux86 if no other machine is selected:
  76. MACHINE ??= "qemux86"
  77.  
  78. #
  79. # Where to place downloads
  80. #
  81. # During a first build the system will download many different source code tarballs
  82. # from various upstream projects. This can take a while, particularly if your network
  83. # connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
  84. # can preserve this directory to speed up this part of subsequent builds. This directory
  85. # is safe to share between multiple builds on the same machine too.
  86. #
  87. # The default is a downloads directory under TOPDIR which is the build directory.
  88. #
  89. #DL_DIR ?= "${TOPDIR}/downloads"
  90.  
  91. #
  92. # Where to place shared-state files
  93. #
  94. # BitBake has the capability to accelerate builds based on previously built output.
  95. # This is done using "shared state" files which can be thought of as cache objects
  96. # and this option determines where those files are placed.
  97. #
  98. # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
  99. # from these files if no changes were made to the configuration. If changes were made
  100. # to the configuration, only shared state files where the state was still valid would
  101. # be used (done using checksums).
  102. #
  103. # The default is a sstate-cache directory under TOPDIR.
  104. #
  105. #SSTATE_DIR ?= "${TOPDIR}/sstate-cache"
  106.  
  107. #
  108. # Where to place the build output
  109. #
  110. # This option specifies where the bulk of the building work should be done and
  111. # where BitBake should place its temporary files and output. Keep in mind that
  112. # this includes the extraction and compilation of many applications and the toolchain
  113. # which can use Gigabytes of hard disk space.
  114. #
  115. # The default is a tmp directory under TOPDIR.
  116. #
  117. #TMPDIR = "${TOPDIR}/tmp"
  118.  
  119. #
  120. # Default policy config
  121. #
  122. # The distribution setting controls which policy settings are used as defaults.
  123. # The default value is fine for general Yocto project use, at least initially.
  124. # Ultimately when creating custom policy, people will likely end up subclassing
  125. # these defaults.
  126. #
  127. DISTRO ?= "poky"
  128. # As an example of a subclass there is a "bleeding" edge policy configuration
  129. # where many versions are set to the absolute latest code from the upstream
  130. # source control systems. This is just mentioned here as an example, its not
  131. # useful to most new users.
  132. # DISTRO ?= "poky-bleeding"
  133.  
  134. #
  135. # Package Management configuration
  136. #
  137. # This variable lists which packaging formats to enable. Multiple package backends
  138. # can be enabled at once and the first item listed in the variable will be used
  139. # to generate the root filesystems.
  140. # Options are:
  141. #  - 'package_deb' for debian style deb files
  142. #  - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
  143. #  - 'package_rpm' for rpm style packages
  144. # E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
  145. # We default to rpm:
  146. PACKAGE_CLASSES ?= "package_rpm"
  147.  
  148. #
  149. # SDK target architecture
  150. #
  151. # This variable specifies the architecture to build SDK items for and means
  152. # you can build the SDK packages for architectures other than the machine you are
  153. # running the build on (i.e. building i686 packages on an x86_64 host).
  154. # Supported values are i686 and x86_64
  155. #SDKMACHINE ?= "i686"
  156.  
  157. #
  158. # Extra image configuration defaults
  159. #
  160. # The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
  161. # images. Some of these options are added to certain image types automatically. The
  162. # variable can contain the following options:
  163. #  "dbg-pkgs"       - add -dbg packages for all installed packages
  164. #                     (adds symbol information for debugging/profiling)
  165. #  "dev-pkgs"       - add -dev packages for all installed packages
  166. #                     (useful if you want to develop against libs in the image)
  167. #  "ptest-pkgs"     - add -ptest packages for all ptest-enabled packages
  168. #                     (useful if you want to run the package test suites)
  169. #  "tools-sdk"      - add development tools (gcc, make, pkgconfig etc.)
  170. #  "tools-debug"    - add debugging tools (gdb, strace)
  171. #  "eclipse-debug"  - add Eclipse remote debugging support
  172. #  "tools-profile"  - add profiling tools (oprofile, lttng, valgrind)
  173. #  "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
  174. #  "debug-tweaks"   - make an image suitable for development
  175. #                     e.g. ssh root access has a blank password
  176. # There are other application targets that can be used here too, see
  177. # meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
  178. # We default to enabling the debugging tweaks.
  179. EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
  180.  
  181. #
  182. # Additional image features
  183. #
  184. # The following is a list of additional classes to use when building images which
  185. # enable extra features. Some available options which can be included in this variable
  186. # are:
  187. #   - 'buildstats' collect build statistics
  188. #   - 'image-mklibs' to reduce shared library files size for an image
  189. #   - 'image-prelink' in order to prelink the filesystem image
  190. #   - 'image-swab' to perform host system intrusion detection
  191. # NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
  192. # NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
  193. # image-prelink disabled for now due to issues with IFUNC symbol relocation
  194. USER_CLASSES ?= "buildstats image-mklibs"
  195.  
  196. #
  197. # Runtime testing of images
  198. #
  199. # The build system can test booting virtual machine images under qemu (an emulator)
  200. # after any root filesystems are created and run tests against those images. To
  201. # enable this uncomment this line. See classes/testimage(-auto).bbclass for
  202. # further details.
  203. #TEST_IMAGE = "1"
  204. #
  205. # Interactive shell configuration
  206. #
  207. # Under certain circumstances the system may need input from you and to do this it
  208. # can launch an interactive shell. It needs to do this since the build is
  209. # multithreaded and needs to be able to handle the case where more than one parallel
  210. # process may require the user's attention. The default is iterate over the available
  211. # terminal types to find one that works.
  212. #
  213. # Examples of the occasions this may happen are when resolving patches which cannot
  214. # be applied, to use the devshell or the kernel menuconfig
  215. #
  216. # Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
  217. # Note: currently, Konsole support only works for KDE 3.x due to the way
  218. # newer Konsole versions behave
  219. #OE_TERMINAL = "auto"
  220. # By default disable interactive patch resolution (tasks will just fail instead):
  221. PATCHRESOLVE = "noop"
  222.  
  223. #
  224. # Disk Space Monitoring during the build
  225. #
  226. # Monitor the disk space during the build. If there is less that 1GB of space or less
  227. # than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
  228. # shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
  229. # of the build. The reason for this is that running completely out of space can corrupt
  230. # files and damages the build in ways which may not be easily recoverable.
  231. # It's necesary to monitor /tmp, if there is no space left the build will fail
  232. # with very exotic errors.
  233. BB_DISKMON_DIRS = "\
  234.     STOPTASKS,${TMPDIR},1G,100K \
  235.     STOPTASKS,${DL_DIR},1G,100K \
  236.     STOPTASKS,${SSTATE_DIR},1G,100K \
  237.     STOPTASKS,/tmp,100M,100K \
  238.     ABORT,${TMPDIR},100M,1K \
  239.     ABORT,${DL_DIR},100M,1K \
  240.     ABORT,${SSTATE_DIR},100M,1K \
  241.     ABORT,/tmp,10M,1K"
  242.  
  243. #
  244. # Shared-state files from other locations
  245. #
  246. # As mentioned above, shared state files are prebuilt cache data objects which can
  247. # used to accelerate build time. This variable can be used to configure the system
  248. # to search other mirror locations for these objects before it builds the data itself.
  249. #
  250. # This can be a filesystem directory, or a remote url such as http or ftp. These
  251. # would contain the sstate-cache results from previous builds (possibly from other
  252. # machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
  253. # cache locations to check for the shared objects.
  254. # NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
  255. # at the end as shown in the examples below. This will be substituted with the
  256. # correct path within the directory structure.
  257. #SSTATE_MIRRORS ?= "\
  258. #file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
  259. #file://.* file:///some/local/dir/sstate/PATH"
  260.  
  261.  
  262. #
  263. # Qemu configuration
  264. #
  265. # By default qemu will build with a builtin VNC server where graphical output can be
  266. # seen. The two lines below enable the SDL backend too. By default libsdl-native will
  267. # be built, if you want to use your host's libSDL instead of the minimal libsdl built
  268. # by libsdl-native then uncomment the ASSUME_PROVIDED line below.
  269. PACKAGECONFIG_append_pn-qemu-native = " sdl"
  270. PACKAGECONFIG_append_pn-nativesdk-qemu = " sdl"
  271. #ASSUME_PROVIDED += "libsdl-native"
  272.  
  273. # CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
  274. # track the version of this file when it was generated. This can safely be ignored if
  275. # this doesn't mean anything to you.
  276. CONF_VERSION = "1"
  277. PACKAGE_CLASSES = "package_ipk"
  278. MACHINE = "beaglebone"
  279. PREFERRED_PROVIDER_virtual/kernel_beaglebone = "linux-ti-staging-rt"
  280. IMAGE_BOOT_FILES_beaglebone = "u-boot.img MLO"
  281. IMAGE_INSTALL_append_beaglebone = " kernel-modules kernel-devicetree"
  282. IMAGE_INSTALL_append_beaglebone = " connman"
  283. IMAGE_INSTALL_append_beaglebone = " connman-client"
  284. PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
  285. BB_NUMBER_THREADS ?= "6"
  286. PARALLEL_MAKE ?= "-j 8"
  287. bernardo@bernardo-ThinkCentre-Edge72:~/yocto/bbb-periphery$ nano conf/bblayers.conf
  288. bernardo@bernardo-ThinkCentre-Edge72:~/yocto/bbb-periphery$ cat conf/bblayers.conf
  289. # POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
  290. # changes incompatibly
  291. POKY_BBLAYERS_CONF_VERSION = "2"
  292.  
  293. BBPATH = "${TOPDIR}"
  294. BBFILES ?= ""
  295.  
  296. BBLAYERS ?= " \
  297.   /home/bernardo/yocto/poky-krogoth/meta \
  298.   /home/bernardo/yocto/poky-krogoth/meta-poky \
  299.   /home/bernardo/yocto/poky-krogoth/meta-ti \
  300.   /home/bernardo/yocto/bbb-periphery/workspace \
  301.   "
  302. bernardo@bernardo-ThinkCentre-Edge72:~/yocto/bbb-periphery$$ devtool build c-periphery
  303. Loading cache: 100% |###########################################################################################################################################| ETA:  00:00:00
  304. Loaded 1470 entries from dependency cache.
  305. Parsing recipes: 100% |#########################################################################################################################################| Time: 00:00:01
  306. Parsing of 1033 .bb files complete (1031 cached, 2 parsed). 1471 targets, 153 skipped, 0 masked, 0 errors.
  307. NOTE: Resolving any missing task queue dependencies
  308.  
  309. Build Configuration:
  310. BB_VERSION        = "1.30.0"
  311. BUILD_SYS         = "x86_64-linux"
  312. NATIVELSBSTRING   = "universal"
  313. TARGET_SYS        = "arm-poky-linux-gnueabi"
  314. MACHINE           = "beaglebone"
  315. DISTRO            = "poky"
  316. DISTRO_VERSION    = "2.1.2"
  317. TUNE_FEATURES     = "arm armv7a vfp thumb neon       callconvention-hard"
  318. TARGET_FPU        = "hard"
  319. meta              
  320. meta-poky         = "krogoth:ae9b341ecfcc60e970f29cfe04306411ad26c0cf"
  321. meta-ti           = "krogoth:f0a7e52d65861a432ff94f2465e67e014cc7eca0"
  322. workspace         = "<unknown>:<unknown>"
  323.  
  324. NOTE: Preparing RunQueue
  325. NOTE: Executing SetScene Tasks
  326. NOTE: Executing RunQueue Tasks
  327. c-periphery-1.0+git999-r0 do_compile: NOTE: c-periphery: compiling from external source tree /home/bernardo/c-periphery
  328. NOTE: Tasks Summary: Attempted 333 tasks of which 327 didn't need to be rerun and all succeeded.
  329. bernardo@bernardo-ThinkCentre-Edge72:~/yocto/bbb-periphery$ devtool deploy-target c-periphery root@10.0.16.35
  330. Parsing recipes..done.
  331. ERROR: No files to deploy - have you built the c-periphery recipe? If so, the install step has not installed any files.
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top