William Hu via Cygwin-apps writes: > Just checked the file and I agree that CFLAGS looks a little funny - are > there any > other stupid flags/variables that you had in mind?
NOt immediately, but it makes me wonder if there's other such leakage. I have not found a (text) file that stores this information in the installed package, so it seems that the information is compiled in someplace. > Re Opam switches: As far as I understand, switches are like "git branch" but > for > different compiler installations instead of different code branches; for > example > you can install ocaml 4.14.0 and 4.12.0 side by side and switch between them > easily. In addition to some other things, it effectively edits your PATH > environment variable so when you type "ocamlc" it'll execute the appropriate > version. Yes, I know that. The complete mystery is why you can't use opam to provide results that can be packaged. > General comment: I don't know much about LLVM, but is there a reason why the > other software (dune, ocamlbuild, etc.) must be installed with the system and > not with opam? Because the expecation is that you can get everything in to a working state just by installing the packages. >> Cygport package changes are in the Cygwin Packages Git repository in the >> respective playground branch as before. > > Re OCaml cygport playground: Thanks for the cygport cleanup and changes. > A couple questions: > > src_compile: > 1. Adding flambda to a default system installation of OCaml can slow down > compile times and produce linking incompatibilities with non-flambda code > [1]. > Additionally, there may be value in a vanilla out-of-the-box OCaml > distribution. I've mainly includeed it because LLVM complained it wasn't enabled (obviously it can build the OCaml bindings with and without flambda) since it seems to work and test OK I just flipped that switch. > Let me know if there is some general Cygwin guidance on what features > packaged > language compilers should support. Otherwise, if flambda is necessary for > LLVM, > I could package an flambda and a non-flambda release for each version, and > the > user can pick which one they prefer. I don't think that makes any sense given the way the packaging is done at the moment. In fact, ever since you updated to 4.14.0 all other OCaml packages in Cygwin were dead since you didn't update these at the same time and there is no mechanism in place yet to ensure that ocaml-* packages and the ocaml package target the same version of the compiler. > 2. What benefit does splitting "cygmake" into the 3-step "cygmake world, opt, > opt.opt" have? Plain old "make/cygmake" with no target appears to be the > recommended compilation step. Hysterical raisins… before I got things to actually build it would stop in various places and I was tring to find out where that happened. I've not gone back to reduce it again since it doewsn't incur any (or at least not noticeable) overhead at the moment. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
