New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Recommend ocamlc as driver for compiling C sources for stublibs #5733
Comments
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
This is an interesting improvement proposal for the documentation, and also a good task for a new contributor. Reopening. |
Hi @gasche, I'm new and I want to work on this. |
Please feel free to work on this. Note that writing a good proposal for the manual probably requires some familiarity with the C/OCaml FFI, so this may be one of the harder "good first issue" tasks. |
Cool. I have some knowledge about C/OCaml FFI. |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Original bug ID: 5733
Reporter: gerd
Status: confirmed (set by @damiendoligez on 2012-11-15T14:30:52Z)
Resolution: open
Priority: normal
Severity: feature
Version: 4.00.0
Category: documentation
Tags: junior_job
Monitored by: @ygrek @hcarty @dbuenzli
Bug description
Basically, it is up to the user how to call the C compiler for compiling stublibs. However, in many build systems I see that users do it the wrong way (e.g. hardcode the compiler "gcc", or forget to pass switches like -fPIC which are sometimes required). My wish is that the section "Interfacing C with OCaml" includes examples how to do it right - which is absolutely simple, because you just need to use ocamlc as driver even for C sources.
There could e.g. be a new section before "Statically linking C code with OCaml code" about "Compiling C code". Contents:
The text was updated successfully, but these errors were encountered: