unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Jone <yeger9@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Simple configure-make-make_install with Guix
Date: Thu, 24 May 2018 21:53:36 +0200	[thread overview]
Message-ID: <20180524215337.3ae1ffe0@lepiller.eu> (raw)
In-Reply-To: <87in7c7jqn.fsf@gmail.com>

Le Thu, 24 May 2018 22:48:48 +0000,
Jone <yeger9@gmail.com> a écrit :

> Hello! I'm wondering, how could I operate with unpacked sources?
> So far I see only this:
> 
>   guix build -f /home/jone/Desktop/template.scm
> guix build: error: #<unspecified>: not something we can build

Hi Jone,

your file should evaluate to a package, not simply define it.
http://www.gnu.org/software/guix/manual/html_node/Additional-Build-Options.html#Additional-Build-Options
has an example for how to use -f. In your case, adding gvolwheel at the
end of the file should work too. Also, you don't need guix' sources for
that.

> 
> Files:
> 1. template.scm
> (use-modules
>  (ice-9 match)
>  (srfi srfi-1)
>  (guix gexp)
>  (guix licenses)
>  (guix build-system gnu)
>  (guix packages)
>  (gnu packages)
>  (gnu packages glib)
>  (gnu packages gtk)
>  (gnu packages audio))
> (define-public gvolwheel
>   (package
>    (name "gvolwheel")
>    (version "-1.0")
>    (source (local-file "/home/jone/Desktop/gvolwheel-1.0"
> #:recursive? #t)) (build-system gnu-build-system)
>    (native-inputs
> 	`(("pkg-config" ,pkg-config)))
>    (inputs
> 	`(("alsa-lib" ,alsa-lib)
> 	  ("gtk+" ,gtk+)))
>    (synopsis "test")
>    (description "test")
>    (home-page "https://sourceforge.net/projects/gvolwheel")
>    (license gpl2)))
> 
> 2. ls -1 .
> aclocal.m4
> AUTHORS
> ChangeLog
> config.guess
> config.h.in
> config.sub
> configure
> configure.ac
> COPYING
> depcomp
> INSTALL
> install-sh
> ltmain.sh
> Makefile.am
> Makefile.in
> missing
> mkinstalldirs
> NEWS
> pixmaps
> po
> README
> src
> 
> This is just an example (a little harder than "GNU Hello"). I would
> like to learn to build such things.

  reply	other threads:[~2018-05-24 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 22:48 Simple configure-make-make_install with Guix Jone
2018-05-24 19:53 ` Julien Lepiller [this message]
2018-05-25  1:07   ` Jone
2018-05-25  8:18     ` Julien Lepiller
2018-05-25 18:33       ` Jone

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=20180524215337.3ae1ffe0@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=yeger9@gmail.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).