diff options
| author | sanine <sanine.not@pm.me> | 2022-10-01 20:59:36 -0500 |
|---|---|---|
| committer | sanine <sanine.not@pm.me> | 2022-10-01 20:59:36 -0500 |
| commit | c5fc66ee58f2c60f2d226868bb1cf5b91badaf53 (patch) | |
| tree | 277dd280daf10bf77013236b8edfa5f88708c7e0 /libs/ode-0.16.1/tools/README.txt | |
| parent | 1cf9cc3408af7008451f9133fb95af66a9697d15 (diff) | |
add ode
Diffstat (limited to 'libs/ode-0.16.1/tools/README.txt')
| -rw-r--r-- | libs/ode-0.16.1/tools/README.txt | 94 |
1 files changed, 94 insertions, 0 deletions
diff --git a/libs/ode-0.16.1/tools/README.txt b/libs/ode-0.16.1/tools/README.txt new file mode 100644 index 0000000..56019df --- /dev/null +++ b/libs/ode-0.16.1/tools/README.txt @@ -0,0 +1,94 @@ +HOW TO MAKE A RELEASE
+
+Originally by Jason Perkins (starkos@industriousone.com)
+
+
+PREREQUISITES
+
+In order to build an OpenDE release you'll need:
+
+* A Windows system
+* A Posix-like system (Linux, Mac OS X, Cygwin)
+* Visual Studio 2003 or later (for C++ release)
+* Visual Studio 2005 or later (for .NET release)
+* Subversion (command line version)
+* 7zip (command line version)
+* Doxygen
+
+All command line binaries (svn, 7z, doxygen) must be available on
+the system search path.
+
+
+
+INSTRUCTIONS
+
+* Update the version numbers in configure.in
+
+ AC_INIT(ODE,0.9.0-rc1,ode@ode.org)
+ ODE_CURRENT=0
+ ODE_REVISION=9
+ ODE_AGE=0-rc1
+
+
+* Create a release branch in Subversion. Using TortoiseSVN:
+
+ Update working copy
+ Right-click working copy folder and choose Branch/Tag
+ To https://opende.svn.sourceforge.net/svnroot/branches/0.9.0-rc1
+ Enter log message "Branching for 0.9.0-rc1 release"
+ OK
+
+ Using the command line:
+
+ $ cd ode
+ $ svn update
+ $ svn copy . -m "Branching for..." https://opende.... (see above)
+
+
+* Run msw-release.bat from a Visual Studio command prompt to create
+ the Windows binary package. I've used VS2003 for all releases since
+ 0.5, but am thinking about switching up to VS2005. The format of
+ this command is:
+
+ > msw-release.bat 0.9.0-rc1
+
+ The version argument supplied to the script must match the name of
+ the release branch in Subversion.
+
+
+* Run dotnet-release.bat to create the .NET bindings package. This
+ script must be run from a Visual Studio 2005 (or later) command
+ prompt. The format of the command is:
+
+ > dotnet-release.bat 0.9.0-rc1
+
+ The version argument supplied to the script must match the name of
+ the release branch in Subversion.
+
+
+* Run src-release.sh to create the source package. This script must be
+ run from a Posix-like environment in order to prepare the configure
+ script. I've tried it under Linux, Mac OS X, and Windows with Cygwin.
+
+ $ ./src-release.sh 0.9.0-rc1
+
+ The version argument supplied to the script must match the name of
+ the release branch in Subversion.
+
+
+* Visit the project site on SourceForge (http://sf.net/projects/opende)
+ and create a new file release including all of the files.
+
+
+SANITY CHECKING
+
+A few optional, but recommeded, checks to make sure that everything
+worked properly.
+
+ The binaries exist in lib/
+
+ include/ode/config.h exists
+
+ configure script exists (if not, make sure autotools is installed)
+
+ docs exist in docs/ (if not, make sure doxygen is on the path)
|