CRAN Package Check Results for Package lidR

Last updated on 2025-05-31 20:50:38 CEST.

Flavor	Version	T_install	T_check	T_total	Status
r-devel-linux-x86_64-debian-clang	4.2.0	134.94	547.12	682.06	OK
r-devel-linux-x86_64-debian-gcc	4.2.0	93.98	329.10	423.08	OK
r-devel-linux-x86_64-fedora-clang	4.2.0			1109.74	OK
r-devel-linux-x86_64-fedora-gcc	4.2.0			707.19	OK
r-devel-windows-x86_64	4.1.2	139.00	473.00	612.00	NOTE
r-patched-linux-x86_64	4.1.2	125.63	501.85	627.48	NOTE
r-release-linux-x86_64	4.2.0	133.11	508.79	641.90	OK
r-release-macos-arm64	4.2.0			219.00	OK
r-release-macos-x86_64	4.2.0			39.00	ERROR
r-release-windows-x86_64	4.2.0	118.00	432.00	550.00	OK
r-oldrel-macos-arm64	4.2.0			267.00	NOTE
r-oldrel-macos-x86_64	4.2.0			43.00	ERROR
r-oldrel-windows-x86_64	4.2.0	114.00	472.00	586.00	NOTE

Check Details

Version: 4.1.2
Check: compiled code
Result: NOTE File 'lidR/libs/x64/lidR.dll': Found non-API call to R: 'Rf_GetOption' Compiled code should not call non-API entry points in R. See 'Writing portable packages' in the 'Writing R Extensions' manual, and section 'Moving into C API compliance' for issues with the use of non-API entry points. Flavor: r-devel-windows-x86_64

Version: 4.1.2
Check: compiled code
Result: NOTE File ‘lidR/libs/lidR.so’: Found non-API call to R: ‘Rf_GetOption’ Compiled code should not call non-API entry points in R. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual, and section ‘Moving into C API compliance’ for issues with the use of non-API entry points. Flavor: r-patched-linux-x86_64

Version: 4.2.0
Check: whether package can be installed
Result: ERROR Installation failed. Flavors: r-release-macos-x86_64, r-oldrel-macos-x86_64

Version: 4.2.0
Check: installed package size
Result: NOTE installed size is 14.7Mb sub-directories of 1Mb or more: R 2.0Mb doc 1.0Mb extdata 1.2Mb libs 9.9Mb Flavors: r-oldrel-macos-arm64, r-oldrel-windows-x86_64