[distcc] Re: Distccd port

[William]

Yet another update to this topic:
I successful sent a distcc job to my windows machine, had it compiled, 
and then linked it at the Gentoo based system. No problems occured in 
sending, no compile errors, no linking errors, test program ran without 
problem, and Digin log file reported everything as it should have.

I used a cross-compile enabled gcc that was built under cygwin, which 
works fine as long as you have cygwin1.dll.

I'm going to preform the clean-up of the code, adding extras(like temp 
file cleanup), and then I'll do a big test by trying to emerge something 
on my Gentoo system using DiGin on my Windows host.

I hope this project interests others, I know it'll help me though.

~William

William wrote:
>     Well, I'd like to give a small update to this. I slaved away and 
> finally got a working port down. It can recieve the preprocessed file, 
> compile it, and send it back, all in working order. A bit of the inwards 
> of distcc were changed. I built it from scratch in a sense, starting 
> with the main thing and only adding on and porting functions as needed, 
> so for now it is a bit dodgy, but I'll clean things up later. I've also 
> kept everything in their proper C files, so upgrading the port when the 
> original changes should be easier.
> 
> I have to tackle the problem of cross-compiling now and have yet to find 
> proper documentation.
> 
> BTW, I've dubbed the port DiGin(DIstibuted Gcc for WIndows). Not too 
> shaby of a name, methinks.
> 
> If anyone would be willing to help out in anyway, such as getting the 
> cross-compiling down, that would be appreciated. I hope I can get all my 
> Windows systems helping out with compiles soon!
> 
> 
> William wrote:
> 
>> I have decided that I would like to take on the task of porting the 
>> distcc daemon system to windows so that I, and possibly others, can 
>> take advantage of windows systems on our network.
>>
>> The current method of doing so just kinda...is poor. That method 
>> includes either cygwin usage, or VMWare usage. Both cause a loss of 
>> computer power, and I, personally, just couldn't get cygwin to work 
>> period.
>>
>> Now, I know the crosscompiling will be...weird, but I'll try anyway, 
>> wont be any worse than cygwin methinks.
>>
>> I need a slight bit of information though, if anyone would be willing. 
>> I'm reading through the source code right now, but it would be helpful 
>> if someone can tell me the exact steps that are taken by both distcc 
>> and the daemon. Knowing this I can better grok the source code, and in 
>> fact speed up the process of building a basic distcc daemon with which 
>> I can begin testing and building upon.
>>
>> So if anyone can provide me with this information, that would be 
>> greatly appreciated.
>>
>> Thank you.
>>
>> ~Billybob
>>
>>
>> __ distcc mailing list            http://distcc.samba.org/
>> To unsubscribe or change options: 
>> http://lists.samba.org/mailman/listinfo/distcc
>>
> 
> 
> __ distcc mailing list            http://distcc.samba.org/
> To unsubscribe or change options: 
> http://lists.samba.org/mailman/listinfo/distcc
>