Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.albasani.net!.POSTED!not-for-mail From: BGB Newsgroups: comp.lang.java.programmer Subject: Re: =?UTF-8?B?QW5kcm9pZOKAlFdoeSBEYWx2aWs/?= Date: Tue, 31 May 2011 15:01:27 -0700 Organization: albasani.net Lines: 37 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: news.albasani.net df4r1PtJgTHdQbkT0IBEUJpt4n7XbrnJzKsrSXrcgxBO6ZILEuiJpyKmvYVCSs37DA2qddYR4qrfRfIMswFNcagtD7taAivAkW2zwcfk8SOMFaZKMXeAdbol6Scv0hpu NNTP-Posting-Date: Tue, 31 May 2011 22:04:29 +0000 (UTC) Injection-Info: news.albasani.net; logging-data="/SCgTVidRa+FNpSrRbzCAZmapazuuqn71x35pNuDenKIIVKVjxFocxJpjpFpglBXBDuPi/M5ba7MnDFyXoyjx0qyfkfAdITTGLYVjYBLoAeriDVgFXwHI0rOt9b8y4A6"; mail-complaints-to="abuse@albasani.net" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 In-Reply-To: Cancel-Lock: sha1:BwPuvv7N4e4URQZniouf1acNEvQ= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4825 On 5/31/2011 12:59 PM, Lawrence D'Oliveiro wrote: > In message, BGB wrote: > >> [autoconf] doesn't exactly tend to work well for non-Linux operating >> systems (such as Windows...). > > It works just fine on a whole load of non-Linux operating systems, on a > whole range of hardware platforms. Among modern OSes, Windows is really the > only one left out. I had also heard before that it tended not to work very well on OSX either, if anything, because many projects which use autoconf tend to also demand GTK, which from I heard doesn't tend to always work on OSX either. I had also heard about a lot of this not working so well for iOS either. granted though, I have no real personal experience trying to build stuff on OSX (or other Apple OS's), so I can't really verify a lot of this. but, my experience is mostly with Windows, where autoconf/configure tends not to even work much of the time with "blessed" environments, such as Cygwin and MinGW. also, it is another problem if one tends to use MSVC and needs to build with MSVC to use the library in a project compiled with MSVC. then one ends up using a custom makefile, and may observe that even "portable everywhere" / "pure ANSI C" code is still prone to contain the occasional GCC-specific extension here and there, or do other things which are prone to misbehave or blow up when building with MSVC (sharing 'FILE*' handles or malloc'ed memory between separately-compiled libraries, for example, ...). or such...