Auto-tools & Win32 & Borland C++ Builder

[Axel Thimm]

sorry for the excessive addressing, but this topic touches all auto-tools.

I am in the process of convincing some people to move their Borland based
source code development to proprietary free models. As you may guess, this is
an extremly difficult task, requiring more pedagogical than technical skills
(and unfortunately myself is extremly Unix-centric, and I still have to learn
about Borland's peculiarities).

Nevertheless I want to give it a try. As a first step I'd have to move the
configure/build/install infrastructure to auto-tools, then I'd attack the
compiler non-portability (and by the end of this decade I might get a GNU
compilant system ...). 

Searching the lists/net nothing helpful came up, but at least there also
wasn't any evidence of any NoGo-theorems.

Does anyone have already some experience in working with auto-tools and
Borland from the command line? How do the maintainers/release managers here
think about it? Would they be willing to accept patches for supporting
commercial compilers ;)

Regards, Axel.
-- 
address@hidden