4 ms·

Weirdly enough, last night I posted a project skeleton up on GH: https://github.com/wickedchicken/ocaml_skeleton https://github.com/wickedchicken/ocaml_skeleton

Weirdly enough, last night I posted a project skeleton up on GH: https://github.com/wickedchicken/ocaml_skeleton https://github.com/wickedchicken/ocaml_skeleton While the core OCaml language is fun to play around in, a lot of the build tools are scattered across the web and hard to decipher (4 year old blog posts with only half-working code don't help). This aims to remedy that, and I'd appreciate any feedback :).

aplusbi 15y ago
I highly recommend you check out oasis (http://oasis.forge.ocamlcore.org/ http://oasis.forge.ocamlcore.org/). It's a meta build system which is quickly gaining traction in the OCaml community. It's still in early development but works extremely well for most projects.
- wickedchicken 15y ago
  Wow! Very cool. Excited to take a look at this
fogus 15y ago
Over the past half year I've been exploring Haskell and so naturally my interest has recently piqued at OCaml. Thank you for this, it couldn't have come at a better time. I wonder if you think it would be worth including camlp4/p5 in the skeleton?
- wickedchicken 15y ago
  Unfortunately as I'm still coming up in the language myself I don't have knowledge of what would be useful there. If someone who does can point to somewhere, I can try and fit it in.
deleted 15y ago
[deleted]
iskander 15y ago
Cool, this would have helped me a lot when I was getting started. An idea: You might want to start the README with 'Skeleton is X'. I had to scan around for a while to figure out what your project actually does.
- wickedchicken 15y ago
  Good idea, thanks
  - iskander 15y ago
    A question: What's the point of the Makefile? Why not use ocamlbuild directly?
    - wickedchicken 15y ago
      Multiple reasons: * It gives you a convenient place to stash extra config options in your project. For example, instead of having to type (and remember!) -tag pkg_oUnit, it's just in the Makefile. You can't forget something that's been saved in a text file! * It gives you a single point of entry for "other" tools which may be added later -- documentation generation, packaging, installing as a library or Debian package. I personally like all of that recorded in one file so I have to search around less. * As an expository project, it's helpful to show off clear examples of ocamlbuild itself -- the syntax is different enough that someone just starting out in the language may not be able to grok the documentation enough to just get something running.
- wickedchicken 15y ago
  Hey, I looked up your profile and you mention doing some compiler research. HN has no way to 'ping' a user, but I'd be curious what that research entailed...
  - iskander 15y ago
    If that email on qrunk.com works, then I just emailed you.

aplusbi 15y ago

I highly recommend you check out oasis (http://oasis.forge.ocamlcore.org/ http://oasis.forge.ocamlcore.org/). It's a meta build system which is quickly gaining traction in the OCaml community. It's still in early development but works extremely well for most projects.

wickedchicken 15y ago
Wow! Very cool. Excited to take a look at this

fogus 15y ago

Over the past half year I've been exploring Haskell and so naturally my interest has recently piqued at OCaml. Thank you for this, it couldn't have come at a better time. I wonder if you think it would be worth including camlp4/p5 in the skeleton?

wickedchicken 15y ago
Unfortunately as I'm still coming up in the language myself I don't have knowledge of what would be useful there. If someone who does can point to somewhere, I can try and fit it in.

deleted 15y ago

[deleted]

iskander 15y ago

Cool, this would have helped me a lot when I was getting started. An idea: You might want to start the README with 'Skeleton is X'. I had to scan around for a while to figure out what your project actually does.

wickedchicken 15y ago
Good idea, thanks
- iskander 15y ago
  A question: What's the point of the Makefile? Why not use ocamlbuild directly?
  - wickedchicken 15y ago
    Multiple reasons: * It gives you a convenient place to stash extra config options in your project. For example, instead of having to type (and remember!) -tag pkg_oUnit, it's just in the Makefile. You can't forget something that's been saved in a text file! * It gives you a single point of entry for "other" tools which may be added later -- documentation generation, packaging, installing as a library or Debian package. I personally like all of that recorded in one file so I have to search around less. * As an expository project, it's helpful to show off clear examples of ocamlbuild itself -- the syntax is different enough that someone just starting out in the language may not be able to grok the documentation enough to just get something running.
wickedchicken 15y ago
Hey, I looked up your profile and you mention doing some compiler research. HN has no way to 'ping' a user, but I'd be curious what that research entailed...
- iskander 15y ago
  If that email on qrunk.com works, then I just emailed you.