From: Ricardo Wurmus <rekado@elephly.net>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Specifying Java version when using ant-build-system
Date: Mon, 15 Aug 2016 16:42:01 +0200 [thread overview]
Message-ID: <87h9am14cm.fsf@elephly.net> (raw)
In-Reply-To: <20160815161734.43f11abd@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hi,
>
> how can I specify that I need a Java 1.8 compiler and source level when using ant-build-system?
The build system adds these inputs by default:
(build-inputs `(("jdk" ,jdk "jdk")
("ant" ,ant)
("zip" ,zip)
,@native-inputs))
You should be able to override each of these by specifying them as a
keyword argument, e.g.
(arguments
`(#:jdk ,some-other-jdk
#:zip ,some-other-zip))
> Also, guix/build-system/ant.scm says:
>
> (define* (ant-build store name inputs
> #:key
> (tests? #t)
> (test-target "tests")
> (configure-flags ''())
> (make-flags ''())
> (build-target "jar")
> (jar-name #f)
> (phases '(@ (guix build ant-build-system)
> %standard-phases))
> (outputs '("out"))
> (search-paths '())
> (system (%current-system))
> (guile #f)p
> ^^^ what does this mean?
Ouch! This shouldn’t have been committed. This is what happened pretty
often with my terrible keyboard at work — my control key (among many
other keys) wasn’t very reliable and would sometimes stop working while
I moved around in the sources in Emacs (where Ctrl+p moves up one
line).
I’m surprised this doesn’t lead to an error.
~~ Ricardo
next prev parent reply other threads:[~2016-08-15 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 14:17 Specifying Java version when using ant-build-system Danny Milosavljevic
2016-08-15 14:27 ` Thompson, David
2016-08-15 14:42 ` Ricardo Wurmus [this message]
2016-08-16 0:38 ` Leo Famulari
2016-08-16 7:58 ` Ricardo Wurmus
2016-08-16 18:10 ` Leo Famulari
2016-08-30 9:17 ` Ludovic Courtès
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=87h9am14cm.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.