Download - Revision history

Shirak: /* Xcode　is somehow wrong */

2017-05-18T10:05:10Z

‎Xcode　is somehow wrong

Shirak: /* Library is not installed */

2017-05-18T04:20:51Z

‎Library is not installed

Shirak: /* "Downloading and running" only case、i.e. without developing */

2017-05-18T00:19:22Z

‎"Downloading and running" only case、i.e. without developing

Shirak: /* Registering your changes in Eos by "git" */

2017-05-17T12:13:06Z

‎Registering your changes in Eos by "git"

Shirak: /* Registering your changes in Eos by "make" */

2017-05-17T07:06:33Z

‎Registering your changes in Eos by "make"

Shirak: /* Add changes */

2017-05-17T06:23:28Z

‎Add changes

Shirak: /* The other way for getting the latest version */

2017-05-17T00:32:48Z

‎The other way for getting the latest version

Shirak: /* Getting the latest version */

2017-05-16T05:52:31Z

‎Getting the latest version

Shirak: /* Using make */

2017-05-16T05:51:17Z

‎Using make

Shirak: /* Running the update command */

2017-05-16T02:45:34Z

‎Running the update command

@@ Line 503: / Line 503: @@
   sudo cp /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Resources/libTIFF.dylib $EOS_HOME//util/X86MAC64/lib/
+This should be OK。An effort is being made so that this problem will not occur.
-−
-−
-−
-−
-−
-. tarball [http://www.yasunaga-lab.bio.kyutech.ac.jp/ja/reserach/eos/eos-download-sites/]
-−
-. git from SourceFoge [http://sourceforge.jp/projects/eos/]
- $ git clone git://git.sourceforge.jp/gitroot/eos/base.git
-  or
- $ git clone git://git.code.sf.net/p/eosforemimageprocessing/code eosforemimageprocessing-code
-−
-−
-−
-. (PIONE) github or gem
-−
-.1 gem (ruby)
- $ gem install pione
-−
-.2 git from github
- $ git clone https://github.com/pione/pione.git

← Older revision		Revision as of 04:20, 18 May 2017
Line 484:		Line 484:
	$ yum install /libXss*		$ yum install /libXss*

		+	=== Xcode　is somehow wrong ===
		+
		+	Q2 ) "make" in the OS-X produces an error:
		+
		+	sh: line 1: 8482 Trace/BPT trap: 5 /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk '' -find make 2> /dev/null
		+	make: error: unable to find utility "make", not a developer tool or in PATH
		+
		+	A2)　The error arises because some of the dynamic libraries are wrong.
		+
		+	Execute the command,
		+
		+	/Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -sdk '' -find make
		+
		+	This will output error messages on missing libraries. In most cases、the path setting of the dynamic libraries are wrong.
		+
		+	Necessary libraries should be copied to $EOS_HOME//util/X86MAC64/lib/ like,
		+
		+	sudo cp /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Resources/libTIFF.dylib $EOS_HOME//util/X86MAC64/lib/

← Older revision		Revision as of 00:19, 18 May 2017
Line 459:		Line 459:

	※　Note that, since 2013/02, the directory structure has been changed drastically. This is because we liked to separate the binaries, which are host dependent, and the source codes, which are not. And also because we liked to execute in a single directory which can be, for example, a directory exported by NFS, while keeping a capability to execute in heterogeneous environments.		※　Note that, since 2013/02, the directory structure has been changed drastically. This is because we liked to separate the binaries, which are host dependent, and the source codes, which are not. And also because we liked to execute in a single directory which can be, for example, a directory exported by NFS, while keeping a capability to execute in heterogeneous environments.
		+
		+
		+	== Systems ==
		+
		+	The following systems have been checked OK for running the Eos。
		+
		+	LINUX 32bits/64bits
		+	OS-X 32bits/64bits
		+	Windows with Cygwin
		+
		+
		+	==Trouble shooting ==
		+
		+	=== Compilation faiure ===
		+	Q1)　When a tool is executed, you see a message " Not Installed: XXXXX-version YYYYYY"
		+
		+	A1)　Failure in compiling and linking. Move to CLASS/YYYYYY under src/Tools. Then key in <br>
		+	make check; make depend; make install
		+
		+	=== Library is not installed ===
		+	Q1) When you find a message "/....../Eos/bin/X86LINUX64/Display2: error while loading shared libraries: libXss.so.1: cannot open shared object file: No such file or directory”
		+
		+	A1) Install libXss.
		+	$ yum install /libXss*
		+
		+

← Older revision		Revision as of 12:13, 17 May 2017
Line 444:		Line 444:

	※ For details of git commands, see [[http://sourceforge.jp/magazine/09/03/16/0831212 sourceforge]] or books on git。		※ For details of git commands, see [[http://sourceforge.jp/magazine/09/03/16/0831212 sourceforge]] or books on git。
		+
		+	== "Downloading and running" only case、i.e. without developing ==
		+
		+	You can download a binary tarball from the site,
		+
		+	[[http://www.yasunaga-lab.bio.kyutech.ac.jp/ja/reserach/eos/eos-download-sites/ EosHomePage]]
		+	or
		+	[[http://sourceforge.jp/projects/eos/releases/ Sourceforge]]
		+
		+
		+	For the binaries that are not uploaded, you can contact yasunaga@bio.kyutech.ac.jp.
		+
		+	The directory structure（[[Eos structure]]）is found in other pages。
		+
		+	※　Note that, since 2013/02, the directory structure has been changed drastically. This is because we liked to separate the binaries, which are host dependent, and the source codes, which are not. And also because we liked to execute in a single directory which can be, for example, a directory exported by NFS, while keeping a capability to execute in heterogeneous environments.
		+

← Older revision		Revision as of 07:06, 17 May 2017
Line 427:		Line 427:

	$ make git-push ; # You upload in SourceForge		$ make git-push ; # You upload in SourceForge
		+
		+	=== Registering your changes in Eos by "git" ===
		+
		+	Registering of your changes for addition of functions or for corrections are described below.
		+
		+	git add ; # add the changed version of your copy
		+	git commit ; # put the changes in git
		+	#
		+	git push ; # put in the git server
		+	or
		+	git push origin master
		+	or
		+	git push origin master
		+
		+	When a repository other than "master" is preferred, prepare an appropriate directory。
		+
		+	※ For details of git commands, see [[http://sourceforge.jp/magazine/09/03/16/0831212 sourceforge]] or books on git。
		+

← Older revision		Revision as of 06:23, 17 May 2017
Line 410:		Line 410:
	$ git merge FETCH_HEAD ;# Merge what has been changed		$ git merge FETCH_HEAD ;# Merge what has been changed

		+	=== Registering your changes in Eos by "make" ===
		+
		+	The installation can be done using the Makefile supplied in Eos. In this mode, you register in the master repository.
		+
		+
		+	$ cd $EOS_HOME ; # Move to the Eos directory.。
		+	$ make git-add ; # Put changed files in the repository temporarily
		+	$ make git-commit ; # Put comments in the repository
		+	Changing a tag<br>
		+	※ The version name tag is attached to the source codes on each uploading for administration purposes. Please do not forget to attach the tag, according to the rules descibed in [[Eos developemnt]], before you upload.
		+
		+	$ git tag
		+	$ git tag newtag
		+
		+	You can now upload,
		+
		+	$ make git-push ; # You upload in SourceForge

← Older revision		Revision as of 00:32, 17 May 2017
Line 401:		Line 401:

	$ git pull git://git.sourceforge.jp/gitroot/eos/base.git		$ git pull git://git.sourceforge.jp/gitroot/eos/base.git
		+
		+	==== check changes ====
		+	$ git log FETCH_HEAD ;# Shows the changes
		+
		+	==== Add changes ====
		+	After checking the changes and seeing that those changes can be merged, add the changes. You have to be careful when you have made your own changes.
		+
		+	$ git merge FETCH_HEAD ;# Merge what has been changed
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+
		+

← Older revision		Revision as of 05:52, 16 May 2017
Line 396:		Line 396:
	$ git fetch git://git.sourceforge.jp/gitroot/eos/base.git		$ git fetch git://git.sourceforge.jp/gitroot/eos/base.git

		+
		+	===== The other way for getting the latest version =====
		+	In git pull, fetch/merge and others are done automatically. When you did not change the source codes, you may well do in this manner. This is recommended only if you know very well what went on. If you are not very sure, the fetch/merge procedure is recommended.
		+
		+	$ git pull git://git.sourceforge.jp/gitroot/eos/base.git

← Older revision		Revision as of 05:51, 16 May 2017
Line 388:		Line 388:
	$ make git-fetch		$ make git-fetch
	$ make git-merge		$ make git-merge
		+
		+	==== Getting the latest version ====
		+	$ git fetch ;# download changed files
		+	or
		+	$ git fetch ssh://${EOS_GITUSER}@git.sourceforge.jp:/gitroot/eos/base.git
		+	or
		+	$ git fetch git://git.sourceforge.jp/gitroot/eos/base.git

← Older revision		Revision as of 02:45, 16 May 2017
Line 375:		Line 375:
	or		or
	$ EOS_GITUSER0=user source $EOS_HOME/env/update-eos.sh directory		$ EOS_GITUSER0=user source $EOS_HOME/env/update-eos.sh directory
		+
		+	=== Updating to the newest version (when you have downloaded using git) ===
		+	You do the update as shown below.
		+
		+	==== Using make ====
		+	If $EOS_HOME/Makefile is the newest, do the following.
		+	<br>
		+	※ Note: $EOS_HOME points to the$HOME/Eos directory.<br>
		+	When you use the environment file without changes, you put the base directory at $HOME and rename it as Eos。
		+
		+	$ cd $EOS_HOME
		+	$ make git-fetch
		+	$ make git-merge
		+