From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] package/openjdk: add support for building the full jdk
Date: Sat, 18 Apr 2020 14:02:11 +0200 [thread overview]
Message-ID: <20200418120211.GN5853@scaer> (raw)
In-Reply-To: <20200417232922.3762195-4-aduskett@gmail.com>
Adam, All,
On 2020-04-17 16:29 -0700, aduskett at gmail.com spake thusly:
> From: Adam Duskett <Aduskett@gmail.com>
>
> Some users may require the full JDK on the target to debug or compile programs.
> This change is relatively trivial to add.
I concur with Thomas on that one: we do not want to support doing
development on the target.
I've marked the patch as rejected in patchwork, now.
Still, please read on for further review of this comit log...
> To install the full JDK, do the following:
> - Add a new entry in package/openjdk/Config.in with the variable
> BR2_PACKAGE_OPENJDK_FULL_JDK
>
> - Check for this variable in openjdk.mk, if it is selected set the following
> variables:
> OPENJDK_INSTALL_DIR = jdk
> OPENJDK_MAKE_TARGET=jdk-image
> Otherwise, set the variables to jre and legacy-jre-image respectively.
>
> - change legacy-jre-image to $(OPENJDK_MAKE_TARGET) in the OPENJD_BUILD_CMDS
> define.
>
> - Change jre/* to $(OPENJDK_INSTALL_DIR)/* in the OPENJDK_INSTALL_TARGET_CMDS
> define
Again, this commit log is not very helpful: it explains what is done,
which is not so much interesting in itself: it is just restating what
the code does, so it is bnetter to look at the code. What a commit log
should do, is explain *why* a change needs to be done.
Basically, a commit log should be a three-stage story:
1. description of the problem
2. explanations of why the problem occurs
3. explanations on how we solve the problem
Regards,
Yann E. MORIN.
> Signed-off-by: Adam Duskett <Aduskett@gmail.com>
> ---
> package/openjdk/Config.in | 7 +++++++
> package/openjdk/openjdk.mk | 12 ++++++++++--
> 2 files changed, 17 insertions(+), 2 deletions(-)
>
> diff --git a/package/openjdk/Config.in b/package/openjdk/Config.in
> index 61294ec49f..158f3031c3 100644
> --- a/package/openjdk/Config.in
> +++ b/package/openjdk/Config.in
> @@ -49,6 +49,13 @@ config BR2_PACKAGE_OPENJDK
>
> if BR2_PACKAGE_OPENJDK
>
> +config BR2_PACKAGE_OPENJDK_FULL_JDK
> + bool "Build the full JDK"
> + help
> + Install the full JDK instead of just the run time.
> + Selecting this option will increase the file system by
> + approximately 110M.
> +
> choice
> prompt "openjdk variant"
> default BR2_PACKAGE_OPENJDK_JVM_VARIANT_SERVER if !BR2_powerpc
> diff --git a/package/openjdk/openjdk.mk b/package/openjdk/openjdk.mk
> index 19e71e98b2..e8803f3cb5 100644
> --- a/package/openjdk/openjdk.mk
> +++ b/package/openjdk/openjdk.mk
> @@ -46,6 +46,14 @@ OPENJDK_JVM_VARIANT = zero
> OPENJDK_DEPENDENCIES += libffi
> endif
>
> +ifeq ($(BR2_PACKAGE_OPENJDK_FULL_JDK),y)
> +OPENJDK_INSTALL_DIR = jdk
> +OPENJDK_MAKE_TARGET=jdk-image
> +else
> +OPENJDK_INSTALL_DIR = jre
> +OPENJDK_MAKE_TARGET=legacy-jre-image
> +endif
> +
> # Because jre/lib has a modules file, installation on a system with a merged
> # /usr directory, and a built Kernel before OpenJDK, the following error
> # occurs: "cp: cannot overwrite directory '/usr/lib/modules with non-directory"
> @@ -117,14 +125,14 @@ endef
> # Make -jn is unsupported. Instead, set the "--with-jobs=" configure option,
> # and use $(MAKE1).
> define OPENJDK_BUILD_CMDS
> - $(TARGET_MAKE_ENV) $(MAKE1) -C $(@D) legacy-jre-image
> + $(TARGET_MAKE_ENV) $(OPENJDK_CONF_ENV) $(MAKE1) -C $(@D) $(OPENJDK_MAKE_TARGET)
> endef
>
> # Calling make install always builds and installs the JDK instead of the JRE,
> # which makes manual installation necessary.
> define OPENJDK_INSTALL_TARGET_CMDS
> mkdir -p $(TARGET_DIR)/$(OPENJDK_INSTALL_BASE)
> - cp -dpfr $(@D)/build/linux-*-release/images/jre/* \
> + cp -dpfr $(@D)/build/linux-*-release/images/$(OPENJDK_INSTALL_DIR)/* \
> $(TARGET_DIR)/$(OPENJDK_INSTALL_BASE)
> cd $(TARGET_DIR)/usr/bin && ln -snf ../../$(OPENJDK_INSTALL_BASE)/bin/* .
> endef
> --
> 2.25.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-04-18 12:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 23:29 [Buildroot] [PATCH 1/4] package/openjdk: fix hash aduskett at gmail.com
2020-04-17 23:29 ` [Buildroot] [PATCH 2/4] package/openjdk: fix installation with merged usr directories aduskett at gmail.com
2020-04-18 12:17 ` Yann E. MORIN
2020-04-18 12:26 ` Yann E. MORIN
2020-04-17 23:29 ` [Buildroot] [PATCH 3/4] package/openjdk: copy all directories and files when installing aduskett at gmail.com
2020-04-18 12:21 ` Yann E. MORIN
2020-04-18 17:00 ` Adam Duskett
2020-04-17 23:29 ` [Buildroot] [PATCH 4/4] package/openjdk: add support for building the full jdk aduskett at gmail.com
2020-04-18 10:03 ` Thomas Petazzoni
2020-04-18 12:02 ` Yann E. MORIN [this message]
2020-04-18 10:01 ` [Buildroot] [PATCH 1/4] package/openjdk: fix hash Thomas Petazzoni
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=20200418120211.GN5853@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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 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.