[Coco] can't compile Toolshed on CygWin

[Aaron Wolfe]

If we're still talking about cygwin (sorry I haven't paid great attention
here) then I don't think cocofuse is going to work anyway, fuse is a Linux
thing AFAIK.

For what it's worth, building the toolshed for use on regular Windows (not
in cygwin, just regular win32 exes) is very easy using MingW.  However,
don't use the "win32" build as apparently win32 really means "cygwin".
 Instead just use the unix build directory.. type 'make' and MingW will
build the toolshed just fine.
You will get an error about cocofuse, since there is no fuse in Windows,
but that is no problem and won't prevent the other binaries from building.

-Aaron


On Thu, Apr 4, 2013 at 6:08 PM, Bob Devries <devries.bob at gmail.com> wrote:

> When i do "make install" (on Toolshed-code) I get an error for cocofuse,
> telling me that fuse.h is missing.
>
>
> Regards, Bob Devries
> Dalby, QLD, Australia
>
> ----- Original Message ----- From: "Luis Antoniosi (CoCoDemus)" <
> retrocanada76 at gmail.com>
> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
> Sent: Friday, April 05, 2013 7:51 AM
>
> Subject: Re: [Coco] can't compile Toolshed on CygWin
>
>
>  don't forget the:
>>
>> make install
>>
>> to copy all binaries into the /bin
>>
>> for nitros9 you will need also lwtools:
>>
>> http://lwtools.projects.l-w.**ca/ <http://lwtools.projects.l-w.ca/>
>>
>> save the http://lwtools.projects.l-w.**ca/releases/lwtools/lwtools-4.**
>> 7.tar.gzinto<http://lwtools.projects.l-w.ca/releases/lwtools/lwtools-4.7.tar.gzinto>
>> the /usr/src for example
>>
>> cd /usr/src
>> tar xvf lwtools-4.7.tar.gz
>> cd lwtools-4.7
>> make
>> make install
>>
>> cd /usr/src
>> hg clone http://nitros9.hg.sourceforge.**net:8000/hgroot/nitros9/**
>> nitros9nitros9<http://nitros9.hg.sourceforge.net:8000/hgroot/nitros9/nitros9nitros9>
>> cd nitros9
>> hg update -r lwtools-port
>> export NITROS9DIR=/usr/src/nitros9
>> make
>> make dsk
>>
>> have fun
>>
>> to create your own distros is very simple just go to the
>> nitros9/level1/makefile or level2/makefile and change the correct
>> descriptors and format options. I made a superIDE 180K distro for me in
>> this way.
>>
>>
>>
>> On Thu, Apr 4, 2013 at 5:34 PM, Bob Devries <devries.bob at gmail.com>
>> wrote:
>>
>>  Thanks, Luis.
>>>
>>> I followed your example, and Toolshed compiled ok.
>>>
>>> Do you have a similar example for the NitrOS9 code?
>>>
>>> Thanks for your help. I hope someone changes the website instructions!
>>>
>>> Regards, Bob Devries
>>> Dalby, QLD, Australia
>>>
>>> ----- Original Message ----- From: "Luis Antoniosi (CoCoDemus)" <
>>> retrocanada76 at gmail.com>
>>> To: "CoCoList for Color Computer Enthusiasts" <coco at maltedmedia.com>
>>> Sent: Thursday, April 04, 2013 11:45 PM
>>> Subject: Re: [Coco] can't compile Toolshed on CygWin
>>>
>>>
>>>  erh CVS ? You mean mercurial right ? Are you taking this one ?
>>>
>>>>
>>>> hg clone http://hg.code.sf.net/p/****toolshed/code<http://hg.code.sf.net/p/**toolshed/code>
>>>> <http://hg.code.**sf.net/p/toolshed/code<http://hg.code.sf.net/p/toolshed/code>
>>>> >**toolshed-code
>>>>
>>>> then you do:
>>>>
>>>> cd build/win32
>>>> make
>>>>
>>>> If you get errors is because you're using gcc4 instead of 3. Change int
>>>> the
>>>> build\win32\Makefile this line to:
>>>>
>>>> export CC=gcc-3
>>>>
>>>> And be happy. I just rebuild a fresh check-out.
>>>>
>>>> Luis Felipe.
>>>>
>>>>
>>>>
>>>> On Thu, Apr 4, 2013 at 12:00 AM, David Ladd <drencor at gamepixel.net>
>>>> wrote:
>>>>
>>>>  Bob,
>>>>
>>>>>
>>>>> At this point I did try to build toolshed inside cygwin and it did fail
>>>>> for
>>>>> me as well.  Though I have systems I use linux natively on.  If you do
>>>>> have
>>>>> a spare system that has linux on it I would go that route.  If not
>>>>> then I
>>>>> might try using VirtualBox with a linux install in a vBox session.
>>>>>
>>>>> There are others that might may have found a workaround for this on
>>>>> CygWin
>>>>> and might chime in on this.
>>>>>
>>>>> I myself would just go a full linux system myself as I have had other
>>>>> source packages not want to compile under cygwin in the past.  So
>>>>> rather
>>>>> than fight a mule I just replaced the mule with a race horse so to
>>>>> speak
>>>>> :P
>>>>> :D
>>>>>
>>>>> --
>>>>> Coco mailing list
>>>>> Coco at maltedmedia.com
>>>>> http://five.pairlist.net/****mailman/listinfo/coco<http://five.pairlist.net/**mailman/listinfo/coco>
>>>>> <http://**five.pairlist.net/mailman/**listinfo/coco<http://five.pairlist.net/mailman/listinfo/coco>
>>>>> >
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Long live the CoCo
>>>>
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/****mailman/listinfo/coco<http://five.pairlist.net/**mailman/listinfo/coco>
>>>> <http://**five.pairlist.net/mailman/**listinfo/coco<http://five.pairlist.net/mailman/listinfo/coco>
>>>> >
>>>>
>>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> http://five.pairlist.net/****mailman/listinfo/coco<http://five.pairlist.net/**mailman/listinfo/coco>
>>> <http://**five.pairlist.net/mailman/**listinfo/coco<http://five.pairlist.net/mailman/listinfo/coco>
>>> >
>>>
>>>
>>
>>
>> --
>> Long live the CoCo
>>
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/**mailman/listinfo/coco<http://five.pairlist.net/mailman/listinfo/coco>
>>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/**mailman/listinfo/coco<http://five.pairlist.net/mailman/listinfo/coco>
>