[hoc-cvs] [hoc] r396 committed - update documentation on the subject of building HOC

[<cod...@go...>]

Revision: 396
Author: wol...@gm...
Date: Tue Aug 11 13:37:27 2009
Log: update documentation on the subject of building HOC

http://code.google.com/p/hoc/source/detail?r=396

Deleted:
  /trunk/hoc/BUILDING.CVS
Modified:
  /trunk/hoc/README.txt

=======================================
--- /trunk/hoc/BUILDING.CVS	Wed May 19 19:17:05 2004
+++ /dev/null
@@ -1,34 +0,0 @@
-CVS BUILDING INSTRUCTIONS
-=========================
-
-These are build instructions if you've checked out HOC from CVS
-(instead of downloading a source distribution tarball).
-
-1. Check out the libffi module from HOC's CVS repository into
-   a directory named libffi-src/ in the HOC source tree:
-
-   cvs -d :pserver:ano...@cv...:/cvsroot/hoc co -d libffi-src  
libffi
-
-   You can also check out libffi into another directory: if you
-   do this, just make sure that
-
-2. Execute autogen.sh to generate the GNU ./configure script:
-
-   ./autogen.sh
-
-3. Build HOC as usual with ./configure && make && make install.
-
-
-cvsps
-=====
-
-While we'd love to use a more modern revision control system such as
-darcs, Subversion or GNU arch, Sourceforge "only" provides a CVS server,
-so we're using that.  For people who are used to more modern revision
-control systems and miss working with 'patchsets' instead of the disjoint
-per-file patches that CVS uses, take a look at cvsps
-<http://www.cobite.com/cvsps/>, a patchset manager for CVS.  While it
-doesn't, by any means, give you the many advantages that more modern
-source control systems offer you, it certainly makes using CVS and
-managing patches far easier!
-
=======================================
--- /trunk/hoc/README.txt	Thu Mar 31 07:35:23 2005
+++ /trunk/hoc/README.txt	Tue Aug 11 13:37:27 2009
@@ -22,9 +22,9 @@
  You can use HOC to write full-blown GUI applications using Mac OS X's
  advanced Cocoa framework.

-For more information on HOC, see its homepage, at:
-
-    http://hoc.sourceforge.net/
+For more information on HOC, see its google code project page, at:
+
+    http://code.google.com/p/hoc


  Building HOC
@@ -35,35 +35,38 @@
  target platforms (Mac OS X 10.2, 10.3, or various Linux & GNUstep
  platforms).  You'll thus have to build HOC from source code.

-(Note: If you have checked out HOC from CVS, see the BUILDING.CVS file for
-build instructions instead of this.)
-
-HOC uses GNU autoconf for its build system, so building HOC should be
-a simple matter of the standard autoconf build mantra:
-
-  ./configure
-  make
-  make install
-
-If you have a problem building HOC, please check the "Requirements"
-section in the docs/HOC.html file to make sure that you have all the Good
-Stuff required for HOC to build properly.  If you've got everything you
-need and HOC still doesn't work, this is a _bug_ -- please see the support
-page at http://hoc.sourceforge.net/support.html, and contact one of the
-HOC developers to help you out.  Chances are that a few other people have
-run into the same problems as you!
-
-HOC should automatically locate where GHC is on your system, but if you
-want to specify what command it should use to run GHC, HOC's ./configure
-script takes a few extra flags you'll be interested in:
-
-  --with-ghc=...          command to run ghc (e.g. $HOME/bin/ghc-6.4)
-  --with-ghc-pkg=...      command to run ghc-pkg (e.g.  
$HOME/bin/ghc-pkg-6.4)
-
-Note that HOC will install itself to GHC's library directory (which you
-can find out yourself with `ghc --print-libdir`), so you'll need the
-appropriate permissions to write to there during the 'make install'.
-
+1. Build the HOC library and the interface generator:
+
+  cabal configure
+  cabal build
+  cabal install
+
+To run the unit tests, use:
+
+  cabal configure -fTests
+  cabal build
+  ./dist/build/hoc-test/hoc-test
+  cabal install
+
+2. Create the bindings:
+
+  cd Bindings
+  sh make-bindings-macos.sh
+  cd ..
+
+3. Build the hoc-wrap tool:
+
+  cd Tools
+  cabal configure
+  cabal build
+  cabal install
+  cd ..
+
+
+Depending on your setup, you will need to add "sudo" in front of the
+"cabal install" commands and in front of the make-bindings command.
+You can also add additional Cabal configure options after "cabal configure"
+and after "sh make-bindings-macos.sh".

  Authors
  =======