But what you’re saying makes a lot of sense. I will go back to my original MagicMirror image and start over and do a git clone from the master branch.
I would like to eventually create a skill for Mycroft to interact with the MagicMirror. Which installation would make more sense to you? Install as a service, or running Mycroft in Virtualenv? It seems to me it would make more sense to run in a virtualenv, but the most important thing will be getting both applications running at the same time and able to easily restart on their own after a reboot. For example, if we lose power.
Whatever advice you can give would be much appreciated. Thanks!
It might be better to run in a virtualenv to keep the dependencies in check. The aptpackage gets cranky if the dependencies versions are changed (as they may do) if pip is used to install stuff on the system.
Top about the dev-setup, avoid the --allow-root flag. It’s meant to run in user mode with sudo. Running as root will install the virtualenv in the root users home folder instead of the user that should be running it (Pi or a separate user).
Sorry I misspoke, you shouldn’t run it as sudo, the script will invoke sudo when necessary.
You should just start it with the normal user with ./dev-setup.sh this will run some parts with sudo and ask for password.
–allow-root is a way to get around the restriction installing the development environment as a normal user in the few cases when it’s actually desirable to install it as root (ex, docker installation), but shouldn’t be used normally.
The installation went ok, with no issues. But when I started
./start-mycroft.sh debug
it gave an error about Padatious. and stopped.
It is apparently an issue with the libfann-dev needing to be newer than what’s in the repo.
I am considering trying two simultaneous builds on different sd cards. One which uses virtualenv and the other installing mycroft as a service through
sudo apt-get install mycroft-core
To see which method presents fewer issues. My concern with the latter is it installs a Mycroft user, and I’m wondering if that will present permission issues that will be harder to overcome.
I tried starting with the picroft image that’s available, but installing MagicMirror on to Jessie Lite proved just as difficult it seems. To install both on the same system requires a 16gb sd card. Fortunately I have 2 to play with.
Thank you so much for your advice. I am very new to all of this. If there is anything else I should look out for with either method, please let me know what you think.
Well… Thanks to your advice, the Mycroft-core is up and running in virtualenv with a working MagicMirror application on the same pi.
It worked following your last suggestion, following these steps listed in these instructions: (not sure all steps were necessary but followed them anyhow)
Update the apt cache to include the new repository
sudo apt-get update
sudo apt-get install libfann2
From there, everything worked like a charm. Now I just need to figure out how to start everything MagicMirror and Mycroft when the desktop boots and I can start working on the MagicMirror skill for mycroft. Do you recommend using .bashrc to start the virtualenv? Or would there be a better suggestion? Considering that it’s necessary to set the desktop to auto login as pi user for the MagicMirror to start?
ok so im starting to see i need help installing the mycroft-core is anyone out there willing to help me please, as im at a loss iv reinstalled stretch as i think iv gone about this all wrong, iv got magicmirror installed.