Difference between revisions of "WebOS Internals Source Code Repositories"

From WebOS Internals
Jump to navigation Jump to search
(Created page with '=WebOS Internals Source Code Repositories= This page has all the information that you need to know about the WebOS Internals Source Code Repositories. ==Getting Access== For co…')
 
Line 5: Line 5:
 
==Getting Access==
 
==Getting Access==
 
For commit permission to this repository please contact rwhitby on #webos-internals or email [mailto:support@webos-internals.org support@webos-internals.org]
 
For commit permission to this repository please contact rwhitby on #webos-internals or email [mailto:support@webos-internals.org support@webos-internals.org]
 +
  
 
==Build, commit and publishing process==
 
==Build, commit and publishing process==
 
 
# Create a local git repository and write your application.
 
# Create a local git repository and write your application.
 
# Request a new git repository and Makefile from rwhitby (see Getting Access above).
 
# Request a new git repository and Makefile from rwhitby (see Getting Access above).
#  
+
# Once you have access to the repository then you can push your application changes to the remote repository.
 
+
# Your code lives in these git repositories, but the metadata used by Preware is in the [http://git.webos-internals.org/?p=preware/build.git;a=summary preware build makefiles].  Here is a [http://git.webos-internals.org/?p=preware/build.git;a=blob;f=apps/wolui/Makefile;h=e995d097d8cd70fbb44afe30c871ee6b707de210;hb=HEAD sample makefile].
 
+
# Once you have updated the Makefile for your application then you can publish the changes back to the remote repository <pre>git push git@git.webos-internals.org:preware/build.git</pre>.
Build Logs: http://logs.nslu2-linux.org/ Look for the 'tinker' box.
+
# The build process is run about every 15 minutes, but might take a little longer.  Check the [http://logs.nslu2-linux.org/ build log files (look for the 'tinker' ones)] and ensure that your changes have been successfully compiled.  Please note that if your build fails then the build for all subsequent applications will fail as well.  So, it is important to ensure that the your code is built without any issues.
 
+
# Once your code has been compiled it will be published to the Preware Feeds in Preware so now you can update the feeds and install/update your app on your webOS device.
git push git@git.webos-internals.org:preware/build.git
 
 
 
 
 
==Publishing Updates==
 
 
 
 
 
 
 
 
 
==Compile Process==
 
How often are the compiles done?
 
Every 15 minutes
 

Revision as of 05:43, 8 November 2010

WebOS Internals Source Code Repositories

This page has all the information that you need to know about the WebOS Internals Source Code Repositories.

Getting Access

For commit permission to this repository please contact rwhitby on #webos-internals or email support@webos-internals.org


Build, commit and publishing process

  1. Create a local git repository and write your application.
  2. Request a new git repository and Makefile from rwhitby (see Getting Access above).
  3. Once you have access to the repository then you can push your application changes to the remote repository.
  4. Your code lives in these git repositories, but the metadata used by Preware is in the preware build makefiles. Here is a sample makefile.
  5. Once you have updated the Makefile for your application then you can publish the changes back to the remote repository
    git push git@git.webos-internals.org:preware/build.git
    .
  6. The build process is run about every 15 minutes, but might take a little longer. Check the build log files (look for the 'tinker' ones) and ensure that your changes have been successfully compiled. Please note that if your build fails then the build for all subsequent applications will fail as well. So, it is important to ensure that the your code is built without any issues.
  7. Once your code has been compiled it will be published to the Preware Feeds in Preware so now you can update the feeds and install/update your app on your webOS device.