Android rom out directory issues

[Falcon]

Has the output directory for the final image changed? I have followed the procedures on the android.source.com and do not get any of the images I am supposed to get. I need some help sorting this issue; I also like to learn which files and directories from the build environment are packaged into the final image please.

[Dave Smith]

No change. The build output will always be in $TOP/out unless you explicitly configure a different destination (http://source.android.com/source/initializing.html#using-a-separate-output-directory). You might want to verify that the build output is indicating that your build is completing successfully, and not terminating with an error.

[Falcon]

On Wednesday, October 14, 2015 at 11:04:10 AM UTC-4, Dave Smith wrote:

No change. The build output will always be in $TOP/out unless you explicitly configure a different destination 

This may be the case as I am using the source from AOSP combined with what I downloaded from Samsung. It may be that Samsung Makefile configures a different output directory. My goal however, is to create a system.img and other required image files to be able to run the same image I created for my handset in the emulator. And running the . "build/envsetup.sh" along with lunch does not accomplish that for me. Further I do not enough to know how to convert the files I get as a result of my successful build of the Samsung+AOSP to something the emulator can use. Here is basically what I get at the end of the build session: 

/home/sansari/WORKING_DIRECTORY/scripts/mk_fipsbinary.sh arch/arm/boot/zImage

Make kernel fips binary..

Done.

  Kernel: arch/arm/boot/zImage is ready

  DTC     arch/arm/boot/msm8974-sec-hlte-r03.dtb

All I want to do is to be able to modify the source in build environment, compile it and see how the resulting image runs. I know that I can not run the image I created for a device in the emulator so the output above is just to show that I do have a successful build. And I agree with you; I think that the Makefile from Samsung source changes the output directory. But that is not the only thing it changes; I do not even see a system.img, or a ramdisk.img anywhere. 

[Falcon]

I wonder if it is faster for me to use yaffs2utils package to create test images for the emulator? I do need to know what to include in a system.img. I believe I can get the ramdisk from the andorid-xx folder of SDK with xx being the version I am building for. I am just trying to save time by testing the image on emulator. I only have one device, and it takes a long time to flash the device, and check to see if the package I want is in there.  

On Wednesday, October 14, 2015 at 11:04:10 AM UTC-4, Dave Smith wrote:

[Shahin Ansari]

I found the problem. I was not updating the right core.mk file.

--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to android-...@googlegroups.com
To unsubscribe from this group, send email to
android-buildi...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en

---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-buildi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Never give in, never give in, never, never, never, never-in nothing, great or small, large or petty-never give in except to convictions of honor and good sense.  
                                       -Winston Churchill