Re: [hoc-users] Build Release vs. CVS

[Peter T. <pet...@co...>]

Alwyn,

Directions to obtain the CVS release are given at:
http://sourceforge.net/cvs/?group_id=3D93369
Alternatively, you could go to the HOC Download page ( http://=20
hoc.sourceforge.net/download.html )
and click on the Sourceforge CVS repository link at the bottom of the =20=

page.

NOTE1: if you are new to using cvs, create a file at the top of your =20
home user directory ( ~/ ) for cvs to use as a record of its =20
activities, like this:
[shell prompt]:~ your_user_name$ touch .cvspass
do this *before* you issue the first cvs command.

Be sure to read the _BUILDING.CVS_ file (also at the bottom of the =20
HOC Download page), for directions on building the CVS file.
As of this writing, the Sourceforge web site is down, but there is a =20
copy in the top level directory ( hoc/BUILDING.CVS ) after you have =20
checked HOC out of cvs.  For convenience, here is a copy of the =20
current BUILDING.CVS file:

-----BUILDING.CVS COPY (Modified)-----
CVS BUILDING INSTRUCTIONS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=


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 =20
libffi-src libffi

--NOTE2: changed cvs.sf.net in above command to cvs.sourceforge.net

    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.
----BUILDING.CVS COPY (Modified)----

NOTE3: If you are building on Mac OS 10.4 (Tiger) with Apple's gcc 4.0:
1. once you have retrieved the CVS version, change to the directory =20
hoc/HOC_cbits
2. backup the file Makefile.in by copying it to some archive name, =20
such as Makefile.in.old
3. open the file Makefile.in (preferably in a text editor that =20
displays line numbers, such as Emacs or Xcode)
4. change line 23 (not 33)
	from:
	ld -r -x -o HOC_cbits.o $(ALL_LOAD) libHOC_cbits.a
	to:
	ld -r -x -o HOC_cbits.o -lSystemStubs $(ALL_LOAD) libHOC_cbits.a
5. save your changes
6. proceed with the build process from item 2. in BUILDING.CVS =20
(running autogen.sh).

Good luck,
Pete

On Mar 10, 2006, at 11:56 AM, David Christensen wrote:

> Alwyn,
>
>> Is this project still alive? Is there any interest in maintaining it?
>
> I can't speak as one of the developers, but I have been interested =20
> in using HOC, and am currently using it to write one of my =20
> applications.  I am still a relative newbie to haskell (just about =20
> a year of part-time hobbyist experience), and I have found that =20
> doing some of the cocoa integration starts to become a bit =20
> tedious.  I think a more active user group would be great; I think =20
> there have been only 10 messages or so to hoc-users in the last =20
> year, so it feels an awful lot like swimming alone in a dark, dark =20
> ocean. :/
>
>> My understanding is that the released version of HOC will not work =20=

>> with GHC 6.4.1, but that there is a version in CVS that may do so. =20=

>> I've been expecting a new release for months, but it hasn't been =20
>> forthcoming.
>
> The CVS version works=97poke around on hoc.sourceforge.net to find =20
> the anonymous cvs url.
>
> Regards,
>
> David Christensen
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting =20
> language
> that extends applications into web and mobile media. Attend the =20
> live webcast
> and join the prime developer group breaking into this new coding =20
> territory!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=121642=

> _______________________________________________
> hoc-users mailing list
> hoc...@li...
> https://lists.sourceforge.net/lists/listinfo/hoc-users