At my previous company, we patched it to understand dcc (Diab Complier) & das (Diab assembler) for 68k & Power arch - it was a little complicated as we were constantly checking arg 0 as to how the args should be processed, but it did work and was still compatible with gcc.
In retrospect, I think the approach that we could have taken for a submitable patch would have been to modify distcc to have a structure array for each compiler supported where the structure has the compiler executable name to key off of and put that instance in that mode, and have the code for argument handling specific to the compiler be function pointers within the structure. This would have given much more flexibility, and made it easier to add any c or assembler to the code base, but it would have been a radical change to the code base, and I feared not excepted as a patch making it difficult for us to pull updates later. -Jim On Jan 31, 2012, at 10:07 PM, Martin Pool <[email protected]> wrote: > On 14 December 2011 14:08, Wang, Zhou (NSN - CN/Hangzhou) > <[email protected]> wrote: >> >> Hi, >> >> We started a new project,and we want to use Distcc to do distributed >> compilation,but our official compiler is not GCC(it's TI's compiler),so we >> want to use another compiler instead of GCC. >> >> Could you tell me how to do that? >> >> Thanks! > > Hi, > > I apologize for the delay. Your mail was accidentally stuck in the spam > queue. > > I think it will need changes to distcc to understand the TI compiler > command line options. People have talked about doing this in the past > but I don't think anyone has actually sent a patch. > > -- > Martin > __ > distcc mailing list http://distcc.samba.org/ > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/distcc __ distcc mailing list http://distcc.samba.org/ To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/distcc
