From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org,Michael Zucchi <notzed@gmail.com>
Subject: Re: OpenJFX 14, gradle
Date: Sun, 03 May 2020 23:12:39 -0400 [thread overview]
Message-ID: <6BD628BA-151C-4F01-871E-937C443A512A@lepiller.eu> (raw)
In-Reply-To: <9c7d89ad-2bf1-ad37-b513-ef0c57c22220@gmail.com>
Le 3 mai 2020 22:00:24 GMT-04:00, Michael Zucchi <notzed@gmail.com> a écrit :
>
>Morning,
>
>I'm trying to work on updating some java stuff as guix currently only
>has java12 which is a year out of date and javafx8 which is ancient.
>Apart from openjdk 13 and 14 which is in motion I've started looking at
>
>openjfx 14.
>
>But openjfx needs to be compiled with gradle 6 now - the openjfx8
>package uses ant but that is no longer an option (there's some netbeans
>
>ant files there but they seem non functional). guix has no
>build-system
>gradle and looking at gradle I can't imagine there will ever be a
>source-bootstrapped package for it - the 6.0 distribution is 215 jar
>files, mostly external libraries, and it needs gradle to build (because
>
>of course it does). I'm assuming that guix wouldn't accept using
>gradle-wrapper here which is the `supported' build mechanism for the
>openjfx project.
>
>Partly out of curiosity and partly as a potential alternative I spent
>the weekend creating a single 1000 line gnu makefile to replace the
> >10kloc of gradle scripts and existing makefiles. I haven't bothered
>with javafx.web or javafx-swt but otherwise it's complete and only
>requires antlr 4.7 at build time. It uses gnu make features
>specifically and assumes a gnu environment, but it's 3-4x faster on my
>machine (amd r9-3900x).
>
>Another alternative could be simple build script that forgoes
>incremental and parallel compilation support for a smaller script. I
>can
>possibly get that down to a few dozen lines of bash if i can utilise
>the
>existing makefiles.
>
>Is either approach worth pursuing or is the whole idea a lost cause?
>
>Regards,
> Michael
Note that the ant-build-system is able to generate its own build.xml. that's going to be tough, so whatever works for you is fine, as long as everything is free software and source-bootstrapped.
next prev parent reply other threads:[~2020-05-04 3:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 2:00 OpenJFX 14, gradle Michael Zucchi
2020-05-04 3:12 ` Julien Lepiller [this message]
2020-05-04 8:53 ` Alexey Abramov
2020-05-05 2:30 ` Michael Zucchi
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=6BD628BA-151C-4F01-871E-937C443A512A@lepiller.eu \
--to=julien@lepiller.eu \
--cc=guix-devel@gnu.org \
--cc=notzed@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).