caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <alain@frisch.fr>
To: Bikal Gurung <bikal.gurung@lemaetech.co.uk>
Cc: r.3@libertysurf.fr, caml-list@inria.fr
Subject: Re: [Caml-list] Ocaml on windows
Date: Wed, 26 Jun 2013 21:54:21 +0200	[thread overview]
Message-ID: <51CB46ED.1010009@frisch.fr> (raw)
In-Reply-To: <CAB-rfD1hH2WxB8NufkQt9D4CKHViMWx1Bh-m=s2VvYr5MP_-Ow@mail.gmail.com>

On 6/26/2013 7:45 PM, Bikal Gurung wrote:
> I am looking to develop a desktop application which will be distributed
> to customers, so for now I think I will need ocaml libs like wxwidget,
> batteries, sql lite db library, sockets, networking etc.
> Is anyone using omake on windows? Does it have a dependency on Cygwin
> like ocamlbuild?

LexiFi uses omake on Windows and Linux.  It does not depend on Cygwin 
itself, if you are careful enough to not use any Cygwin tool in the 
build rules, of course.  omake actually implements a decent scripting 
language (with built-in versions of some useful tools).

FWIW, we use a tool ( http://www.lexifi.com/csml ) to interact easily 
with the .Net framework, allowing our application to access .Net 
components.  For instance, our Windows GUI is based on .Net Windows 
Forms and we use the .Net driver from Oracle.  (For PostgreSQL, we use 
Markus' ocaml bindings to the native libpq library.)


Alain

> B.
>
> Bikal Gurung
> Enterprise Integration Architect
> bikal.gurung@lemaetech.co.uk <mailto:bikal.gurung@lemaetech.co.uk>
> Mobile: +44 (0) 777 556 4109
> London, UK
>
>
> On 26 June 2013 13:02, <r.3@libertysurf.fr <mailto:r.3@libertysurf.fr>>
> wrote:
>
>     Hello,
>     I personnaly used mxe to cross compile from linux to windows (gtk2,
>     cairo, camlimages)
>     Mxe is a set of hundreds of C libraries cross-compiled, plus a few
>     ocaml libraries.
>     community is nice for support of C libraries, but would not be able
>     to help you on ocaml packages.
>
>     what C and ocaml libraries does your project depend on ? What build
>     system do you use (ocamlbuild, Makefile, ...)
>     This might be easy to use mxe, depending on your answers.
>
>     Best regards,
>     William
>
>
>


  parent reply	other threads:[~2013-06-26 19:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130626113838.0643281793@sympa.inria.fr>
2013-06-26 12:02 ` r.3
2013-06-26 17:45   ` Bikal Gurung
2013-06-26 17:55     ` David Allsopp
2013-06-26 18:07       ` Bikal Gurung
2013-06-26 18:28         ` Wojciech Meyer
2013-06-26 18:12       ` Adrien Nader
2013-06-26 19:54     ` Alain Frisch [this message]
2013-06-24  9:07 Bikal Gurung
     [not found] ` <E51C5B015DBD1348A1D85763337FB6D9CC8677FE@Remus.metastack.local>
2013-06-24 10:01   ` Bikal Gurung
2013-06-24 10:11     ` Jonathan Protzenko
2013-06-24 12:10       ` Malcolm Matalka
2013-06-24 17:18       ` Adrien Nader
2013-06-25  8:40     ` David Allsopp
2013-06-26 18:17       ` Adrien Nader
2013-06-26 19:55         ` David Allsopp
2013-06-24 17:21 ` Adrien Nader
2013-06-24 20:16   ` AW: " Gerd Stolpmann
2013-06-26 18:29     ` Adrien Nader
2013-06-26 18:46       ` Wojciech Meyer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51CB46ED.1010009@frisch.fr \
    --to=alain@frisch.fr \
    --cc=bikal.gurung@lemaetech.co.uk \
    --cc=caml-list@inria.fr \
    --cc=r.3@libertysurf.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).