Install 3rd-party programs or libraries - Revision history

Jadrian Miles: /* Install a complicated source tree */ typo in wget example

2010-10-18T14:52:40Z

Install a complicated source tree: typo in wget example

← Older revision		Revision as of 14:52, 18 October 2010
Line 67:		Line 67:
	download:		download:
	rm -rf src nifti.zip		rm -rf src nifti.zip
	wget -rq --reject ".html" --nH --cut-dirs=2 http://nifti.nimh.nih.gov/pub/dist/src/		wget -rq --reject ".html" -nH --cut-dirs=2 http://nifti.nimh.nih.gov/pub/dist/src/
	zip -r nifti.zip src		zip -r nifti.zip src
	rm -rf nifti.zip		rm -rf nifti.zip

Jadrian Miles at 22:57, 6 March 2009

2009-03-06T22:57:17Z

← Older revision		Revision as of 22:57, 6 March 2009
Line 90:		Line 90:
	# Copy the binaries into the new <code>$G/src/<projectname></code> directory, add each one with <code>cvs add -kb <filename></code>, and then commit.		# Copy the binaries into the new <code>$G/src/<projectname></code> directory, add each one with <code>cvs add -kb <filename></code>, and then commit.

	~~[[Category:HOWTO]]~~[[Category:$G]][[Category:Software Development]]		[[Category:$G HOWTO]][[Category:Software Development]]

Jadrian Miles: /* Advanced: use wget */

2009-01-16T00:59:23Z

Advanced: use wget

← Older revision		Revision as of 00:59, 16 January 2009
Line 58:		Line 58:
	</pre>		</pre>

	===Advanced: use <code>wget</code>===		=== Advanced: use <code>wget</code> or <code>cvs</code> ===
	Sometimes it makes sense to have the build and install scripts just download the project directly, rather than checking an archive into our CVS. Be careful about doing this, as versions and URLs change over time.		Sometimes it makes sense to have the build and install scripts just download the project directly, rather than checking an archive into our CVS. Be careful about doing this, as versions and URLs change over time.

	Rather than download the project's <code>.zip</code> file yourself and then check that in, you can add a <code>wget</code> command to the Makefile to download it, and then unzip, build, and install it as above.		Rather than download the project's <code>.zip</code> file yourself and then check that in, you can add a <code>wget</code> command to the Makefile to download it, and then unzip, build, and install it as above.

	Here's an optional <code>download</code> target that could be appended to the Makefile above and added to the <code>all</code> step:		Here's an optional <code>download</code> target that could be appended to the Makefile above and added to the <code>all</code> step to download with <code>wget</code>:
	download:		<pre>
	rm -rf src nifti.zip		download:
	wget -rq --reject ".html" --nH --cut-dirs=2 ~~<nowiki>~~http://nifti.nimh.nih.gov/pub/dist/src/~~</nowiki>~~		rm -rf src nifti.zip
	zip -r nifti.zip src		wget -rq --reject ".html" --nH --cut-dirs=2 http://nifti.nimh.nih.gov/pub/dist/src/
	rm -rf src		zip -r nifti.zip src
			rm -rf nifti.zip
			# to build, just "cd src; ./configure; make"
			</pre>

			And here's one that works with <code>cvs</code>:
			<pre>
			download:
			rm -rf xmedcon
			cvs -z3 -d:pserver:anonymous@xmedcon.cvs.sourceforge.net:/cvsroot/xmedcon co -P xmedcon
			# to build, just "cd xmedcon; ./configure; make"
			</pre>

	==Install binary files directly==		==Install binary files directly==

Jadrian Miles at 13:48, 24 September 2008

2008-09-24T13:48:49Z

← Older revision		Revision as of 13:48, 24 September 2008
Line 79:		Line 79:
	# Copy the binaries into the new <code>$G/src/<projectname></code> directory, add each one with <code>cvs add -kb <filename></code>, and then commit.		# Copy the binaries into the new <code>$G/src/<projectname></code> directory, add each one with <code>cvs add -kb <filename></code>, and then commit.

	[[Category:HOWTO]]		[[Category:HOWTO]][[Category:$G]][[Category:Software Development]]

Jadrian Miles: /* Install a complicated source tree */

2008-07-23T05:41:33Z

Install a complicated source tree

← Older revision		Revision as of 05:41, 23 July 2008
Line 56:		Line 56:
	mkdir -p $(G)/shared/man/nifti		mkdir -p $(G)/shared/man/nifti
	cd src/docs/html; cp -f .html .png .css .gif $G/shared/man/nifti		cd src/docs/html; cp -f .html .png .css .gif $G/shared/man/nifti
			</pre>

	===Advanced: use <code>wget</code>===		===Advanced: use <code>wget</code>===

Jadrian Miles: /* Install a simple source tree */

2008-07-23T05:41:18Z

Install a simple source tree

← Older revision		Revision as of 05:41, 23 July 2008
Line 18:		Line 18:
	cd src; make all		cd src; make all

	install: ~~all~~		install:
	cd src; make doc		cd src; make doc
	# we have to do some gymnastics to avoid copying the CVS directory		# we have to do some gymnastics to avoid copying the CVS directory

Jadrian Miles: /* Install a complicated source tree */

2008-07-23T05:41:10Z

Install a complicated source tree

← Older revision		Revision as of 05:41, 23 July 2008
Line 40:		Line 40:

	Here's another Makefile for the NIFTI library, but this time extracting the source code on the fly:		Here's another Makefile for the NIFTI library, but this time extracting the source code on the fly:
	all:		<pre>
	unzip -ou nifti.zip		all:
	# nifti.zip has a root directory called "src"		unzip -ou nifti.zip
	cd src; make all		# nifti.zip has a root directory called "src"
			cd src; make all
	install: ~~all~~
	cd src; make doc		install:
	cp src/bin/* $(G)/~~bin~~		cd src; make doc
	cp -rf src/lib $(G)/lib/nifti		# we have to do some gymnastics to avoid copying the CVS directory
	cp -rf src/include $(G)/include/nifti		find src/bin -maxdepth 1 -type f -print0 \| xargs -0 -I '{}' cp '{}' $(G)/bin
	cp -rf src/docs/html $G/shared/man/nifti		mkdir -p $(G)/lib/nifti
			cp -f src/lib/*.a $(G)/lib/nifti
			mkdir -p $(G)/include/nifti
			cp -f src/include/*.h $(G)/include/nifti
			mkdir -p $(G)/shared/man/nifti
			cd src/docs/html; cp -f .html .png .css .gif $G/shared/man/nifti

	===Advanced: use <code>wget</code>===		===Advanced: use <code>wget</code>===

Jadrian Miles: /* Install a simple source tree */

2008-07-23T05:40:30Z

Install a simple source tree

← Older revision		Revision as of 05:40, 23 July 2008
Line 12:		Line 12:

	Here's an example Makefile for the NIFTI medical image format library:		Here's an example Makefile for the NIFTI medical image format library:
	all:		<pre>
	# NIFTI lib source code is one directory down		all:
	# to preserve the Makefile that comes with it		# NIFTI lib source code is one directory down
	cd src; make all		# to preserve the Makefile that comes with it
			cd src; make all
	install: all
	cd src; make doc		install: all
	cp src/bin/* $(G)/~~bin~~		cd src; make doc
	cp -rf src/lib $(G)/lib/nifti		# we have to do some gymnastics to avoid copying the CVS directory
	cp -rf src/include $(G)/include/nifti		find src/bin -maxdepth 1 -type f -print0 \| xargs -0 -I '{}' cp '{}' $(G)/bin
	cp -rf src/docs/html $G/shared/man/nifti		mkdir -p $(G)/lib/nifti
			cp -f src/lib/*.a $(G)/lib/nifti
			mkdir -p $(G)/include/nifti
			cp -f src/include/*.h $(G)/include/nifti
			mkdir -p $(G)/shared/man/nifti
			cd src/docs/html; cp -f .html .png .css .gif $G/shared/man/nifti
			</pre>

	==Install a complicated source tree==		==Install a complicated source tree==

Jadrian Miles at 00:34, 23 July 2008

2008-07-23T00:34:11Z

← Older revision		Revision as of 00:34, 23 July 2008
Line 5:		Line 5:
	==Install a simple source tree==		==Install a simple source tree==
	In this case, installing a 3rd-party project is identical to checking in and installing one you wrote yourself.		In this case, installing a 3rd-party project is identical to checking in and installing one you wrote yourself.
	# Create a new directory for the project (''not'' in <code>$G</code> but somewhere in your homedir) and copy the source tree into a subdirectory of this. Remember to make sure the tree is clean; no object files or other binaries.		# Create a new directory for the project (''not'' in <code>$G</code> but somewhere in your homedir) and copy the source tree into a subdirectory of this, say <code>src</code>. Remember to make sure the tree is clean; no object files or other binaries.
			# Create a Makefile in ''your'' directory (not the <code>src</code> directory that contains the project's source tree) and give it some rules:
			#* The <code>all</code> target should simply call the source's own Makefile.
			#* The <code>install</code> target should copy the resulting executables, headers, libraries, and documentation into <code>$G/bin</code>, <code>$G/include</code>, <code>$G/lib</code>, and <code>$G/man</code> respectively.
	# [[Put your code into CVS in $G\|Import the project into CVS as normal]].		# [[Put your code into CVS in $G\|Import the project into CVS as normal]].
	~~# You need to provide a Makefile for building and installing the project. There are two options:~~
	## Modify the Makefile that came with the project so that <code>make all</code> builds the project locally and <code>make install</code> puts executables into <code>$G/bin</code>, headers into <code>$G/include</code>, libraries into <code>$G/lib</code>, and documentation into <code>$G/man</code>.
	~~## Create your own Makefile~~
	~~# Check in and commit your changes to the Makefile, and you're done!~~

	Here's an example Makefile for the NIFTI medical image format library:		Here's an example Makefile for the NIFTI medical image format library:

Jadrian Miles: /* Install a simple source tree */

2008-07-23T00:30:16Z

Install a simple source tree

← Older revision		Revision as of 00:30, 23 July 2008
Line 5:		Line 5:
	==Install a simple source tree==		==Install a simple source tree==
	In this case, installing a 3rd-party project is identical to checking in and installing one you wrote yourself.		In this case, installing a 3rd-party project is identical to checking in and installing one you wrote yourself.
	# ~~Copy~~ the ~~source tree into any directory of your choice~~ (''not'' in <code>$G</code> but somewhere in your homedir). Remember to make sure the tree is clean; no object files or other binaries.		# Create a new directory for the project (''not'' in <code>$G</code> but somewhere in your homedir) and copy the source tree into a subdirectory of this. Remember to make sure the tree is clean; no object files or other binaries.
	# [[Put your code into CVS in $G\|Import the project into CVS as normal]].		# [[Put your code into CVS in $G\|Import the project into CVS as normal]].
	# Modify the Makefile that came with the project so that <code>make all</code> builds the project locally and <code>make install</code> puts executables into <code>$G/bin</code>, headers into <code>$G/include</code>, libraries into <code>$G/lib</code>, and documentation into <code>$G/man</code>.		# You need to provide a Makefile for building and installing the project. There are two options:
			## Modify the Makefile that came with the project so that <code>make all</code> builds the project locally and <code>make install</code> puts executables into <code>$G/bin</code>, headers into <code>$G/include</code>, libraries into <code>$G/lib</code>, and documentation into <code>$G/man</code>.
			## Create your own Makefile
	# Check in and commit your changes to the Makefile, and you're done!		# Check in and commit your changes to the Makefile, and you're done!

	Here's an example Makefile for the NIFTI medical image format library:		Here's an example Makefile for the NIFTI medical image format library:
	all:		all:
			# NIFTI lib source code is one directory down
			# to preserve the Makefile that comes with it
	cd src; make all		cd src; make all