1. 26 Dec, 2014 1 commit
  2. 20 Dec, 2014 1 commit
  3. 19 Dec, 2014 2 commits
  4. 18 Dec, 2014 9 commits
  5. 17 Dec, 2014 8 commits
    • Patrick Lankswert's avatar
      Merge "Fixed build error" · b3a2c51b
      Patrick Lankswert authored
    • sudarshan prasad's avatar
    • Sudarshan Prasad's avatar
      Fixed build error · c81cf676
      Sudarshan Prasad authored
      Due to a previous merge, build was failing when scons was used.
      Signed-off-by: default avatarSudarshan Prasad <sudarshan.prasad@intel.com>
      Change-Id: I26ad37273f91e61bd4afb49c9c4010cde32cb3b9
    • Patrick Lankswert's avatar
    • Uze Choi's avatar
    • Uze Choi's avatar
    • Kishen Maloor's avatar
      OIC scons build patch for Yocto · 585ea764
      Kishen Maloor authored
      Adds Yocto as a build target for OIC. Code is
      executed ONLY when TARGET_OS=yocto.
      It WILL NOT affect a build for any other target.
      Yocto cross-toolchains for platforms would have
      to be fetched, installed and configured in their
      standard way. This configuration is done by
      sourcing in an “environment setup” script that
      comes with the toolchain. scons is run after this
      The code in this patch reads the variables set
      by Yocto’s script and: 1) Learns of tool names and
      build flags (varies by target and arch.), 2) Finds
      absolute path of these tools (yocto’s script adds
      these to PATH) by looking in PATH, 3) Modifies the
      scons construction environment to point to tools
      + all their required flags, 4) Switches TARGET_OS
      to Linux so that it uses the Linux build configuration
      for OIC, 5) Elects to preserve debug symbols (using -g)
      so that Yocto’s build process can generate both
      DEBUG and RELEASE packages for OIC (This is the
      default recommendation of Yocto’s BitBake)
      Additional notes:
      -The pre-existing TC_PREFIX/TC_PATH framework is
      not sufficient to support Yocto’s cross-toolchain.
      -Supported architectures for the yocto target are x86
      and x86_64. These have been tested to work for Intel
      Edison and Minnowboard platforms.
      From a user’s perspective, there are no unexpected
      1) source <yocto-env-setup-script>
      2) …/oic-resource$ scons TARGET_OS=yocto <regular options>
      For eg. “scons TARGET_OS=yocto TARGET_ARCH=x86 RELEASE=1”
      The results of a build will now go into “out/yocto/x86/…”.
      If step 1) hasn’t been done before step 2), the build will
      fail with an error message.
      Change-Id: I55efab20f9c174f46446e9d59e3fca6eef3df7f2
      Signed-off-by: Kishen Maloor's avatarKishen Maloor <kishen.maloor@intel.com>
    • sudarshan prasad's avatar
  6. 16 Dec, 2014 6 commits
  7. 15 Dec, 2014 8 commits
  8. 13 Dec, 2014 1 commit
  9. 12 Dec, 2014 4 commits