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
Original bug ID: 4254 Reporter:@alainfrisch Status: resolved (set by @damiendoligez on 2016-04-19T12:27:35Z) Resolution: suspended Priority: normal Severity: minor Target version: 4.03.0+dev / +beta1 Category: ~DO NOT USE (was: OCaml general)
Bug description
In bytelink.ml, the options -ccobj, -ccopt, -dllib and -custom present in linked .cma files are ignored when creating a bytecode executable using -use-runtime (or -use-prims). For -ccobj, -ccopt and -custom this is natural, but I think it would be best if it wasn't the case for -dllib (if one want to ignore these, one can still use -noautolink).
The text was updated successfully, but these errors were encountered:
This looks strange. -use-runtime and -use-prims date back to a time when the runtime couldn't do dynamic loading of C files to get extra primitives. Why do you need them if you're going to dynamically load your primitives anyway?
Original bug ID: 4254
Reporter: @alainfrisch
Status: resolved (set by @damiendoligez on 2016-04-19T12:27:35Z)
Resolution: suspended
Priority: normal
Severity: minor
Target version: 4.03.0+dev / +beta1
Category: ~DO NOT USE (was: OCaml general)
Bug description
In bytelink.ml, the options -ccobj, -ccopt, -dllib and -custom present in linked .cma files are ignored when creating a bytecode executable using -use-runtime (or -use-prims). For -ccobj, -ccopt and -custom this is natural, but I think it would be best if it wasn't the case for -dllib (if one want to ignore these, one can still use -noautolink).
The text was updated successfully, but these errors were encountered: