public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: lablgtk2 (was: [ITP] unison2.48)
Date: Fri, 12 Jun 2015 21:31:00 -0000	[thread overview]
Message-ID: <1434144729.9188.19.camel@cygwin.com> (raw)
In-Reply-To: <4sgmnah53l3dpkdp9n7frrc5fc93f3g76u@4ax.com>

On Fri, 2015-06-12 at 16:40 -0400, Andrew Schulman wrote:
> > On Fri, 2015-06-12 at 03:54 -0400, Andrew Schulman wrote:
> > > OK, pushed to https://github.com/andrex-e-schulman/cygwin-lablgtk2.git.  I
> > > started with the version in Cygwin ports - the cygport file and two patches.  I
> > > adjusted the cygport file as follows:
> > > 
> > > * Added ocaml_lablgtk2_REQUIRES and DEPEND.
> > 
> > Was something missing from the autogenerated requires?
> 
> Yes, IIRC none of them included ocaml. 

Hmm, I'll have to look into that, although practically speaking I don't
think it's much of a concern.

> Also, all of the autogenerated requires included all of the -devel packages -
> about a dozen of them.  Which is undesirable and seems wrong, since then anyone
> who installed unison-gtk for example would need to have all of those -devel
> packages too.

No they wouldn't, no more than anyone installing unison has to install
ocaml.

While ocaml has the toplevel system for use as a script interpreter and
runtime system for bytecode interpretation, the primary practical use of
ocaml (on platforms which support it) is as a native code compiler.  On
these platforms, ocaml *programs* are generally native-compiled for much
better performance, and such use requires -devel packages.

This is particularly true on x86_64-cygwin, where we don't have flexdll
working yet (although upstream is making progress), which severely
limits the usefulness of bytecode interpretation.  

> > > * Replaced $OCAML_LIB_DIR (I think it was) by usr/lib/ocaml.
> > > * Changed ocaml_install (which I can't find anywhere) to "make old-install
> > > DESTDIR=${D}".
> > 
> > These are both provided by ocaml.cygclass.
> 
> Ah, thanks.  I guess I moved the "inherit ocaml" too far down in the file.

inherit commands are intended to be at the top of the .cygport, preceded
only by variables that are required thereby (as indicated in the
manual).

--
Yaakov


  reply	other threads:[~2015-06-12 21:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 16:06 [ITP] unison2.48 Andrew Schulman
2015-06-05 18:46 ` Yaakov Selkowitz
2015-06-05 20:16   ` Andrew Schulman
2015-06-05 22:24     ` Yaakov Selkowitz
2015-06-06  1:59       ` Andrew Schulman
2015-06-11 12:16         ` Michael DePaulo
2015-06-11 12:51           ` Andrew Schulman
2015-06-12  1:24             ` Michael DePaulo
2015-06-12  7:54               ` lablgtk2 (was: [ITP] unison2.48) Andrew Schulman
2015-06-12 19:41                 ` Yaakov Selkowitz
2015-06-12 20:40                   ` Andrew Schulman
2015-06-12 21:31                     ` Yaakov Selkowitz [this message]
2015-06-12 21:52                       ` Andrew Schulman

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=1434144729.9188.19.camel@cygwin.com \
    --to=yselkowitz@cygwin.com \
    --cc=cygwin-apps@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).