Re: Informix running on Linux

Alan Denney said >Pish-tosh. The actual *build* takes only a small fraction of the overall >time -- it's the *testing* and certification (and, in some cases, media >manufacture or install packaging) that takes the vast majority of the time. Ah. I've always treated porting, QA and distribution as separate but related stages. Besides, post-development QA must be expensive but port validation can be largely automated. >You *do* want the product TESTED, don't you? These days I don't expect it :-). >> His one beef was that Informix couldn't or wouldn't provide >>development tools under Linux. Thus he was moving away from *Informix*. > >I don't understand -- I thought you just said the SCO products ran fine >under Linux... what is different about the development tools? Informix comes with libraries which were compiled against SCO libraries. Since standards define APIs which may be implemented in header file macros as well as library functions you have to link against the libraries you compiled against. Thus once you have objects built against the SCO libraries you have to build the rest against SCO libraries - and use the SCO header files. Which means a SCO dev sys. You can host a SCO dev sys on Linux - I've gradually merged systems to the point where I have native Linux with SCO 3.2v4, SCO OS5, Unixware and Wyse V/386 hosted - but most people don't want to be buggered about like that. If they want to do development on Linux as well, they generally don't do Informix. Mike -- .----------------------------------------------------------------------. | Mike Jagdis | Internet: mailto:mike@roan.co.uk | | Roan Technology Ltd. | | | 54A Peach Street, Wokingham | Telephone: +44 118 989 0403 |