Difference between revisions of "Template:Luneos install"

From WebOS-Ports
Jump to: navigation, search
 
(23 intermediate revisions by 4 users not shown)
Line 4: Line 4:
 
|warning=THIS PAGE IS NOT A REGULAR WIKI PAGE.  IT IS A WIKI *TEMPLATE* AUTO-INCLUDED INTO POTENTIALLY HUNDREDS OF OTHER PAGES.  ANY CHANGE MADE HERE WILL AFFECT ALL THESE PAGES SIMULTANEOUSLY, INCLUDING PAGES DEALING WITH MANY TYPES OF DEVICES.  SO DO NOT EDIT THIS PAGE UNLESS YOU KNOW '''EXACTLY''' WHAT YOU ARE DOING.  THANKS!}}
 
|warning=THIS PAGE IS NOT A REGULAR WIKI PAGE.  IT IS A WIKI *TEMPLATE* AUTO-INCLUDED INTO POTENTIALLY HUNDREDS OF OTHER PAGES.  ANY CHANGE MADE HERE WILL AFFECT ALL THESE PAGES SIMULTANEOUSLY, INCLUDING PAGES DEALING WITH MANY TYPES OF DEVICES.  SO DO NOT EDIT THIS PAGE UNLESS YOU KNOW '''EXACTLY''' WHAT YOU ARE DOING.  THANKS!}}
 
</noinclude>
 
</noinclude>
==Install the build==
+
==Installing and running the image==
{{Commentlink
+
<!--{{Commentlink
 
|section=install-the-build-for-{{{device_name}}}
 
|section=install-the-build-for-{{{device_name}}}
}}
+
}}-->
  
  
Assuming the build completed without error (it will be obvious when it finishes), type:
+
Assuming the build completed without error (it will be obvious when it finishes).
  
<code># cd $OUT</code>
+
Once you have built the image, you'll likely want to install it and run it on your {{{device_name}}}. See [http://webos-ports.org/wiki/Install_LuneOS_for_{{{device_codename}}} Testing LuneOS for {{{device_name}}}] for further details on that process.
  
in the same terminal window that you did the build. Here you’ll find all the files that were created. The stuff that will go in <code>/system</code> is in a folder called <code>system</code>. The stuff that will become your ramdisk is in a folder called <code>root</code>. And your kernel is called... <code>kernel</code>.
+
Remember: The file you want to sideload on your device is '''<build env>/tmp-glibc/deploy/images/{{lc:{{{device_codename}}}}}/{{#ifeq:{{lc:{{{device_codename}}}}}|tenderloin| luneos-dev-image-tenderloin.tar.gz | luneos-dev-package-{{lc:{{{device_codename}}}}}.zip }} '''
  
But that’s all just background info. The two files we are interested in are (1) <code>recovery.img</code>, which contains ClockworkMod recovery, and (2) <code>WOP<nowiki>-[</nowiki>something].zip</code>, which contains WebOS Ports Open webOS.
+
If you also need the kernel, it's in '''<build env>/tmp-glibc/deploy/images/{{lc:{{{device_codename}}}}}/uImage'''
<!--
 
add recovery instructions
 
-->
 
  
{{#if:{{{device_recovery_install_method|}}}|{{recovery_install_{{{device_recovery_install_method}}}
+
=== Success!  And next steps? ===
|device_name={{{device_name}}}}}}}
 
  
===Install WebOS Ports open WebOS===
+
''You've done it!''  Welcome to the club of people who can build their operating system from the source code! Hopefully you enjoyed the experience and are inspired to do more!
  
{{Commentlink|section=install-wop-for-{{{device_name}}}
+
To rebuild after the source code has changed on GitHub,
}}
+
* If you've logged in again to the virtual machine, run setup-env, as above
 
+
* Pull the latest code from GitHub by running <code>make update</code>, as above
Back to the <code>$OUT</code> directory on your computer-- you should see a file that looks something like:
+
* Build, as above
 
 
<code>wop1.0alpha2-{{CURRENTYEAR}}{{CURRENTMONTH}}{{CURRENTDAY2}}-UNOFFICIAL-{{{device}}}.zip</code>
 
 
 
{{Note|note=The above file name may vary depending on the version of WebOS Ports Open webOS you are building.  Your build may not include a version number or may identify itself as a "<code>KANG</code>" rather than <code>UNOFFICIAL</code> version.  Regardless, the file name will end in <code>.zip</code> and should be titled similarly to official builds.}}
 
 
 
Now you can flash the <code>wop...zip</code> file above as usual via recovery mode.  (Be sure you have backed up any previous installation before trying your new build.)
 
 
 
=== Success!  So....what's next? ===
 
 
 
''You've done it!''  Welcome to the elite club of self-builders.  You've built your operating system from scratch, from the ground up.  You are the master/mistress of your domain... and hopefully you've learned a bit on the way and had some fun too.
 
 
 
Now that you've succeeded in building WebOS Ports open WebOS for your device, here are [[After_You_Build|some suggestions on what to do next]].
 
 
 
Also, be sure to take a glance at the [[Development|Dev Center]] on this wiki for all kinds of more detailed information about developer topics ranging from [[Doc:_debugging_with_logcat|collecting logs]], understanding [[Doc:_the_wop_source|what's in the source code directories]], [[Doc:_using_gerrit|submitting your own contributions]], [[Doc:_porting_intro|porting WebOS Ports open WebOS]] to new devices, and a lot more.
 
 
 
Congrats again!
 

Latest revision as of 10:08, 28 October 2016


WARNING: DO NOT EDIT!

THIS PAGE IS NOT A REGULAR WIKI PAGE. IT IS A WIKI *TEMPLATE* AUTO-INCLUDED INTO POTENTIALLY HUNDREDS OF OTHER PAGES. ANY CHANGE MADE HERE WILL AFFECT ALL THESE PAGES SIMULTANEOUSLY, INCLUDING PAGES DEALING WITH MANY TYPES OF DEVICES. SO DO NOT EDIT THIS PAGE UNLESS YOU KNOW EXACTLY WHAT YOU ARE DOING. THANKS!

Installing and running the image

Assuming the build completed without error (it will be obvious when it finishes).

Once you have built the image, you'll likely want to install it and run it on your {{{device_name}}}. See Testing LuneOS for {{{device_name}}} for further details on that process.

Remember: The file you want to sideload on your device is <build env>/tmp-glibc/deploy/images/{{{device_codename}}}/luneos-dev-package-{{{device_codename}}}.zip

If you also need the kernel, it's in <build env>/tmp-glibc/deploy/images/{{{device_codename}}}/uImage

Success! And next steps?

You've done it! Welcome to the club of people who can build their operating system from the source code! Hopefully you enjoyed the experience and are inspired to do more!

To rebuild after the source code has changed on GitHub,

  • If you've logged in again to the virtual machine, run setup-env, as above
  • Pull the latest code from GitHub by running make update, as above
  • Build, as above