This repository is a workspace for module exploration and common functionality.
On OS X there can be an annoying firewall dialog every time the Magenta tools are rebuilt. To prevent the dialog disable the firewall or sign the new binaries, for instance to sign the
sudo codesign --force --sign - $FUCHSIA_DIR/out/build-magenta/tools/netruncmd
The dialog will now only appear the first time the command is run, at least until it gets rebuilt.
On new or newly provisioned devices it is possible to trigger an SSL error caused by the system clock being set in the future. To prevent this you must set the device clock:
# On Darwin (fgo && DATE=`date +%Y-%m-%dT%T`; ./out/build-magenta/tools/netruncmd : "clock --set $DATE") # On Linux (fgo && DATE=`date -Iseconds`; ./out/build-magenta/tools/netruncmd : "clock --set $DATE")
This only needs to be done once.
Listen to device logs:
Checking out the Fuchsia tree (instructions) will create an empty
config.json in this directory. To enable functionality for the modules living in
//apps/modules/ some values will need to be set.
When the config file is updated a build will be required to load it onto the target device (see the Build section below).
Email, and Chat require values for:
To authenticate (login) with OAuth make sure the oauth_id, and oauth_secret values are set. Generate auth credentials derived from oauth_id, and oauth_secret with:
This will prompt you to follow a link to login via an OAuth flow.
NOTE Re-build to load the new credential values (stored in config.json) onto the target device.
make auth task adds generated credentials to the config.json file used by several modules:
Make sure to start from a “very clean build” (remove $FUCHSIA_DIR/out) if you have built before but didn't do the auth steps above. There is a make task to help with this:
make depclean all
This will clean and create a release build. To do this manually you can use:
source $FUCHSIA_DIR/scripts/env.sh rm -rf $FUCHSIA_DIR/out fset x86-64 --release --modules default fbuild
Assuming you have an Acer properly networked and running
fboot in another terminal session you can run email two different ways.
Running with the full sysui
netruncmd : "@boot device_runner"
Running the email story directly
netruncmd : "@boot device_runner --user_shell=dev_user_shell --user_shell_args=--root_module=<target>"