DevTools:CMake - Revision history

David Haslam: /* See also */ Category:SWORD

2018-01-11T14:04:10Z

2013-06-23T03:15:52Z

‎Where is the code?

2013-06-23T03:15:33Z

‎Where is the code?

2013-06-10T19:37:09Z

2013-06-10T19:36:25Z

‎How do I hack the code?: == See also ==

2012-01-12T11:08:58Z

[http://www.answers.com/topic/patch-pumpkin-computer-jargon pumpkin holder]

2011-04-08T10:31:07Z

‎Bash or other command-line tool, probably Unix/Linux environment: [http://en.wikipedia.org/wiki/Python_%28programming_language%29 python]

2011-04-08T10:29:18Z

‎Bash or other command-line tool, probably Unix/Linux environment: [http://en.wikipedia.org/wiki/Language_binding bindings]

2010-10-04T04:55:47Z

Add actual shell commands

2010-08-30T21:40:02Z

‎Developer or Packager specific options

← Older revision		Revision as of 14:04, 11 January 2018
Line 122:		Line 122:

	[[Category:Development tools\|CMake]]		[[Category:Development tools\|CMake]]
		+	[[Category:SWORD]]

@@ Line 6: / Line 6: @@
 == Where is the code? ==
-Currently the source for the CMake build system can be found in the regular SWORD SVN tree and is included with distributions starting with version 1.6.2.  Refer elsewhere for information on fetching the SWORD code by Subversion as that is beyond the scope of the present document.
+Currently the source for the CMake build system can be found in the regular SWORD SVN tree and is included with distributions starting with version 1.6.2.
 == Now what do I do with the code? ==

@@ Line 6: / Line 6: @@
 == Where is the code? ==
-Currently the source for the CMake build system can be found in the regular SWORD SVN tree and should be included with distributions starting with version 1.6.2 (unreleased at the time of this writing) and onwards.  Refer elsewhere for information on fetching the SWORD code by Subversion as that is beyond the scope of the present document.
+Currently the source for the CMake build system can be found in the regular SWORD SVN tree and is included with distributions starting with version 1.6.2.  Refer elsewhere for information on fetching the SWORD code by Subversion as that is beyond the scope of the present document.
 == Now what do I do with the code? ==

← Older revision		Revision as of 19:37, 10 June 2013
Line 119:		Line 119:

	== See also ==		== See also ==
		+	* [[DevTools:Bindings]]

	[[Category:Development tools\|CMake]]		[[Category:Development tools\|CMake]]

← Older revision		Revision as of 19:36, 10 June 2013
Line 117:		Line 117:

	After build, install is handled in the sword/cmake/install.cmake file.		After build, install is handled in the sword/cmake/install.cmake file.
		+
		+	== See also ==

	[[Category:Development tools\|CMake]]		[[Category:Development tools\|CMake]]

← Older revision		Revision as of 11:08, 12 January 2012
Line 1:		Line 1:
−	An initial, experimental, proof-of-concept version of a [http://www.cmake.org/ CMake] build system for the SWORD library is under way borrowing from the BibleTime CMake system and others. The current pumpkin holder for it is Greg Hellings.	+	An initial, experimental, proof-of-concept version of a [http://www.cmake.org/ CMake] build system for the SWORD library is under way borrowing from the BibleTime CMake system and others. The current [http://www.answers.com/topic/patch-pumpkin-computer-jargon pumpkin holder] for it is Greg Hellings.

	----		----

@@ Line 26: / Line 26: @@
 *From here on out, building should be just like building with Autotools - make -j4/sudo make install
-An example of building in a subdir, shared library, setting the prefix, and building the python [http://en.wikipedia.org/wiki/Language_binding bindings]:
+An example of building in a subdir, shared library, setting the prefix, and building the [http://en.wikipedia.org/wiki/Python_%28programming_language%29 python] [http://en.wikipedia.org/wiki/Language_binding bindings]:
 <pre>
 mkdir cmakebuild

@@ Line 25: / Line 25: @@
 *Check that there are no error messages and that CMake ends with the messages "Configuring done", "Generating done", and "Build files have been written to: <object directory>"
 *From here on out, building should be just like building with Autotools - make -j4/sudo make install
 === GUI users ===

@@ Line 84: / Line 84: @@
 ==== Developer or Packager specific options ====
 *LIBSWORD_LIBRARY_TYPE - If this has the value "Shared" then a shared library will be build (DLL or .so) along with the exported linking stub.  If this is unspecified, then a static library will be built.
 *CMAKE_BUILD_TYPE - If this is given the value of "Debug" then the default SWORD debugging flags (-g3 -Wall -Werror -O0) will be enabled.  If this is unspecified or any value other than "Debug" then the flag -O3 will be enabled.