From: Leo Famulari <leo@famulari.name>
To: Arnaud B <arnaud.beaudhuin@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Unison GTK UI in unison package
Date: Mon, 2 Apr 2018 16:16:05 -0400 [thread overview]
Message-ID: <20180402201605.GA3852@jasmine.lan> (raw)
In-Reply-To: <CAAD90k_jGtePxzmh6Hs79_ROJdSwuyg0KYG-3dxrg5CFTz10Aw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2104 bytes --]
On Mon, Apr 02, 2018 at 02:10:22PM +0200, Arnaud B wrote:
> I looked at the ocaml.scm file where the unison package is defined,
> together with ocaml, lablgtk and a number of other related tools. It uses
> the gtk module (gnu packages gtk), in which there is pango as well.
> So it seems everything is in place to build unison and at the same time its
> graphical version, according to the build instructions
> <https://webdav.seas.upenn.edu/svn/unison/branches/2.48/src/INSTALL.gtk2>
> given for that.
> But in the end in my GuixSD as the user having done the installation, I
> just end up with the CLI unison and not unison-gtk2 as expected.
> I tried explicitly installing various packages such as gtk+, lablgtk, and
> then rebuilding the unison package, to no avail.
Basically, the packages that are required to build the Unison GUI, such
as lablgtk, GTK+ itself, etc, are not present in the environment where
Unison is built by Guix. They may be defined in the same source file as
the Unison package, or they may be imported by that file, but this does
not mean they are present in the Unison build environment. Additionally,
installing a package with `guix package --install` has no effect on how
packages are built.
Each time Guix builds a package, it uses an isolated environment that
only includes the software specified in the package definition of the
package being built, as well as "implicit" dependencies that come with
the specified build system.
To make progress on building the Unison GUI, I recommend adding the
required packages to a new inputs field in the Unison package
definition. You can copy the structure of the native-inputs field for
this.
I recommend reading the Introduction of the Guix manual [0], and
continuing to other sections as your interest allows. You will also find
some useful info in Package Reference [1].
Please don't hesitate to ask more questions here or on the Guix IRC
channel, #guix on Freenode.
[0]
https://www.gnu.org/software/guix/manual/html_node/Introduction.html
[1]
https://www.gnu.org/software/guix/manual/html_node/package-Reference.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-02 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 12:10 Unison GTK UI in unison package Arnaud B
2018-04-02 20:16 ` Leo Famulari [this message]
2018-04-03 21:24 ` Arnaud B
2020-03-25 9:18 ` Marco van Hulten
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180402201605.GA3852@jasmine.lan \
--to=leo@famulari.name \
--cc=arnaud.beaudhuin@gmail.com \
--cc=help-guix@gnu.org \
/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).