Building cupcake for dream

[Jean-Baptiste Queru]

I've made some progress to build cupcake for dream.

Steps (I hope I have them right):
sync cupcake (with no local_manifest.xml - all the necessary projects
are now included in the default manifest)
in vendor/htc/dream-open, run ./extract-files.sh
. build/envsetup.sh
lunch htc_dream-eng
make

At the moment, this is only valid for cupcake, I'll replicate the
setup across to donut and master and I'll update the instructions on
the web site as soon as I get a chance.

JBQ

--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

[Jean-Baptiste Queru]

The change has been propagated to donut and master, and the
instructions have been updated. Let me know if something doesn't work
right.

JBQ

[Johan de Koning]

What do you mean with sync cupcake? From this thread
http://groups.google.com/group/android-platform/browse_thread/thread/4853d33c28abb5f5
I though that the cupcake-release is the branch for the devices. So
what I did when initializing the branch is

repo init -u git://android.git.kernel.org/platform/manifest.git - b
cupcake-release

But this release does get the vendor/htc/dream-open project. So which
branch to use? Should I use cupcake instead? When it is cupcake it is
not the same as told in the other discussion. Hope you can clear this
up.

Thanks for all your help

[dan raaka]

Dont you need to add

 

adb pull /system/lib/libaudio.so proprietary/libaudio.so
adb pull /system/lib/libcamera.so proprietary/libcamera.so
adb pull /system/lib/librpc.so proprietary/librpc.so

 

to extract-files.sh

-Dan

[Jean-Baptiste Queru]

With the current setup, short of doing some manual setup, you'll need
to use the "true" cupcake. The differences between cupcake and
cupcake-release won't make any significant difference here.

If you want to do a manual setup, look at the history in
platform/manifest, grab the change I did recently in cupcake, apply it
manually locally on your cupcake-release manifest (and add
revision="cupcake" to both lines that you're adding).

JBQ

On Thu, Jul 23, 2009 at 1:50 PM, Johan de Koning<ikben...@gmail.com> wrote:
>

[Johan de Koning]

I did the repo init and sync again this time with the cupcake branch

repo init -u git://android.git.kernel.org/platform/manifest.git - b
cupcake

This version also contains the vendor/htc/dream-open.

So does this mean that cupcake is for the device? And cupcake-release
for....?

On 23 jul, 22:50, Johan de Koning <ikbennu...@gmail.com> wrote:
> What do you mean with sync cupcake? From this threadhttp://groups.google.com/group/android-platform/browse_thread/thread/...

[Johan de Koning]

BTW kernel.version contains outdated information inside the dream-open
project.

[Johan de Koning]

You are right. Not all the proprietary files are inside the extract-
files.sh script. That means that the AndroidBoard.mk is also not
complete.

I submitted a patch for this some time ago: https://review.source.android.com/Gerrit#change,10501
But this patch also downloads the wlan.ko from the device which is not
needed because it is already part of the dream-open project and can
also be compiled from source.

On 23 jul, 23:02, dan raaka <danra...@gmail.com> wrote:
> Dont you need to add
>
> adb pull /system/lib/libaudio.so proprietary/libaudio.so
> adb pull /system/lib/libcamera.so proprietary/libcamera.so
> adb pull /system/lib/librpc.so proprietary/librpc.so
>
> to extract-files.sh
>
> -Dan
>

> On Thu, Jul 23, 2009 at 1:50 PM, Johan de Koning <ikbennu...@gmail.com>wrote:
>
>
>
>
>
> > What do you mean with sync cupcake? From this thread
>

> >http://groups.google.com/group/android-platform/browse_thread/thread/...

[Jean-Baptiste Queru]

Cupcake is the "mainline" cupcake codeline, cupcake-release is closer
to what shipped on consumer devices (their current states are close to
SDK-1.5r3 and CRC01, respectively). The difference between them isn't
large.

We recommend that OEMs shipping consumer devices do so from the
cupcake-release branch, but for development purposes you can use
either, and if you want to play with the code on dream right now the
only codelines that are configured out of the box to do so are
cupcake, donut and master. Most probably, future ancillary codelines
will also have that, but for now that's the current setup.

JBQ

[Jean-Baptiste Queru]

The current setup is hard to maintain, because it doesn't match at all
the tree structure that we use inside Google to build for those
devices.

Bringing those in better sync is on my todo list, but that was not the
point of my manifest shuffling, and it's not going to happen right
away.

JBQ

[Johan de Koning]

Is the SdkSetup package not needed anymore (and is it still inside the
git source tree)?

[dan raaka]

SdkSetup in the first boot set things up like .. home key confugurations .. which allowed long homekey press .. not sure if it is still needed

-Dan

[Johan de Koning]

The SdkSetup also makes it possible to accept/make calls (don't know
exactly if it was making calls or receiving calls). Some provisioning
flash will be set.

There is new OTAProvisioningClient project which could do probally the
same (looking at the description) but there are no commits inside this
project

On 23 jul, 23:31, dan raaka <danra...@gmail.com> wrote:
> SdkSetup in the first boot set things up like .. home key confugurations ..
> which allowed long homekey press .. not sure if it is still needed
>
> -Dan
>

> On Thu, Jul 23, 2009 at 2:29 PM, Johan de Koning <ikbennu...@gmail.com>wrote:
>
>
>
>
>
> > Is the SdkSetup package not needed anymore (and is it still inside the
> > git source tree)?
>
> > On 23 jul, 23:20, Johan de Koning <ikbennu...@gmail.com> wrote:
> > > You are right. Not all the proprietary files are inside the extract-
> > > files.sh script. That means that the AndroidBoard.mk is also not
> > > complete.
>
> > > I submitted a patch for this some time ago:
> >https://review.source.android.com/Gerrit#change,10501
> > > But this patch also downloads the wlan.ko from the device which is not
> > > needed because it is already part of the dream-open project and can
> > > also be compiled from source.
>
> > > On 23 jul, 23:02, dan raaka <danra...@gmail.com> wrote:
>
> > > > Dont you need to add
>
> > > > adb pull /system/lib/libaudio.so proprietary/libaudio.so
> > > > adb pull /system/lib/libcamera.so proprietary/libcamera.so
> > > > adb pull /system/lib/librpc.so proprietary/librpc.so
>
> > > > to extract-files.sh
>
> > > > -Dan
>
> > > > On Thu, Jul 23, 2009 at 1:50 PM, Johan de Koning <ikbennu...@gmail.com
> > >wrote:
>
> > > > > What do you mean with sync cupcake? From this thread
>

> >http://groups.google.com/group/android-platform/browse_thread/thread/.<http://groups.google.com/group/android-platform/browse_thread/thread/>
> > ..

[Jean-Baptiste Queru]

That's yet another orthogonal issue. Yeah, that kind of hack is still
needed. I've been wishing to get this fixed just about forever, just
never found time to come up with an acceptable solution.

JBQ

[Johan de Koning]

BTW about the SdkSetup. I was mistaken. It is still part of the
source. Under developmen/apps

[Jean-Baptiste Queru]

BTW, thanks for all the interest in getting the Android Open-Source
Project to run on Dream. I'm planning to improve the support as time
goes, and the recent manifest change is just a beginning. I'm going to
plug process holes as time goes, and my end goal is get to a state
where it's possible to build an actually usable and fully functional
system image from the open-source tree.

JBQ

[dan raaka]

hmm .. isn't all public commits to be made against master only ??

-Dan

[dan raaka]

without any changes ..

 

 

the following build error on cupcake ..

 

 

make: *** No rule to make target `vendor/htc/dream-open/proprietary/libOmxCore.so', needed by `out/target/product/dream-open/obj/lib/libOmxCore.so'.  Stop.
make: *** Waiting for unfinished jobs....
external/neven/FaceRecEm/common/src/b_FDSDK/DCR.c: In function 'btk_DCR_assignImageROI':
external/neven/FaceRecEm/common/src/b_FDSDK/DCR.c:238: warning: signed and unsigned type in conditional expression
external/neven/FaceRecEm/common/src/b_FDSDK/DCR.c:239: warning: signed and unsigned type in conditional expression

-Dan

[Jean-Baptiste Queru]

In general, given the current process, yes, we (Google) are only
equipped to accept contributions done against master.

vendor/htc/dream-open (formerly known as vendor/htc/dream) was
special, in that it didn't actually exist on Google's internal
servers. That meant that work on it had to happen directly in the
open, so that contributing against any of its branches wasn't
necessarily unreasonable (but it wasn't ideal). It also meant that it
was grossly unmaintained and entirely untested.

I want to get out of that mode and turn Dream into a reliable device
for framework development in the android open-source project.

JBQ

On Thu, Jul 23, 2009 at 3:52 PM, dan raaka<danr...@gmail.com> wrote:

[Jean-Baptiste Queru]

Did you run extract-files.sh ?

JBQ

[dan raaka]

well not quite, but I just copied over the files that I had extracted a while ago.

 

my@user-desktop:~/AndroidSources/cupcake$ ls vendor/htc/dream-open/proprietary/
akmd  AudioFilter.csv  AudioPara4.csv  brf6300.bin  Fw1251r1c.bin  gps.conf  libaudioeq.so  libgps.so  libhgl.so  libhtc_ril.so  libqcamera.so  tiwlan.ini

 

-Dan

[Jean-Baptiste Queru]

Yeah, looks like those were extracted with an older version of the
script (more than 3 months old), going back to the time when
libOmxCore.so wasn't being extracted.

JBQ

[dan raaka]

I hoping someone will post those missing file for me to download ..!!

-Dan

[Jean-Baptiste Queru]

Download the latest image from
http://www.htc.com/www/support/android/adp.html (that's 150275), flash
it on your device, and extract the file from there.

JBQ

[dan raaka]

why flash when there is unyaffs :) ..running build now ..

-Dan

[dan raaka]

cupcake builds now .. with no errors ..

 

Finding NOTICE files: out/target/product/dream-open/obj/NOTICE_FILES/hash-timestamp
Combining NOTICE files: out/target/product/dream-open/obj/NOTICE.html
gzip -c out/target/product/dream-open/obj/NOTICE.html > out/target/product/dream-open/obj/NOTICE.html.gz
Target system fs image: out/target/product/dream-open/obj/PACKAGING/systemimage_unopt_intermediates/system.img
Install system fs image: out/target/product/dream-open/system.img
Installed file list: out/target/product/dream-open/installed-files.txt

:)

-Dan

[The One]

Is there also a way to build the newest source with kernel 2.6.29 for
dream? The problem is everytime I do this the camera isn't working. I
only see a black screen.

[Jean-Baptiste Queru]

I don't think that cupcake works with kernel 2.6.29.

Camera issues are most likely to be related to missing proprietary
files - the current dream-open repository is very far from being
complete. That's on my todo list.

JBQ

[The One]

And would it be possible with the current Android 1.5r2 source.
Because there are already some Images with this source and the new
kernel available on internet.

[Jean-Baptiste Queru]

The different variants of cupcake/1.5 are very close to one another,
too close to make a difference in that area as far as I can tell. I'm
not a kernel guy, though, and you might get some better answers in
that area by reading the archives of the android-kernel group, but I
strongly guess that the conclusion will be "use 2.6.27" when it comes
to contributing to the Android Open-Source Project (note also that
cupcake is closed to external submissions). If you'd like to discuss
and get support for your own experiments, you'll find that the
android-porting group is far more appropriate.

(Someone hinted that the kernel currently in dream-open isn't the
latest and greatest, I'll be looking into that when I get a chance -
it was suggested as well that the kernel should be extracted from the
official ADP1 images).

JBQ

[bmfc187]

Im failing at the "lunch htc_dream-eng" part. Tells me, "bash:
lunch: command not found." i tried to apt-get install lunch, not
found. Any help?

-BMFC

On Jul 23, 12:49 am, Jean-Baptiste Queru <j...@android.com> wrote:
> I've made some progress to build cupcake for dream.
>
> Steps (I hope I have them right):
> sync cupcake (with no local_manifest.xml - all the necessary projects
> are now included in the default manifest)
> in vendor/htc/dream-open, run ./extract-files.sh
> . build/envsetup.sh
> lunch htc_dream-eng
> make
>
> At the moment, this is only valid for cupcake, I'll replicate the
> setup across to donut and master and I'll update the instructions on
> the web site as soon as I get a chance.
>
> JBQ
>

[Jean-Baptiste Queru]

Did you run ". build/envsetup.sh" ? (notice the leading dot)

JBQ

[Chrigi]

The change, that no local_manifest is needed anymore is great. Thank
you.
But it does not check out any kernel. So you're stuck with the
prebuilt one. Which is, as you mentioned, not as up to date as one
would like when you check out the sources...
If everything Dream (ADP) related is checked out anyway, why no kernel
sources?
Oh and btw. Please make a note on the wiki page "Building for Dream"
that the attached local_manifest is not needed anymore (or delete it)
to keep it as straight forward as possible.

And while I'm already at this point: There are two things which would
be very, very nice if they'd get added to the aforementioned wiki
page:
How to check out the kernel sources and how to build it and the needed
modules.
Some Optimization Options. Source or build time. (As long as there
isn't anything in the documentation - I didn't find anything)

[Jean-Baptiste Queru]

The kernel is always built independently anyway, so with the android
build system you're using the prebuilt one anyway regardless of
whether you have the kernel sources. With a keen eye you might even
notice that the one that was mentioned in the local manifest was the
wrong version for cupcake (!)

Further questions about the kernel should be asked on the android-kernel list.

Thanks,
JBQ

[The One]

What do I have to do to build the Android 1.5r3 Release for dream,
because the /htc/dream-open/ direcotry isn't added and maybe also
another directories are missing.

[Jean-Baptiste Queru]

You can probably get away with adding the latest versions of
dream-open and msm7k to your manifest.

JBQ

[The One]

And if I want to recompile the kernel on my own? Do I have to use the
local manifest again?

[Jean-Baptiste Queru]

The kernel source code lives in its own world and isn't integrated
with the rest of the Android build system. The best way to get to it
is to git clone the kernel repository directly, though it you want to
use a local manifest for it that's gonna work too.

JBQ

On Sun, Aug 9, 2009 at 2:46 AM, The One<m.su...@gmail.com> wrote:
>
> And if I want to recompile the kernel on my own? Do I have to use the
> local manifest again?
> >
>

[The One]

If i run the extract-files script it copies everything right except
AudioPara4.csv.

failed to copy '/system/etc/AudioPara4.csv' to 'proprietary/
AudioPara4.csv': Permission denied

[Jean-Baptiste Queru]

Are you starting from the 150275 image from HTC's web site? I believe
that this file isn't accessible on consumer builds.

JBQ

[The One]

Ok i got it from the newest build. I just used unyaffs and changed the
rights. Then I copied it over. Maybe unyaffs should be used generally
instead of adb.

[Zsolt Dollenstein]

Hi,

On Sat, Aug 8, 2009 at 12:03 PM, Jean-Baptiste Queru <j...@android.com> wrote:

You can probably get away with adding the latest versions of
dream-open and msm7k to your manifest.

I can second this, as I have just done so yesterday.

Zsolt
 

[Jean-Baptiste Queru]

150275 as available on HTC's site is the newest build for the ADP1.

JBQ

[Vladimir]

There is more simple way and without ADP1 and extract-files script at
all.
Just download Recovery Image 150275 from HTC's site and look inside
System folder.
You will find all you need.

[Chad]

New to this. Have build custom kernel etc over at XDA. Essentially, I
want to make the AOSP r3 and get to the make stage and get the
following error: build/core/main.mk:402: *** No config file found for
TARGET_DEVICE dream-open. Stop.

I'm familiar with the .config for compiling the kernel, what kind of
config file is it looking for?

Really appreciate the work you do, and thanks in advance.

On Aug 9, 11:38 pm, Jean-Baptiste Queru <j...@android.com> wrote:
> 150275 as available on HTC's site is the newest build for the ADP1.
>
> JBQ
>

[Lutz Schönemann]

I'm trying to build cupcake for the Dev Phone 1 and got stuck on step
4. Can someone tell me what "lunch" is and where to find it? I'm
unable to find any information about that.

A second thing is that "extract-files.sh" was unable to extract /
system/etc/AudioPara4.csv. It has not the right to read it. I had to
copy that file manually.

On 24 Jul., 02:44, dan raaka <danra...@gmail.com> wrote:
> why flash when there is unyaffs :) ..running build now ..
>
> -Dan
>
> On Thu, Jul 23, 2009 at 5:30 PM, Jean-Baptiste Queru <j...@android.com>wrote:
>
>
>
>
>
> > Download the latest image from

> >http://www.htc.com/www/support/android/adp.html(that's 150275), flash

> > it on your device, and extract the file from there.
>
> > JBQ
>

> > On Thu, Jul 23, 2009 at 5:18 PM, dan raaka<danra...@gmail.com> wrote:
> > > I hoping someone will post those missing file for me to download ..!!
> > > -Dan
>
> > > On Thu, Jul 23, 2009 at 5:04 PM, Jean-Baptiste Queru <j...@android.com>
> > > wrote:
>
> > >> Yeah, looks like those were extracted with an older version of the
> > >> script (more than 3 months old), going back to the time when
> > >> libOmxCore.so wasn't being extracted.
>
> > >> JBQ
>

> > >> On Thu, Jul 23, 2009 at 4:57 PM, dan raaka<danra...@gmail.com> wrote:
> > >> > well not quite, but I just copied over the files that I had extracted
> > a
> > >> > while ago.
>
> > >> > my@user-desktop:~/AndroidSources/cupcake$ ls
> > >> > vendor/htc/dream-open/proprietary/
> > >> > akmd  AudioFilter.csv  AudioPara4.csv  brf6300.bin  Fw1251r1c.bin
> > >> >  gps.conf
> > >> > libaudioeq.so  libgps.so  libhgl.so  libhtc_ril.so  libqcamera.so
> > >> > tiwlan.ini
>
> > >> > -Dan
>
> > >> > On Thu, Jul 23, 2009 at 4:31 PM, Jean-Baptiste Queru <j...@android.com
>
> > >> > wrote:
>
> > >> >> Did you run extract-files.sh ?
>
> > >> >> JBQ
>

> > >> >> On Thu, Jul 23, 2009 at 3:52 PM, dan raaka<danra...@gmail.com>

> > wrote:
> > >> >> > without any changes ..
>
> > >> >> > the following build error on cupcake ..
>
> > >> >> > make: *** No rule to make target
> > >> >> > `vendor/htc/dream-open/proprietary/libOmxCore.so', needed by
> > >> >> > `out/target/product/dream-open/obj/lib/libOmxCore.so'.  Stop.
> > >> >> > make: *** Waiting for unfinished jobs....
> > >> >> > external/neven/FaceRecEm/common/src/b_FDSDK/DCR.c: In function
> > >> >> > 'btk_DCR_assignImageROI':
> > >> >> > external/neven/FaceRecEm/common/src/b_FDSDK/DCR.c:238: warning:
> > >> >> > signed
> > >> >> > and
> > >> >> > unsigned type in conditional expression
> > >> >> > external/neven/FaceRecEm/common/src/b_FDSDK/DCR.c:239: warning:
> > >> >> > signed
> > >> >> > and
> > >> >> > unsigned type in conditional expression
>
> > >> >> > -Dan
>

> > >> >> > On Thu, Jul 23, 2009 at 3:52 PM, dan raaka <danra...@gmail.com>

> > >> >> > wrote:
>
> > >> >> >> hmm .. isn't all public commits to be made against master only ??
> > >> >> >> -Dan
>
> > >> >> >> On Thu, Jul 23, 2009 at 2:20 PM, Johan de Koning

> > >> >> >> <ikbennu...@gmail.com>

> > >> >> >> wrote:
>
> > >> >> >>> You are right. Not all the proprietary files are inside the
> > >> >> >>> extract-
> > >> >> >>> files.sh script. That means that the AndroidBoard.mk is also not
> > >> >> >>> complete.
>
> > >> >> >>> I submitted a patch for this some time ago:
> > >> >> >>>https://review.source.android.com/Gerrit#change,10501
> > >> >> >>> But this patch also downloads the wlan.ko from the device which
> > is
> > >> >> >>> not
> > >> >> >>> needed because it is already part of the dream-open project and
> > can
> > >> >> >>> also be compiled from source.
>
> > >> >> >>> On 23 jul, 23:02, dan raaka <danra...@gmail.com> wrote:
> > >> >> >>> > Dont you need to add
>
> > >> >> >>> > adb pull /system/lib/libaudio.so proprietary/libaudio.so
> > >> >> >>> > adb pull /system/lib/libcamera.so proprietary/libcamera.so
> > >> >> >>> > adb pull /system/lib/librpc.so proprietary/librpc.so
>
> > >> >> >>> > to extract-files.sh
>
> > >> >> >>> > -Dan
>
> > >> >> >>> > On Thu, Jul 23, 2009 at 1:50 PM, Johan de Koning
> > >> >> >>> > <ikbennu...@gmail.com>wrote:
>
> > >> >> >>> > > What do you mean with sync cupcake? From this thread
>

> >http://groups.google.com/group/android-platform/browse_thread/thread/.<http://groups.google.com/group/android-platform/browse_thread/thread/>
> > ..

[Jean-Baptiste Queru]

This is known to happen on some linux systems other than ubuntu
8.04.3. If I remember correctly the build system in cupcake doesn't
work with recent versions of bash and/or findutils. I believe that
this was fixed in donut and master.

JBQ

[Jean-Baptiste Queru]

lunch is a shell function installed by envsetup.sh. You need to source
envsetup.sh into your shell before you can use lunch:

$ . build/envsetup.sh # notice the leading dot
$ lunch htc_dream-eng
$ make

As for AudioPara4.csv, I believe that it can't be read from consumer
("user") builds, but that it can be read on debug ("userdebug") builds
like the official ADP1 build. Be sure that you start from the ADP1
build 150275 when trying to do your own build, so that you get the
same files as everyone else.

JBQ

2009/8/10 Lutz Schönemann <lutz.sch...@sit.fraunhofer.de>:

[Lutz Schönemann]

Thanks. But there is one more thing. How can I specify that I want to
build cupcake and not donut?

[Jean-Baptiste Queru]

You do that be specifying which version to sync on the repo init command line:

$ repo init [...] -b cupcake # gets you cupcake
$ repo init [...] -b donut # gets you donut

It *might* be possible (from a perfectly clean tree) to switch between
the two by using "repo init -b cupcake; repo sync" on a donut tree, or
"repo init -d donut; repo sync" on a cupcake tree - but this has been
known to have issues.

[Chad Cyrowski]

Drats, I'm using Ubuntu 9.04. Thanks for your timely response, I'm off to set up a new environment!

[alien]

I compiled cupake succefully for a dream using all propertary files
extraced by extract-files.sh script. All work except camcorder
application. Affer starting it i get a black screen. Does anybody have
the same problem? Is there a solution for this problem?

Best wishes

[Chad Cyrowski]

This may be a late response, but did you use a custom kernel or the
generic kernel? I had to roll back commits to July 11th for custom
kernel.

[The One]

Today I compiled the Android 1.5r3 sources and I also compiled the
2.6.27 Kernel. Everything worked. But there are no images in the /out/
target/product/dream-open directory. The system folder is there, but
there is no system image, no boot image and no userdata image. Altough
i added the msm7k and dream-open sources to the manifest. Why are
there no images, but the system folder?

[Chad Cyrowski]

I'm still getting the following error even though I downgraded to Ubuntu 8.04 

"build/core/main.mk:402: *** No config file found for TARGET_DEVICE dream-open. Stop. 

I have followed the setup instructions to the T, and had no problem whatsoever building a kernel. Any help at all would be greatly appreciated. 

[Jean-Baptiste Queru]

Are you building cupcake or android-1.5r3? (the latter doesn't have
all the files for dream if I remember correctly).

JBQ

[Chad Cyrowski]

.. r3... do you know the missing files or ppoint me in the right direction?

On Aug 12, 2009 8:23 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:


Are you building cupcake or android-1.5r3? (the latter doesn't have
all the files for dream if I remember correctly).

JBQ

On Wed, Aug 12, 2009 at 4:52 PM, Chad Cyrowski<ccyr...@gmail.com> wrote: > I'm still getting the ...

Jean-Baptiste M. "JBQ" Queru Software Engineer, Android Open-Source Project, Google. Questions sent...

--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subs...

[Jean-Baptiste Queru]

1.5r3 is missing hardware/msm7k and vendor/htc/dream-open.

The easiest way to get you back on cupcake should be "repo init -b
cupcake ; repo sync". You probably want to make a copy of your files
first (i.e. cp -R mydroid mydroid2) just in case something goes wrong.

JBQ

On Wed, Aug 12, 2009 at 6:21 PM, Chad Cyrowski<ccyr...@gmail.com> wrote:
> .. r3... do you know the missing files or ppoint me in the right direction?
>
> On Aug 12, 2009 8:23 PM, "Jean-Baptiste Queru" <j...@android.com> wrote:
>
>
> Are you building cupcake or android-1.5r3? (the latter doesn't have
> all the files for dream if I remember correctly).
>
> JBQ
>
> On Wed, Aug 12, 2009 at 4:52 PM, Chad Cyrowski<ccyr...@gmail.com> wrote: >
> I'm still getting the ...
>
> Jean-Baptiste M. "JBQ" Queru Software Engineer, Android Open-Source Project,
> Google. Questions sent...
>
> >
>



--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.

[The One]

I added both of these projects. Everything got synced correctly. Also
the sources got compiled correctly without error. BUT there are no
images in the output directory. There is only the system folder and
some other folders, but no images.

Whats the problem there??

[Jean-Baptiste Queru]

Amusingly, I don't actually know where the images are, because I don't
need to know.

I just boot my device into the bootloader (hold the back key when
powering up or rebooting) and run "fastboot flashall" (or fastboot -w
flashall") - that finds the right images and flashes them.

JBQ

[The One]

Yeah but this only works if the images are in the directory where
fastboot is executed I think. I know that the boot.img and the
system.img where in the out/vendor/product/dream-open evertime i
compiled the source.

On 13 Aug., 15:49, Jean-Baptiste Queru <j...@android.com> wrote:
> Amusingly, I don't actually know where the images are, because I don't
> need to know.
>
> I just boot my device into the bootloader (hold the back key when
> powering up or rebooting) and run "fastboot flashall" (or fastboot -w
> flashall") - that finds the right images and flashes them.
>
> JBQ
>

[Jean-Baptiste Queru]

I always run fastboot from the root of my source tree, right where I
ran make, and it's been working fine for me since "forever".

JBQ