CcPublisher Prerequisites - Revision history

Nathan Yergler at 14:15, 29 June 2006

2006-06-29T14:15:12Z

← Older revision		Revision as of 14:15, 29 June 2006
Line 20:		Line 20:
	== Developing ccPublisher ==		== Developing ccPublisher ==

	Depending on your platform, your development model may vary slightly. See the appropriate platform-specific page:		Depending on your platform and toolset, your development model may vary slightly. See the appropriate tool/platform-specific page:

	* [[Developing ccPublisher with Command Line Tools]]		* [[Developing ccPublisher with Command Line Tools]]
	* [[Developing ccPublisher with Eclipse]]		* [[Developing ccPublisher with Eclipse]]
	* [[Developing ccPublisher with Wing]]		* [[Developing ccPublisher with Wing]]

Nathan Yergler: Developing ccPublisher 2 moved to CcPublisher Prerequisites

2006-06-29T14:10:52Z

Developing ccPublisher 2 moved to CcPublisher Prerequisites

← Older revision	Revision as of 14:10, 29 June 2006
(No difference)

Nathan Yergler at 14:10, 29 June 2006

2006-06-29T14:10:05Z

@@ Line 2: / Line 2: @@
 [[Category:Developer]]
-This page describes setting up a sandbox for running ccPublisher 2 and P6 from Subversion.
+This page describes the prerequisites needed to develop ccPublisher.  We try to maintain pure Python within our Subversion repository (either with a vendor tag or svn:external).  However, there are a handful of dependencies which are better built on individual systems or installed from binaries.
 * '''Python 2.4'''
@@ Line 27: / Line 17: @@
 ** ''Note:'' This is a change as of 8 February 2006 (see [[why ElementTree]] for details on the switch from libxml2)
 ** http://effbot.org/downloads/#elementtree
 == Developing ccPublisher ==
@@ Line 46: / Line 22: @@
 Depending on your platform, your development model may vary slightly.  See the appropriate platform-specific page:
 * [[Developing ccPublisher with Eclipse]]
 * [[Developing ccPublisher with Wing]]

Nathan Yergler at 14:05, 29 June 2006

2006-06-29T14:05:44Z

← Older revision		Revision as of 14:05, 29 June 2006
Line 46:		Line 46:
	Depending on your platform, your development model may vary slightly. See the appropriate platform-specific page:		Depending on your platform, your development model may vary slightly. See the appropriate platform-specific page:

	* [[Developing ccPublisher ~~on Linux]]~~		* [[Developing ccPublisher with Eclipse]]
	* [[Developing ccPublisher on Windows]]
	* [[Developing ccPublisher on Mac OS X]]
	* [[Developing ccPublisher with Wing]]		* [[Developing ccPublisher with Wing]]

Nathan Yergler at 17:51, 21 June 2006

2006-06-21T17:51:36Z

← Older revision		Revision as of 17:51, 21 June 2006
Line 49:		Line 49:
	* [[Developing ccPublisher on Windows]]		* [[Developing ccPublisher on Windows]]
	* [[Developing ccPublisher on Mac OS X]]		* [[Developing ccPublisher on Mac OS X]]
			* [[Developing ccPublisher with Wing]]

	== Distributing ccPublisher ==		== Distributing ccPublisher ==

	See [[CcPublisher Release Procedure]] for details on creating packages of ccPublisher (or other P6 applications).		See [[CcPublisher Release Procedure]] for details on creating packages of ccPublisher (or other P6 applications).

Nathan Yergler at 13:33, 21 June 2006

2006-06-21T13:33:48Z

← Older revision		Revision as of 13:33, 21 June 2006
Line 1:		Line 1:
	[[Category:CcPublisher]]		[[Category:CcPublisher]]
	[[Category:Developer]]		[[Category:Developer]]
	~~{{incomplete}}~~
	This page describes setting up a sandbox for running ccPublisher 2 and P6 from ~~CVS~~.		This page describes setting up a sandbox for running ccPublisher 2 and P6 from Subversion.

	== Setting Up a ccPublisher Sandbox ==		== Setting Up a ccPublisher Sandbox ==
Line 34:		Line 34:
	$ svn co svn://svn.berlios.de/cctools/publisher/trunk ccpublisher		$ svn co svn://svn.berlios.de/cctools/publisher/trunk ccpublisher

	This will check out the entire required source tree, including dependencies from the Zope 3 project, into the ccpublisher directory.		This will check out the entire required source tree, including dependencies from the Zope 3 project, into the <code>ccpublisher</code> directory.

	=== Running ===		=== Running ===
Line 40:		Line 40:
	Once you have the dependencies listed above installed, run <code>main.py</code> to start ccPublisher:		Once you have the dependencies listed above installed, run <code>main.py</code> to start ccPublisher:

	$ python ~~main~~.py		$ python ccp.py

			== Developing ccPublisher ==

	~~== Editting~~ the ~~Source ==~~		Depending on your platform, your development model may vary slightly. See the appropriate platform-specific page:

	~~== Submitting Your Changes ==~~		* [[Developing ccPublisher on Linux]]
			* [[Developing ccPublisher on Windows]]
			* [[Developing ccPublisher on Mac OS X]]

	== Distributing ccPublisher ==		== Distributing ccPublisher ==

	See [[CcPublisher Release Procedure]] for details on creating packages of ccPublisher (or other P6 applications).		See [[CcPublisher Release Procedure]] for details on creating packages of ccPublisher (or other P6 applications).

Nathan Yergler at 20:46, 9 May 2006

2006-05-09T20:46:17Z

← Older revision		Revision as of 20:46, 9 May 2006
Line 48:		Line 48:
	== Distributing ccPublisher ==		== Distributing ccPublisher ==

	~~This section contains basic information~~ on ~~building a distribution~~ of ccPublisher (or other P6 ~~Application~~). ~~We '''will''' have scripts for this, we just haven't found the right tool. Ideally something like Ant, but without the Java overhead. Suggestions welcome.~~		See [[CcPublisher Release Procedure]] for details on creating packages of ccPublisher (or other P6 applications).

	~~=== Prerequisites ===~~
	~~{\| border=1 width="100%"~~
	~~! Windows~~
	~~! Mac OS X~~
	~~! Linux~~
	\|-
	~~\|width=33%\|~~
	* '''py2exe''' http://www.py2exe.org/
	~~\|width=33%\|~~
	* '''py2app'''
	~~\|width=33%\|~~
	\|}

	~~=== Building ===~~

	~~=== Packaging ===~~

Nathan Yergler at 13:43, 20 February 2006

2006-02-20T13:43:39Z

← Older revision		Revision as of 13:43, 20 February 2006
Line 14:		Line 14:
	We try to maintain pure Python within our Subversion repository (either with a vendor tag or svn:external). However, there are a handful of dependencies which are better built on individual systems or installed from binaries.		We try to maintain pure Python within our Subversion repository (either with a vendor tag or svn:external). However, there are a handful of dependencies which are better built on individual systems or installed from binaries.

	* '''Python 2.4''' ~~Python 2.4 is required.~~		* '''Python 2.4'''
	** Windows: http://python.org/download/		** Windows: http://python.org/download/
	** Mac OS X: http://undefined.org/python/		** Mac OS X: http://undefined.org/python/
Line 20:		Line 20:
	* '''pywin32''' Python Extensions for the Win32 API (Windows only)		* '''pywin32''' Python Extensions for the Win32 API (Windows only)
	** http://starship.python.net/crew/mhammond/win32/Downloads.html		** http://starship.python.net/crew/mhammond/win32/Downloads.html
	* '''wxPython''' Unicode build ~~recommended~~		* '''wxPython''' Unicode build required to properly support non-ANSI characters in ''any'' input field. So really, just use the Unicode build.
	** [http://wxpython.org/download.php~~#binaries binary downloads~~]		** [http://prdownloads.sourceforge.net/wxpython/wxPython2.6-win32-unicode-2.6.2.1-py24.exe Windows]
			** [http://prdownloads.sourceforge.net/wxpython/wxPython2.6-osx-unicode-2.6.2.1-macosx10.3-py2.4.dmg Mac OS X (10.3 and later)]
			** Linux: use a distro-specific package or see [http://wxpython.org/download.php the wxPython download page] for other options
	* '''elementtree'''		* '''elementtree'''
	** ''Note:'' This is a change as of 8 February 2006 (see [[why ElementTree]] for details on the switch from libxml2)		** ''Note:'' This is a change as of 8 February 2006 (see [[why ElementTree]] for details on the switch from libxml2)

Nathan Yergler at 02:08, 9 February 2006

2006-02-09T02:08:29Z

← Older revision		Revision as of 02:08, 9 February 2006
Line 33:		Line 33:

	This will check out the entire required source tree, including dependencies from the Zope 3 project, into the ccpublisher directory.		This will check out the entire required source tree, including dependencies from the Zope 3 project, into the ccpublisher directory.

	~~=== Building ===~~

	Before you can run from source you need to build the zope.proxy C extension. The included <code>setup.py</code> will handle the actual compilation process. Assuming you checked out ccPublisher as show above, just run:

	~~$ cd ccpublisher~~
	~~$ python setup.py build~~

	This will compile the extension module, but will not install it into the standard Python path. So before you can run from within the checkout, you need to move the compiled extension to the appropriate directory. On Linux systems, the extension takes the form of a .so file, so your command will look something like:

	~~$ cp build/lib.linux-i686-2.4/zope/proxy/_zope_proxy_proxy.so zope/proxy~~

	=== Running ===		=== Running ===

	~~After~~ you~~'ve copied~~ the ~~zope.proxy extension into the appropriate location~~, run <code>main.py</code> to start ccPublisher:		Once you have the dependencies listed above installed, run <code>main.py</code> to start ccPublisher:

	$ python main.py		$ python main.py

Nathan Yergler: /* Setting Up a ccPublisher Sandbox */

2006-02-09T01:59:26Z

Setting Up a ccPublisher Sandbox

← Older revision		Revision as of 01:59, 9 February 2006
Line 8:		Line 8:
	A sandbox is a checkout of the ccPublisher sourcecode from Subversion. Setting up a sandbox lets you work with the most recent features, as well as work on the source code yourself. For background on how the sourcecode is organized see [[ccPublisher 2 Architecture]].		A sandbox is a checkout of the ccPublisher sourcecode from Subversion. Setting up a sandbox lets you work with the most recent features, as well as work on the source code yourself. For background on how the sourcecode is organized see [[ccPublisher 2 Architecture]].

	~~In order to run ccPublisher 2 from source~~, ~~you will need to first build the P6 framework. P6 includes portions of the Zope3 framework which require~~ a C compiler~~. If building on Win32 without Visual C++ 7.1, you will need~~ to ~~download and install the free [http://msdn.microsoft.com/visualc/vctoolkit2003/ Microsoft Toolkit Compiler]. Instructions for configuring Python~~ 2.~~4.1 with the Toolkit Compiler are available at http://www.vrplumber.com/programming/mstoolkit/.~~		As of 8 February 2006, a C compiler is no longer required to build ccPublisher 2 or P6.

	=== Prerequisites ===		=== Prerequisites ===