From: "Michał Kurcewicz" <michal.kurcewicz@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] OASIS help - libraries with mixed C/C++ part
Date: Sat, 5 Oct 2013 12:13:28 +0200 [thread overview]
Message-ID: <CAM3BXOwZyu7GEL-fL-+LYhup6YG4P544L-rzt6BV+EPsV5uY8A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
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 not solve
the problem. What is recommended way to build libraries that include a
mixed C/C++ part using OASIS/ocamlbuild?
Regards,
--mk
[-- Attachment #2: Type: text/html, Size: 734 bytes --]
next reply other threads:[~2013-10-05 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-05 10:13 Michał Kurcewicz [this message]
2013-10-05 13:58 ` Philippe Veber
2013-10-06 3:19 ` ygrek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM3BXOwZyu7GEL-fL-+LYhup6YG4P544L-rzt6BV+EPsV5uY8A@mail.gmail.com \
--to=michal.kurcewicz@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox