Installation of PIONE - Revision history

Shirak: /* PIONE install example */

2017-05-24T04:41:08Z

‎PIONE install example

2017-05-24T04:40:31Z

‎Check the update

2017-05-24T04:38:37Z

‎Download and install

2017-05-24T01:19:19Z

‎Checking the libraries

2017-05-23T08:00:35Z

‎An error and how to get around

2017-05-23T05:54:02Z

‎The problem about install

2017-05-22T23:59:57Z

‎Installation with PIONE Webclient, using a installation shell

2017-05-22T07:14:02Z

‎Setting environment

2017-05-22T07:00:19Z

‎Installing directly from github

2017-05-22T06:42:01Z

‎Installing directly from github

← Older revision		Revision as of 04:41, 24 May 2017
Line 223:		Line 223:
	[[PIONE]] update can be done in two ways, via github and via gem. The update via github requires that [[PIONE]] is downloaded/installed from github beforehand. The update via gem is possible if you have [[ruby]], [[gem]], [[bundle]]. Both updates make your version the newest. In the gem use, its update reflects the data immediately after a verion up. In the github use, this update reflects the source code changes. Therefore, github is recommended when you like to check very new bug corrections.<br>		[[PIONE]] update can be done in two ways, via github and via gem. The update via github requires that [[PIONE]] is downloaded/installed from github beforehand. The update via gem is possible if you have [[ruby]], [[gem]], [[bundle]]. Both updates make your version the newest. In the gem use, its update reflects the data immediately after a verion up. In the github use, this update reflects the source code changes. Therefore, github is recommended when you like to check very new bug corrections.<br>
	<br>		<br>
−
−	~~=== [[PIONE]] install example ===~~
−	~~<pre>~~
−	~~Install YAMLand others.~~
−	↓
−	~~Install (compile) Ruby (greater than 1.9.2, but less tahn 2).~~
−	↓
−	~~Install bundle by gem.~~
−	↓
−	~~Install PIONE by gem.~~
−	↓
−	~~Install PIONE Webclient.~~
−	~~</pre>~~
−	~~<br>~~
−
−

@@ Line 222: / Line 222: @@
 == Notes on the update ==
 　[[PIONE]] update can be done in two ways, via github and via gem. The update via github requires that [[PIONE]] is downloaded/installed from github beforehand. The update via gem is possible if you have [[ruby]], [[gem]], [[bundle]]. Both updates make your version the newest.  In the gem use, its update reflects the data immediately after a verion up. In the github use, this update reflects the source code changes. Therefore, github is recommended when you like to check very new bug corrections.<br>
 <br>

@@ Line 190: / Line 190: @@
 </pre>
 (Note) The destination directory（where you can find bin and lib directories）should be given in the absolute path。When you update [[ruby]] from within Eos, you have to be careful.　This is because${EOSHOME}/util/${EOS_HOSTDIR} and directories below it are linked to ${EOS_HOME}/hostdepend/${EOS_HOSTDIR}/util/${EOS_HOSTDIR}.(Refer to :[[よく使うシェルコマンド#pwdによる注意事項]])<br>
 <br>

@@ Line 175: / Line 175: @@
 ==== Checking the libraries ====
 Before compilation, you check if you have all the necessary libraries .In case of openssl described above,  you need to have openssl to be installed. When [[Eos]] has been installed, all the libraries are under the [[Eos]]directory.  Update those according to [[Downlaod#Update by make|Eos update]].You can find the libraries in /Eos/hostdepend/X86MAC/util/X86MAC/（In case of Mac). For a quick update, you visit [http://sourceforge.jp/projects/eos/scm/git/base/tree/master/hostdepend/], select your OS, download only util directory, and then update.<br>
 <br>

@@ Line 150: / Line 150: @@
 => true
 </pre>
 <br>

← Older revision		Revision as of 05:54, 23 May 2017
Line 122:		Line 122:

	bundle can be installed by gem.		bundle can be installed by gem.
		+
		+	=== An error and how to get around ===
		+	An error message:
		+	<pre>
		+	$ bundle install --path vender/bundle
		+
		+	Could not load OpenSSL.
		+	You must recompile Ruby with OpenSSL support or change the sources in your Gemfile from 'https' to 'http'. Instructions
		+	for compiling with OpenSSL using RVM are available at http://rvm.io/packages/openssl.
		+	</pre>
		+	<br>
		+
		+	may suggest that OpenSSL is not included in [[ruby]] that you use. Use irb command as below. (if [[Ruby TIPS#irb]])is not included, you may have to recompile [[ruby]]。<br>
		+	<br>
		+	An example when not included in [[ruby]]<br>
		+	<pre>
		+	$ irb
		+	irb(main):001:0> require 'openssl'
		+	LoadError: libssl.so.0.9.8: cannot open shared object file: No such file or directory
		+	</pre>
		+	<br>
		+
		+	When included in [[ruby], you will see "true"。<br>
		+	<pre>
		+	$ irb
		+	irb(main):001:0> require 'openssl'
		+	=> true
		+	</pre>
		+	<br>
		+

← Older revision		Revision as of 23:59, 22 May 2017
Line 96:		Line 96:

	$ sudo gem install bundler		$ sudo gem install bundler
		+	<br>
		+
		+	=== Check the install ===
		+
		+	Submit the following command [[commands]] to check if the install of [[PIONE]] was OK.<br>
		+	<pre>
		+	$ pione -v
		+	pione 0.5.0
		+	</pre>
		+	<br>
		+	To run [[PIONE]] and [[PIONE Webclient]]、refer to [[PIONE starting]]。<br>
	<br>		<br>

@@ Line 78: / Line 78: @@
 <br>
 　You may well have  this setting to be performed after your shell starts, as in [[Setting environment of Eos]].<br>
-　Those envrionment variables, and commands such as bundle install, are not needed on install. <br>
+　Those environment variables, and commands such as bundle install, are not needed on install. <br>
 <br>

@@ Line 59: / Line 59: @@
 Secondly, update bundle, if you have it. It is to be noted that the bundle install command is run in /pione, or
-  set the path beforehand (Gemfile, vender/bundle and files below it are necessary). <br>
+  set its path beforehand (Gemfile, vender/bundle and files below it are necessary). <br>
 <pre>
 $ cd pione

← Older revision		Revision as of 06:42, 22 May 2017
Line 65:		Line 65:
	</pre>		</pre>

		+	<br>
		+
		+	=== Setting environment ===
		+	Run the following for defining variables of PATH and RUBYLIB.
		+
		+	$ cd ${PIONE_REP}
		+	$ export PATH=$PWD/bin:$PATH
		+	$ export RUBYLIB=$PWD/lib
		+
		+	or running pione/misc/env.sh is able to set the environment.
		+
		+	<br>
		+	You may well have this setting to be performed after your shell starts, as in [[Setting environment of Eos]].<br>
		+	Those envrionment variables, and commands such as bundle install, are not needed on install. <br>
	<br>		<br>