From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id C551C7FD03 for ; Tue, 21 Apr 2015 23:36:38 +0200 (CEST) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of rich@annexia.org) identity=pra; client-ip=80.68.91.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="rich@annexia.org"; x-sender="rich@annexia.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of rich@annexia.org designates 80.68.91.176 as permitted sender) identity=mailfrom; client-ip=80.68.91.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="rich@annexia.org"; x-sender="rich@annexia.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@furbychan.cocan.org) identity=helo; client-ip=80.68.91.176; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="rich@annexia.org"; x-sender="postmaster@furbychan.cocan.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BIIQCUwjZV/7BbRFBbgwxSXAGCSbFlBQEBAQEBAQUBgQKSM4YEAoFBOxEBAQEBAQEBfUEBAgKDWwEBBDo/EAsOCgkTEg8FKCGIQgEIzAgBAQEBAQUBAQEBHoYWOYRohQQHgxeBFgWPE4IghAGGJ5UuIoI3gT09MoJDAQEB X-IPAS-Result: A0BIIQCUwjZV/7BbRFBbgwxSXAGCSbFlBQEBAQEBAQUBgQKSM4YEAoFBOxEBAQEBAQEBfUEBAgKDWwEBBDo/EAsOCgkTEg8FKCGIQgEIzAgBAQEBAQUBAQEBHoYWOYRohQQHgxeBFgWPE4IghAGGJ5UuIoI3gT09MoJDAQEB X-IronPort-AV: E=Sophos;i="5.11,618,1422918000"; d="scan'208";a="136118602" Received: from furbychan.cocan.org ([80.68.91.176]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 21 Apr 2015 23:36:38 +0200 Received: from rich by furbychan.cocan.org with local (Exim 4.80) (envelope-from ) id 1YkfqO-0003ey-I0; Tue, 21 Apr 2015 22:36:36 +0100 Date: Tue, 21 Apr 2015 22:36:36 +0100 From: "Richard W.M. Jones" To: Malcolm Matalka Cc: caml-list@inria.fr Message-ID: <20150421213636.GA5589@annexia.org> References: <877ftfoudd.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <877ftfoudd.fsf@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [Caml-list] Suggested way to determine platform specific capabilities in build system? On Tue, Apr 14, 2015 at 10:51:42AM +0000, Malcolm Matalka wrote: > Hello, > > What is the current suggested way to determine what, roughly, autoconf > would do for you? I have some platform specific functionality to be > included (or excluded) depending on the OS. Is there a reason not to use autoconf? I use it all the time with OCaml projects, eg: https://github.com/libguestfs/libguestfs https://github.com/libguestfs/supermin and a random more recent example: http://git.annexia.org/?p=mclu.git;a=tree There are ocaml.m4 macros on ocamlforge. Rich. -- Richard Jones Red Hat