1. 29 Sep, 2017 1 commit
  2. 08 Feb, 2016 1 commit
  3. 12 Jan, 2016 1 commit
  4. 06 Jan, 2016 1 commit
  5. 27 Mar, 2015 4 commits
    • Stephen Boyd's avatar
      make-arm: Export CROSS_COMPILE into compilation environment · 386c283f
      Stephen Boyd authored
      We need to export CROSS_COMPILE into the environment for the make
      subprocesses to pick it up when the config.sh file is used.
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      386c283f
    • Stephen Boyd's avatar
      skales: Make kobj and bootimage directory configurable · 47f1709e
      Stephen Boyd authored
      Some users of skales don't want to rely on the kernel, kobj
      directory structure. Instead they want to build the object files
      within the same directory as the kernel sources. Support this
      configuration with a KOBJ variable that can be set in the config.
      If KOBJ isn't set we fall-back to the original configuration
      where kobj lives next to the kernel sources. We also expose a
      BOOTIMG_DIR config so that users can configure where their boot
      images are generated. If it isn't set we fall-back to the
      original configuration where the bootimages live directly above
      the kernel sources.
      
      To make things nicer on these users we also cleanup the
      intermediate objects during the package invocation so that their
      git status comes out clean.
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      47f1709e
    • Stephen Boyd's avatar
      skales: Allow per-kernel configuration files · 325a7030
      Stephen Boyd authored
      Look for a .skales/config file in the root of the kernel
      directory to use as the per-kernel configuration. This will
      override whatever is specified in the global config in the skales
      root directory.
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      325a7030
    • David Brown's avatar
      skales: Simplify the workflow for common usage · cedca0ea
      David Brown authored
      The default workflow in Skales is fairly complex and uses features of
      git not everyone will be familiar or comfortable with.
      
      Instead, simplify the instructions a bit, and implement a config file
      that can be used to control some of the behavior of skales if desired:
      
        - The cross compiler can be set here instead of in the environment.
      
        - The user can specify a defconfig which will automatically be
          copied in and out of the tree as part of the build. This more
          closely resembles the behavior that android developers are used
          to.
      
      [sboyd: Use config.sh.example to avoid dirty trees. Use test
      	instead of brackets. Don't assume defconfigs end in
      	"_defconfig". Default to msm_defconfig for upstream]
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      cedca0ea
  6. 05 Jun, 2013 1 commit
  7. 06 Dec, 2012 2 commits
    • Stephen Boyd's avatar
      Don't force a CROSS_COMPILE · 5bb44767
      Stephen Boyd authored
      Lets the environment specify one if necessary. In the future we
      can add a 'choose compiler' script that lets you pick between a
      handful of arm compilers.
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      5bb44767
    • Stephen Boyd's avatar
      skales: meta build scripts · ad46fb9c
      Stephen Boyd authored
      Instead of using Makefiles and such, introduce a 'skales' branch as
      a meta branch in the kernel repo. Usage should be simple enough
      
      1) Source the source-me script to setup the PATH
      
      2) init-branch <branch name> to get a branch under b/
      
      3) cd b/<branch name>/kernel and hack away
      
      4) compile with make-arm <insert build options>
      
      5) package a boot.img with package-<arch>
      Signed-off-by: 's avatarStephen Boyd <sboyd@codeaurora.org>
      ad46fb9c