> On 29/05/2024, at 11:21 AM, Boylan, Ross wrote:
>
> Is it required that the package submitted to CRAN have been built with R CMD
> build rather than some other tool? When you say "CRAN has nothing to do with
> any of the above [different tools]" it sounds as if one can use anything; but
[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
Duncan's point about options is key... the build options set by default in
devtools etc are generally configured to minimize the time required to identify
the next big issue to address. Options appropriate for preparing to submit to
CRAN are slow and inconvenient for developing.
I recommend tha
-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 package:
Ross,
R CMD build is the only offical way to build a (source) package in R.
All other "tools" are just convenience wrappers by 3rd parties that call R CMD
build eventually. There is no reason to assume that those tools should behave
in a certain way - nor are you required to use them. They typi
On 2024-05-28 6:20 p.m., Boylan, Ross via R-package-devel wrote:
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 al
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
On 5/28/24 06:18, drc via R-package-devel wrote:
Is it possible to get flex in the win-builder windows environment? It's present
in the debian environment. My package depends on cmake, bison, and flex. Each
of these are listed in the `SystemRequirments` field of my DESCRIPTION file but
flex is
Is it possible to get flex in the win-builder windows environment? It's present
in the debian environment. My package depends on cmake, bison, and flex. Each
of these are listed in the `SystemRequirments` field of my DESCRIPTION file but
flex is the only one that cmake can't find.
The win-build
