JavaGD

Java Graphics Device

v0.6-6 · Aug 19, 2025 · GPL-2 | GPL-3

Description

Graphics device routing all graphics commands to a Java program. The actual functionality of the JavaGD depends on the Java-side implementation. Simple AWT and Swing implementations are included.

Downloads

Last 30 days

3768th

Last 90 days

17.9K

Last year

Trend: +2.4% (30d vs prior 30d)

CRAN Check Status

14 NOTE

Show all 14 flavors

Flavor	Status	Time
r-devel-linux-x86_64-debian-clang	NOTE	38.9s
r-devel-linux-x86_64-debian-gcc	NOTE	30.4s
r-devel-linux-x86_64-fedora-clang	NOTE	58.1s
r-devel-linux-x86_64-fedora-gcc	NOTE	54.6s
r-devel-macos-arm64	NOTE	18s
r-devel-windows-x86_64	NOTE	73s
r-oldrel-macos-arm64	NOTE
r-oldrel-macos-x86_64	NOTE	66s
r-oldrel-windows-x86_64	NOTE	88s
r-patched-linux-x86_64	NOTE	34.8s
r-release-linux-x86_64	NOTE	34.2s
r-release-macos-arm64	NOTE
r-release-macos-x86_64	NOTE	50s
r-release-windows-x86_64	NOTE	74s

Check details (19 non-OK)

NOTE r-devel-linux-x86_64-debian-clang

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@R-project.org>’

Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-debian-clang

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-debian-gcc

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@R-project.org>’

Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-debian-gcc

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-fedora-clang

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-fedora-gcc

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-oldrel-macos-arm64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-oldrel-macos-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-macos-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-oldrel-windows-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-patched-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-macos-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way to quote/escape the space in Make rules and directives.  However,
one can and should quote pathnames when passed from Makefile to the
shell, and this can be done specifically when invoking Make recursively.
It is therefore recommended to use the Make '-f' option to include files
in directories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

Additional Issues

rchk Details →

Check History

NOTE 0 OK · 14 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Apr 6, 2026

NOTE r-devel-linux-x86_64-debian-clang

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@R-project.org>’

Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-debian-gcc

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@R-project.org>’

Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-fedora-clang

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-fedora-gcc

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-patched-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-macos-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-oldrel-macos-arm64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-macos-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-windows-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

ERROR 0 OK · 13 NOTE · 0 WARNING · 1 ERROR · 0 FAILURE Apr 3, 2026

NOTE r-devel-linux-x86_64-debian-clang

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@R-project.org>’

Package has FOSS license, installs .class/.jar but has no 'java' directory.

ERROR r-devel-linux-x86_64-debian-gcc

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@R-project.org>’

Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-fedora-clang

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-fedora-gcc

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-patched-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-macos-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-oldrel-macos-arm64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-macos-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-windows-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE 0 OK · 14 NOTE · 0 WARNING · 0 ERROR · 0 FAILURE Mar 10, 2026

NOTE r-devel-linux-x86_64-debian-clang

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@R-project.org>’

Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-debian-gcc

CRAN incoming feasibility

Maintainer: ‘Simon Urbanek <Simon.Urbanek@R-project.org>’

Package has FOSS license, installs .class/.jar but has no 'java' directory.

NOTE r-devel-linux-x86_64-fedora-clang

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-linux-x86_64-fedora-gcc

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-devel-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-patched-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-linux-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-macos-arm64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-macos-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-release-windows-x86_64

include directives in Makefiles

Found the following Makefile(s) with an include directive with a pathname using R_HOME:
  src/jvm-w32/Makefile
Even though not recommended, variable R_HOME may contain spaces.
Makefile directives use space as a separator and there is no portable
way 
...[truncated]...
ctories specified using R_HOME.  This option can be specified
multiple times to include multiple Makefiles.  Note that 'Makeconf' is
included automatically into top-level makefile of a package.
More information can be found in 'Writing R Extensions'.

NOTE r-oldrel-macos-arm64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-macos-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

NOTE r-oldrel-windows-x86_64

for GNU extensions in Makefiles

GNU make is a SystemRequirements.

Reverse Dependencies (4)

depends

JGR

imports

Crossover gMCP mutossGUI

Dependency Network

Version History

new 0.6-6 Mar 10, 2026

updated 0.6-6 ← 0.6-5 diff Aug 18, 2025

updated 0.6-5 ← 0.6-4 diff Nov 29, 2022

updated 0.6-4 ← 0.6-2 diff Nov 1, 2020

updated 0.6-2 ← 0.6-1.1 diff Apr 29, 2020

updated 0.6-1.1 ← 0.6-1 diff Apr 14, 2019

updated 0.6-1 ← 0.5-5.1 diff Sep 12, 2012

updated 0.5-5.1 ← 0.5-5 diff Sep 9, 2012

updated 0.5-5 ← 0.5-4 diff Dec 10, 2011

updated 0.5-4 ← 0.5-3 diff Jun 21, 2011

updated 0.5-3 ← 0.5-2 diff Oct 17, 2010

updated 0.5-2 ← 0.5-1 diff Oct 18, 2008

updated 0.5-1 ← 0.5-0 diff Apr 3, 2008

updated 0.5-0 ← 0.4-3 diff Mar 23, 2008

updated 0.4-3 ← 0.4-2 diff Aug 24, 2007

updated 0.4-2 ← 0.4-1 diff May 21, 2007

updated 0.4-1 ← 0.3-6 diff Apr 30, 2007

updated 0.3-6 ← 0.3-5 diff Mar 6, 2007

updated 0.3-5 ← 0.3-4 diff Sep 14, 2006

updated 0.3-4 ← 0.3-3 diff Aug 18, 2006