4 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
5 <meta name="generator" content="AsciiDoc 8.6.9">
6 <title>MLNLFFIGen</title>
7 <link rel="stylesheet" href="./asciidoc.css" type="text/css">
8 <link rel="stylesheet" href="./pygments.css" type="text/css">
11 <script type="text/javascript" src="./asciidoc.js"></script>
12 <script type="text/javascript">
17 <link rel="stylesheet" href="./mlton.css" type="text/css">
19 <body class="article">
21 <div id="banner-home">
22 <a href="./Home">MLton 20180207</a>
30 <div class="sectionbody">
31 <div class="paragraph"><p><span class="monospaced">mlnlffigen</span> generates a <a href="MLNLFFI">MLNLFFI</a> binding from a collection of <span class="monospaced">.c</span>
32 files. It is based on the <a href="CKitLibrary">CKitLibrary</a>, which is primarily designed
33 to handle standardized C and thus does not understand many (any?)
34 compiler extensions; however, it attempts to recover from errors when
35 seeing unrecognized definitions.</p></div>
36 <div class="paragraph"><p>In order to work around common gcc extensions, it may be useful to add
37 <span class="monospaced">-cppopt</span> options to the command line; for example
38 <span class="monospaced">-cppopt '-D__extension__'</span> may be occasionally useful. Fortunately,
39 most portable libraries largely avoid the use of these types of
40 extensions in header files.</p></div>
41 <div class="paragraph"><p><span class="monospaced">mlnlffigen</span> will normally not generate bindings for <span class="monospaced">#included</span>
42 files; see <span class="monospaced">-match</span> and <span class="monospaced">-allSU</span> if this is desirable.</p></div>
46 <div id="footnotes"><hr></div>
48 <div id="footer-text">
50 <div id="footer-badges">