You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without considering copyright issue, we are not supposed to "hack" the ocaml source files. So they should be outside of our git repo, in a separate directory, with a clear dependency.
Some $VARIABLE could be setup before compiling to point to the corresponding directory.
Moreover, git is actually tracking some files that are generated during the ./configure step.
The text was updated successfully, but these errors were encountered:
We are indeed supposed to hack the ocaml source files, since it is not adapted "as is" for the use we intend to make of it. I already had to make some modifications to the interp.c/h source files to make some functions available externally.
But the extent to which we have to hack it will grow when we have to plug VMKit in the project.
I'd gladly be proved wrong about this, in the form of a diff/pull request that shows me how to have the same functionality without hacking in the ocaml source code.
We can then treat the license/copyright issue separately. The configure files can probably be removed right away.
Without considering copyright issue, we are not supposed to "hack" the ocaml source files. So they should be outside of our git repo, in a separate directory, with a clear dependency.
Some $VARIABLE could be setup before compiling to point to the corresponding directory.
Moreover, git is actually tracking some files that are generated during the ./configure step.
The text was updated successfully, but these errors were encountered: