DrizzleWiki - Recent changes [en]

Compiling

LinuxJedi — Mon, 06 Sep 2010 19:31:26 GMT

←Older revision		Revision as of 19:31, 6 September 2010
Line 17:		Line 17:
	* intltool		* intltool
	* libcurl4-gnutls		* libcurl4-gnutls
-	* [https://launchpad.net/libdrizzle/ libdrizzle]
	* libevent		* libevent
	* libgtest ([http://googletest.googlecode.com/files/gtest-1.5.0.tar.gz source])		* libgtest ([http://googletest.googlecode.com/files/gtest-1.5.0.tar.gz source])
Line 31:		Line 30:

	Lenz Grimmer has created RPM packages of protobuf for Fedora, Mandriva, RHEL/CENTOS and OpenSUSE, available via [http://download.opensuse.org/repositories/home:/LenzGr/ his package repository] on the [http://build.opensuse.org/ openSUSE build service].		Lenz Grimmer has created RPM packages of protobuf for Fedora, Mandriva, RHEL/CENTOS and OpenSUSE, available via [http://download.opensuse.org/repositories/home:/LenzGr/ his package repository] on the [http://build.opensuse.org/ openSUSE build service].
		+
		+	'''Note''': as of 2010-08-20 libdrizzle is no longer a dependency, it is now part of the main drizzle package. If you have libdrizzle installed separately please remove it before trying to install an updated drizzle.

	[[Compiling/CentOS_5\|Resolving dependencies on CentOS 5]]		[[Compiling/CentOS_5\|Resolving dependencies on CentOS 5]]
Line 39:		Line 40:

	[[Compiling/Ubuntu\|Resolving dependencies on Ubuntu]]		[[Compiling/Ubuntu\|Resolving dependencies on Ubuntu]]
-
-	~~= libdrizzle =~~
-	[https://launchpad.net/libdrizzle/ libdrizzle] is the client and protocol library that is required to build Drizzle. You can either grab a tarball release from the libdrizzle project page or you can grab the latest source from Launchpad.
-
-	~~=== Source Tarball ===~~
-	~~Grab the latest from [https://launchpad.net/libdrizzle/+download the project page] and install by replacing VERSION with the version you downloaded and running:~~
-
-	~~tar xvzf libdrizzle-VERSION.tar.gz~~
-	~~cd libdrizzle-VERSION~~
-	~~./configure~~
-	~~make~~
-	~~make install~~
-
-
-	NOTE: The config/autorun.sh step is not required when using source tarballs. On some platforms this may result in issues compiling, e.g. [https://bugs.launchpad.net/drizzle/+bug/526518 Bug #526518]. Please report any issues found to help the development teams.
-
-	~~=== Launchpad ===~~
-	~~Once you have bzr installed, you first need to log into launchpad and then create a bzr repo directory (this is only needed once for all bzr related projects):~~
-
-	~~bzr launchpad-login my_lp_username~~
-
-	~~mkdir ~/bzrwork~~
-	~~bzr init-repo --2a ~/bzrwork~~
-	~~cd ~/bzrwork~~
-
-	~~And then grab the libdrizzle source code, build, and install:~~
-
-	~~bzr branch lp:libdrizzle~~
-	~~cd libdrizzle~~
-	~~./config/autorun.sh~~
-	~~./configure~~
-	~~make~~
-	~~make install~~

	= Getting the Code =		= Getting the Code =

Main Page

Kalebral — Thu, 02 Sep 2010 16:01:47 GMT

←Older revision		Revision as of 16:01, 2 September 2010
Line 46:		Line 46:
	* [[User Documentation]]		* [[User Documentation]]
	* [http://drizzle.org/doxygen/ Doxygen]		* [http://drizzle.org/doxygen/ Doxygen]
		+	* [http://www.norbye.org/source/ OpenGrok]
	* [http://drizzle.org/libdrizzle-doxygen-api/modules.html libdrizzle API docs]		* [http://drizzle.org/libdrizzle-doxygen-api/modules.html libdrizzle API docs]
	* [http://drizzle.org/libdrizzle-doxygen-dev/modules.html libdrizzle Development docs]		* [http://drizzle.org/libdrizzle-doxygen-dev/modules.html libdrizzle Development docs]
Line 51:		Line 52:
	* [[Developer Documentation\| Developer/Contributor Documentation]]		* [[Developer Documentation\| Developer/Contributor Documentation]]
	* [https://bugs.launchpad.net/drizzle Drizzle Bugs]		* [https://bugs.launchpad.net/drizzle Drizzle Bugs]
-	* [http://twitter.com/drizzlebugs Drizzle Bugs on Twitter]
	* [[Open Discussions]]		* [[Open Discussions]]
	* [https://launchpad.net/~drizzle-discuss/ Mailing List (on launchpad)]		* [https://launchpad.net/~drizzle-discuss/ Mailing List (on launchpad)]

Test-run notes

Pcrews — Tue, 31 Aug 2010 20:09:59 GMT

Writing test cases:

←Older revision		Revision as of 20:09, 31 August 2010
Line 5:		Line 5:
	=Writing test cases=		=Writing test cases=
	* [http://forge.mysql.com/w/images/4/46/HowToWriteABetterTestCase.pdf - general thoughts on test cases]		* [http://forge.mysql.com/w/images/4/46/HowToWriteABetterTestCase.pdf - general thoughts on test cases]
		+	==Shutdown / crash a server mid test==
		+	It is possible to shutdown or to crash a server mid test. This might be useful in certain cases:
		+	* [https://blueprints.launchpad.net/drizzle/+spec/remove-print-stack-trace blueprint]
		+	% ./drizzled/drizzled --plugin-add=crash_function
		+	select crash();
		+
		+	% ./drizzled/drizzled --plugin-add=shutdown_function
		+	select shutdown()
	==include files==		==include files==
	Using include files can be a very good idea. If you have a sequence of actions that will be repeated several times, it can make sense to put that test code into an include file, then to just reference this file from within the test. It can make for a cleaner, easier-to-read test.		Using include files can be a very good idea. If you have a sequence of actions that will be repeated several times, it can make sense to put that test code into an include file, then to just reference this file from within the test. It can make for a cleaner, easier-to-read test.