From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id A99907EE4B for ; Sat, 5 Oct 2013 15:58:29 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of philippe.veber@gmail.com) identity=pra; client-ip=209.85.223.178; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="philippe.veber@gmail.com"; x-sender="philippe.veber@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of philippe.veber@gmail.com designates 209.85.223.178 as permitted sender) identity=mailfrom; client-ip=209.85.223.178; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="philippe.veber@gmail.com"; x-sender="philippe.veber@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-ie0-f178.google.com) identity=helo; client-ip=209.85.223.178; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="philippe.veber@gmail.com"; x-sender="postmaster@mail-ie0-f178.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AjwCAD8aUFLRVd+ylGdsb2JhbABZgz9Sgyi9cYEOCBYOAQEBAQcLCwkSKoIlAQEEASMdARsdAQMMBgUEBzcCAiEBAREBBQEcBhMIh2sBAwkGDJ1GjAJRgwqEAgoZJw1kiQEBAQQMjFqCZwQHgmqBOQOWGIFpjEqDSxgphFA6 X-IPAS-Result: AjwCAD8aUFLRVd+ylGdsb2JhbABZgz9Sgyi9cYEOCBYOAQEBAQcLCwkSKoIlAQEEASMdARsdAQMMBgUEBzcCAiEBAREBBQEcBhMIh2sBAwkGDJ1GjAJRgwqEAgoZJw1kiQEBAQQMjFqCZwQHgmqBOQOWGIFpjEqDSxgphFA6 X-IronPort-AV: E=Sophos;i="4.90,1039,1371074400"; d="scan'208";a="29217485" Received: from mail-ie0-f178.google.com ([209.85.223.178]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 05 Oct 2013 15:58:28 +0200 Received: by mail-ie0-f178.google.com with SMTP id to1so12135216ieb.9 for ; Sat, 05 Oct 2013 06:58:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wvpT3JAWmF0U+IG3ZQK5wvUO95zjcRc3oHFYRKfgzEc=; b=uv1iY1IdqS8Rgv0ewSMEwwCExB52ulB1vRfp5riRkG2FK+o95UUZpDk6BsjSzP30/r M01VY6o22xq5tmu872WnfnLzCWikHnEKTSuOhl5LWXx1fyzeLsNw49RIX5Oy8CYD/tS1 dyRNxw7JfOD54R8LI8eyfNCUfEG7puwIFITNw7lKv6q9oecCPlR/5AAshwvHgvI+t4qP N/avsBJo9Q5xgyWVQd+M46Gq7Xo5RNRtLXDVGqHEWWKGy578rmlLL+JR7KxcgJjChtxw NBbUoFwXYztqSojYSTrAkrFVbgxT1CbNWKzqB0mGNIePHDCsWwhpcMY0cIsNZtAUnIKu Sx9g== X-Received: by 10.42.51.6 with SMTP id c6mr11572857icg.3.1380981507214; Sat, 05 Oct 2013 06:58:27 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.126.163 with HTTP; Sat, 5 Oct 2013 06:58:07 -0700 (PDT) In-Reply-To: References: From: Philippe Veber Date: Sat, 5 Oct 2013 15:58:07 +0200 Message-ID: To: =?ISO-8859-2?Q?Micha=B3_Kurcewicz?= Cc: caml users Content-Type: multipart/alternative; boundary=20cf301cc4562dd3cb04e7fed052 X-Validation-by: philippe.veber@gmail.com Subject: Re: [Caml-list] OASIS help - libraries with mixed C/C++ part --20cf301cc4562dd3cb04e7fed052 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Michal, for an example you can have a look at a binding [1] of the Irrlicht 3d engine (for the record my fork [2] currently has a small addition) or a binding [3] I started (but never got very far) of the Ogre3D library. The latter shows how to put the C++ files in a subdirectory, which was not that easy to obtain. HTH, Philippe. [1] https://github.com/antegallya/OCaml-Irrlicht [2] https://github.com/pveber/OCaml-Irrlicht [3] https://github.com/pveber/ogrillon 2013/10/5 Micha=C5=82 Kurcewicz > > Hello, > > I am migrating some old code from OCamlMakefile to a oasis/ocamlbuild > based build process. While the migration is generally straightforward, I > have encountered some problems with a library where the C part includes > mixed C/C++ code. Putting the C++ files into CSources: in _oasis does not > seem to work, the files are not even copied over to the _build directory, > changing the file extensions and adding some options (-x c++) also does n= ot > solve the problem. What is recommended way to build libraries that include > a mixed C/C++ part using OASIS/ocamlbuild? > > Regards, > > --mk > --20cf301cc4562dd3cb04e7fed052 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Michal,

for an example you can have a look at a = binding [1] of the Irrlicht 3d engine (for the record my fork [2] currently= has a small addition) or a binding [3] I started (but never got very far) = of the Ogre3D library. The latter shows how to put the C++ files in a subdi= rectory, which was not that easy to obtain.

HTH,
=C2=A0 Philippe.

[1] https://github.com/antegallya/OCaml-Irrlicht
[= 2] https://github.com/= pveber/OCaml-Irrlicht
[3] https://github.com/pvebe= r/ogrillon


2013/10/5 Micha=C5=82 Kurcewicz <michal.kurcewicz@gmai= l.com>

Hello,
<= br>
I am migrating some old code from OCamlMakefile to a oasis/oc= amlbuild based build process. While the migration is generally=C2=A0straigh= tforward, I have encountered some problems with a library where the C part = includes mixed C/C++ code. Putting the C++ files into CSources: in _oasis d= oes not seem to work, the files are not even copied over to the _build dire= ctory, changing the file extensions and adding some options (-x c++) also d= oes not solve the problem. What is recommended way to build libraries that = include a mixed C/C++ part using OASIS/ocamlbuild?

Regards,

--mk

--20cf301cc4562dd3cb04e7fed052--