From: Per Bothner <per@bothner.com>
To: Vijay Mathew <vijay.the.lisper@gmail.com>, kawa@sourceware.org
Subject: Re: Dependency Management
Date: Fri, 12 Jul 2019 02:02:00 -0000 [thread overview]
Message-ID: <c183a5a2-dcda-2f33-5320-7efabdcd946b@bothner.com> (raw)
In-Reply-To: <CAK0HBnhZ3uLS2ppJrT0S8Vs-jnPWptCdX+vCTHmdrHjt6Vtq4w@mail.gmail.com>
On 7/11/19 2:54 AM, Vijay Mathew wrote:
> Hi,
>
> How can I automate build and dependency-management for a Kawa project?
> Is there something similar to Leiningen (https://leiningen.org/)?
Kawa tries to be simple and un-opinionated when it comes to build tools.
You can use whatever tooling you'd use for Java: autotools/make, Ant, Grail ...
Kawa aims for natural defaults and an easy mapping between source files/directories
and modules.
This chapter in the manual may be helpful:
https://www.gnu.org/software/kawa/Importing.html
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2019-07-12 2:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 9:55 Vijay Mathew
2019-07-11 23:02 ` Alcides Flores Pineda
2019-07-12 2:02 ` Per Bothner [this message]
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=c183a5a2-dcda-2f33-5320-7efabdcd946b@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.org \
--cc=vijay.the.lisper@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).