Services/Sync/Getting Started: Difference between revisions

Line 46: Line 46:
However, this is slow. If you have simply changed a JS file in ''services/sync/'', it is sufficient to run the following from your object directory:
However, this is slow. If you have simply changed a JS file in ''services/sync/'', it is sufficient to run the following from your object directory:


  $ make -C services/sync
  $ make -sj8 -C services/sync


The xpcshell tests will pick up changes immediately. However, if you launch Firefox, your changes '''won't''' be reflected. For that, you'll also need to rebuild the browser component:
The xpcshell tests will pick up changes immediately. However, if you launch Firefox, your changes '''won't''' be reflected. For that, you'll also need to rebuild the browser component:


  $ make -C services/sync && make -C browser
  $ make -sj8 -C services/sync && make -sj8 -C browser


A handy alias to have around is:
A handy alias to have around is:


  $ alias sync-launch make -C services/sync && make -C browser && dist/bin/firefox -no-remote -ProfileManager
  $ alias sync-launch make -sj8 -C services/sync && make -sj8 -C browser && dist/bin/firefox -no-remote -ProfileManager


Or, on OS X:
Or, on OS X:


  $ alias sync-launch make -C services/sync && make -C browser && dist/NightlyDebug.app/Contents/MacOS/ -no-remote -ProfileManager
  $ alias sync-launch make -sj8 -C services/sync && make -sj8 -C browser && dist/NightlyDebug.app/Contents/MacOS/ -no-remote -ProfileManager


= Using Bugzilla =
= Using Bugzilla =
canmove, Confirmed users
725

edits