compiling CM for 2 devices

Discussion in 'Cyanogenmod' started by JBirdVegas, Feb 22, 2011.

  1. JBirdVegas
    Offline

    JBirdVegas Developer Developer

    Joined:
    Aug 8, 2010
    Messages:
    107
    Likes Received:
    0
    Trophy Points:
    0
    My question is I'm trying to compile CM for my devices (sholes & harmony) do I need to have different build enviroment for each device?

    Their wiki:
    Building from source - CyanogenMod Wiki

    made building for droid og (sholes) super easy but then when I tried to build for harmony breakfast, brunch & lunch continually quit complaining:
    *** Don't have a product spec for: 'cyanogen_harmony

    yes I pulled the propitiatory files from my G tablet

    also would building from android.git.kernel.org break the lunch?

    <SOLVED> make cleaninstall
    Last edited: Feb 26, 2011
  2. joshk6656
    Offline

    joshk6656 New Member

    Joined:
    May 12, 2010
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    0
    my understanding is you do not need a seperate environment for each device since the prop files are stored in device specific directories.

    your doing:

    . build/envsetup.sh && brunch sholes
    and
    . build/envsetup.sh && brunch harmony

    ?
  3. JBirdVegas
    Offline

    JBirdVegas Developer Developer

    Joined:
    Aug 8, 2010
    Messages:
    107
    Likes Received:
    0
    Trophy Points:
    0
    yea ... err I also
    #from cm's github
    . build/envsetup.sh && brunch sholes
    #from aosp
    . build/envsetup.sh && brunch sholes
    #from cm's git hub
    . build/envsetup.sh && brunch harmony

    I was thinking both prob use the same lunch so when I did #from aosp I damaged lunch in someway???
  4. joshk6656
    Offline

    joshk6656 New Member

    Joined:
    May 12, 2010
    Messages:
    28
    Likes Received:
    0
    Trophy Points:
    0
  5. JBirdVegas
    Offline

    JBirdVegas Developer Developer

    Joined:
    Aug 8, 2010
    Messages:
    107
    Likes Received:
    0
    Trophy Points:
    0
    I found the answer in google's building documentation using

    make cleaninstall

    Prevents any previous build configs from being grandfathered into you new build

    Ill add <SOLVED> to the title when I get home. Thanks y'all


    Sent from my Droid using Tapatalk
Search tags for this page

** don't have a product spec for: cm n7000

,

android breakfast brunch

,
android brunch build
,

android build brunch

,
android don't have a product spec for
,
cm brunch vs lunch
,
cm-10.2 don't have a product spec for: cm n7100
,
don't have a product spec for: cm d2vzw
,
don't have a product spec for: cm endeavoru
,
don't have a product spec for: cm yuga