Difference between revisions of "Core (real-time) Framework v0.1 - Installation Instructions"

From wiki.gpii
Jump to: navigation, search
(Fedora 17)
Line 132: Line 132:
[http://localhost:8081/user/sammy/logout http://localhost:8081/user/sammy/logout]
[http://localhost:8081/user/sammy/logout http://localhost:8081/user/sammy/logout]
== Mac Installation Instructions ==
Covering the installation of the universal package and node.js.
<span style="color:#ff0000;">'''The Mac installation doesn't do much yet except running gpii in node.js. There are no settings handlers or listeners implemented yet, so only the http GET or POST requests will work.'''</span>
*Installing make: The make compiler is not automatically included in a Mac, but is included in the Xcode development package.
**If you have already installed xcode, you can skip this step. Otherwise there are two possibilities as described below. Anyway you need an apple developer account, which is for free at this time.
**Download and install Xcode from the apple developers page [https://developer.apple.com/devcenter/ Apple Developer Center]
**or only install the "Command Line Tools For XCode" from [https://developer.apple.com/downloads/ Apple Developer Downloads]
*Install [https://help.github.com/articles/set-up-git git]. The GUI-Tools automatically install the command line tools too.
*Install node.js in the terminal:
<pre>git clone git://github.com/ry/node.git
cd /node
sudo make install</pre>
*Install GPII Universal
(to be tested.)
<pre>git clone git://github.com/GPII/universal.git</pre>
finally you need to mimic the structure in the git gpii linux version.
*move the just downloaded "universal" directory to a place you like.
*create a folder-structure looking like this
<pre>- gpii
- mac
-- index.js
- node-modules
-- universal
*the index.js file needs to be created and for the beginning can contain
GPII Linux Personalization Framework Node.js Bootstrap
Copyright 2012 OCAD University
Licensed under the New BSD license. You may not use this file except in
compliance with this License.
You may obtain a copy of the License at
var fluid = require("universal"),
    gpii = fluid.registerNamespace("gpii");
// fluid.require("gsettingsBridge", require); /* linux specific, like this you can load the handlers and listeners as soon as they are developed. */
    nodeEnv: gpii.config.getNodeEnv("fm.ps.sr.dr.mm.os.development"),
    configPath: gpii.config.getConfigPath() || "../node_modules/universal/gpii/configs"
*the "universal" folder is the recently downloaded folder from github, containing all the downloaded files.
*open the terminal and go to the just created index.js file. run:
<pre>node index.js
Well done, this will start the node.js server and make gpii running and listening. The Port number on which it is listening should be shown in the second-last output line, like this:
13:04:25.786:  Firing event registerMiddleware of component with typename gpii.requests and id 9c0m8p6e-14 to list of 1 listeners
13:04:25.787:  Firing event onHandlers of component with typename gpii.server and id 9c0m8p6e-9 to list of 1 listeners
13:04:25.789:  Server is running on port: 8081
13:04:25.789:  Cleared instantiators (last id 9c0m8p6e-8) from threadLocal for end of flowManager.preferencesServer.solutionsRegistry.deviceReporter.matchMaker.ontologyServer.development

Revision as of 15:40, 11 February 2013

Installation Instrutions

This release supports two platforms; windows 7 and Fedora Linux with Gnome 3. Installation instructions can be found below

Fedora 17


  • Fedora 17 needs to be installed. Installation requires super-user privileges.

Installation Instructions

Ensure pre-requisites

sudo yum install kernel-devel kernel-headers dkms gcc gcc-c++ \
  git openssl-devel glib-devel glib2-devel gtk3-devel \
  pcsc-lite-devel pcsc-lite pcsc-perl

Install node

sudo yum localinstall --nogpgcheck http://nodejs.tchol.org/repocfg/fedora/nodejs-stable-release.noarch.rpm
sudo yum install nodejs nodejs-devel nodejs-gyp nodejs-doc nodejs-debuginfo
sudo ln -s /usr/bin/nodejs /usr/bin/node

Install RFID listener

(only required if you want to use a RFID listener on the system)

Go to the location where you want to install the GPII

Clone the GPII PCSC Tools Repository

git clone https://github.com/GPII/linux-rfid-user-listener
cd linux-rfid-user-listener

Compile and install

make all
sudo make install

Final step is to start a daemon running in the background and the scanner

Start first daemon and then scanner:

sudo /usr/sbin/pcscd

Install and run GPII Personalization Framework

Make sure you're in the directory where you want to install the GPII.

From the command line:

# Clone the GPII Linux repository:
git clone git://github.com/GPII/linux.git
cd linux

# Build the Framework:

# Start up the Personalization Framework:

Running the framework in general

After having followed the above steps, you will have installed the GPII and it should be running on the machine. In general (for example after a reboot), you would have to do the following steps:

To starts GPII, go to the GPII install dir, then:

cd linux

To enable the RFID listener, go to the GPII install dir, then:

cd linux-rfid-user-listener
sudo /usr/sbin/pcscd

Windows Installation Instructions


Building and Starting

  • Open up cmd.exe (Start > Run > cmd.exe)
  • Create a GPII directory
    • mkdir c:\gpii (or wherever you prefer)
    • cd c:\gpii
  • Clone the GPII Windows repository
    • git clone git://github.com/GPII/windows.git
    • cd windows
  • Compile the GPII Windows native code (run the following command from the Windows/DOS shell):
    • build.cmd
  • Start the GPII Framework and the USB Listener (from the Windows/DOS shell - not the Git Bash sell - while in the gpii\windows folder):
    • start.cmd

Setup and Configuration

  • On Windows 7, the GPII can't currently kill applications using taskill unless you:
    • Go into Control Panels > User Accounts and Family Safety > User Accounts > User Account Control Settings
    • Set the notification level to "Never notify"


Once you start the system (by using the start.cmd/start.sh scripts), you can test it without USB by navigating your browser to the following URLs: