Re: [R-pkg-devel] different build tools

2024-05-28 Thread Boylan, Ross via R-package-devel
[Sorry: Outlook doesn't quote messages the "normal" way] -Original Message- From: Simon Urbanek Sent: Tuesday, May 28, 2024 4:10 PM Ross, R CMD build is the only offical way to build a (source) package in R. All other "tools" are just convenience wrappers [] Please note that CRAN

Re: [R-pkg-devel] different build tools

2024-05-28 Thread Boylan, Ross via R-package-devel
-Original Message- From: Duncan Murdoch Sent: Tuesday, May 28, 2024 3:30 PM To: Boylan, Ross ; r-package-devel@r-project.org Subject: Re: [R-pkg-devel] different build tools On 2024-05-28 6:20 p.m., Boylan, Ross via R-package-devel wrote: > There are at least 4 ways to build a pack

[R-pkg-devel] different build tools

2024-05-28 Thread Boylan, Ross via R-package-devel
There are at least 4 ways to build a package: 1. R CMD build 2. pkgbuild::build(), which I believe calls 1. 3. devtools::build(), which calls 2. 4. RStudio GUI, which calls 3. I recently discovered these don't all behave the same. Invoking bootstrap.R at the start requires 2 or g

Re: [R-pkg-devel] handling documentation build tools

2024-05-21 Thread Boylan, Ross via R-package-devel
Thanks for the pointer. You may have been thrown off by some goofs I made in the intro, which said > I would like to build the automatically, with requiring either users or > repositories to have the tools. The intended meaning, with corrections in **, was > I would like to build the *custom

[R-pkg-devel] handling documentation build tools

2024-05-21 Thread Boylan, Ross via R-package-devel
I have some documentation that requires external tools to build. I would like to build the automatically, with requiring either users or repositories to have the tools. What's the best way to accomplish that. Specifically one document is written using the LyX word processor, so the "source" i