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 3D38F7EE78 for ; Tue, 26 Apr 2016 14:34:47 +0200 (CEST) IronPort-PHdr: 9a23:SowQVhTYuos3rzFFjrgurX8ajtpsv+yvbD5Q0YIujvd0So/mwa64YhaN2/xhgRfzUJnB7Loc0qyN4/CmBj1LvcrJmUtBWaIPfidNsd8RkQ0kDZzNImzAB9muURYHGt9fXkRu5XCxPBsdMs//Y1rPvi/6tmZKSV3BPAZ4bt74BpTVx5zukbviq9uMMk4U2HKUWvBbElaflU3prM4YgI9veO4a6yDihT92QdlQ3n5iPlmJnhzxtY+a9Z9n9DlM6bp6r5YTGfayQ6NtRrVdCHw7KG0v/4W/vhDGSU6L52AAemQQiBtBRQbfukLURJD05wD6rOtmxC6CPfrW0785Q3z25KdxSQT0jz8HcT4+/W7akORskedRrQilpho5z4OCM9LdD+Z3Yq6IJYBSfmFGRMsEDyE= Authentication-Results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=christoph.hoeger@tu-berlin.de; spf=None smtp.mailfrom=christoph.hoeger@tu-berlin.de; spf=None smtp.helo=postmaster@mail.tu-berlin.de Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of christoph.hoeger@tu-berlin.de) identity=pra; client-ip=130.149.7.33; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="christoph.hoeger@tu-berlin.de"; x-sender="christoph.hoeger@tu-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of christoph.hoeger@tu-berlin.de) identity=mailfrom; client-ip=130.149.7.33; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="christoph.hoeger@tu-berlin.de"; x-sender="christoph.hoeger@tu-berlin.de"; x-conformance=sidf_compatible Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail.tu-berlin.de) identity=helo; client-ip=130.149.7.33; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="christoph.hoeger@tu-berlin.de"; x-sender="postmaster@mail.tu-berlin.de"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CpAABZXx9XkCEHlYJehQinRJApgh2BdIdKOhIBAQEBAQEBAREBAQEBCQsJCSEvgi2CPg8BRTYCBRYLAgsDAgECAUsNBgIBAYgmBKJdj12RanyRL4JWBZgQiHOOWoVbjzAnCYFoAQtUgVdqiQABAQE X-IPAS-Result: A0CpAABZXx9XkCEHlYJehQinRJApgh2BdIdKOhIBAQEBAQEBAREBAQEBCQsJCSEvgi2CPg8BRTYCBRYLAgsDAgECAUsNBgIBAYgmBKJdj12RanyRL4JWBZgQiHOOWoVbjzAnCYFoAQtUgVdqiQABAQE X-IronPort-AV: E=Sophos;i="5.24,536,1454972400"; d="scan'208";a="215870355" Received: from mail.tu-berlin.de ([130.149.7.33]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Apr 2016 14:34:46 +0200 X-tubIT-Incoming-IP: 91.66.50.149 Received: from ip5b423295.dynamic.kabel-deutschland.de ([91.66.50.149] helo=[192.168.178.42]) by mail.tu-berlin.de (exim-4.76/mailfrontend-5) with esmtpsa [UNKNOWN:AES128-SHA:128] for id 1av2CS-0002Lc-9G; Tue, 26 Apr 2016 14:34:45 +0200 To: caml users From: =?UTF-8?Q?Christoph_H=c3=b6ger?= Organization: =?UTF-8?Q?Technische_Universit=c3=a4t_Berlin?= Message-ID: <571F6064.9050909@tu-berlin.de> Date: Tue, 26 Apr 2016 14:34:44 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2016.4.26.122716 X-PMX-Spam: Gauge=IIIIIII, Probability=0%, Report='' Subject: [Caml-list] [OASIS help] Run an executable during build with ocamlbuild Dear all, in one of my projects, the compiler shall be used to generate a module required in order to run the integration tests. I _could_ tweak a ppx preprocessor to run that compiler by passing the correct arguments. However, oasis won't set the corresponding variable: Executable "ppx_mcl" Path: ppx_src ... Executable "mcl_tests" ... NativeOpt: -ppx ppx_src/ppx_mcl.native Ideally, I would write: NativeOpt: -ppx $ppx_mcl but that gives: Failure: No variable ppx_mcl defined when trying to expand "${ppx_mcl}" Why is that? So another idea is to directly create ocamlbuild rules. I have these rules in another project where they work fine. But there they assume that the compiler is in PATH. This is clearly not the case in the test environment, so how do I access the path of an oasis executable during the build? thanks, Christoph -- Christoph Höger Technische Universität Berlin Fakultät IV - Elektrotechnik und Informatik Übersetzerbau und Programmiersprachen Sekr. TEL12-2, Ernst-Reuter-Platz 7, 10587 Berlin Tel.: +49 (30) 314-24890 E-Mail: christoph.hoeger@tu-berlin.de