Dirk and Duncan,
thanks. the slight nudge towards =R CMD INSTALL= is a helpful reminder,
and hewing close to the straight-and-narrow is undoubtedly a good thing.
cheers, Greg
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/l
On Thu, 24 Jun 2021, Greg Minshall writes:
> hi.
>
> when developing packages, my current work flow is to change the code,
> (re-)build the package, detach/load the package, test (to find the
> N+1'st bug, sigh).
>
> the building step takes tens of seconds.
>
> is there an obvious way to present s
On 6/24/21 11:31 PM, Duncan Murdoch wrote:
On 24/06/2021 4:52 p.m., Dirk Eddelbuettel wrote:
On 24 June 2021 at 16:31, Duncan Murdoch wrote:
| This does the full compile again, so it's slow.
ccache fixes that (as it has its own cache). It also works on macOS.
I haven't tried ccache: shoul
On 24/06/2021 5:53 p.m., Gábor Csárdi wrote:
Actually, I see somewhat different things in RStudio, for me there is
no pre-clean (with the default options AFAIR).
I'm not using the default options, as I said.
Duncan Murdoch
I can reproduce the rebuilding for rgl, but not for other packages I
Actually, I see somewhat different things in RStudio, for me there is
no pre-clean (with the default options AFAIR).
I can reproduce the rebuilding for rgl, but not for other packages I
tried. I vaguely remember a similar issue for another package, which
also used autoconf. So this indeed might be
On 24/06/2021 5:22 p.m., Gábor Csárdi wrote:
On Thu, Jun 24, 2021 at 10:31 PM Duncan Murdoch
wrote:
[...]
I'm working in RStudio on a Mac, in case that makes any difference.
Yes, RStudio probably does its own thing in "Install and restart". The
pre-clean of course removes the object files fro
On 24/06/2021 4:52 p.m., Dirk Eddelbuettel wrote:
On 24 June 2021 at 16:31, Duncan Murdoch wrote:
| This does the full compile again, so it's slow.
ccache fixes that (as it has its own cache). It also works on macOS.
I haven't tried ccache: shouldn't "make" handle that kind of thing?
Duncan
On Thu, Jun 24, 2021 at 10:31 PM Duncan Murdoch
wrote:
[...]
> I'm working in RStudio on a Mac, in case that makes any difference.
Yes, RStudio probably does its own thing in "Install and restart". The
pre-clean of course removes the object files from the package src/
directory, so the next load_
On 24 June 2021 at 16:31, Duncan Murdoch wrote:
| This does the full compile again, so it's slow.
ccache fixes that (as it has its own cache). It also works on macOS.
Dirk
--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
__
R-pack
On 24/06/2021 3:44 p.m., Gábor Csárdi wrote:
On Thu, Jun 24, 2021 at 8:55 PM Duncan Murdoch wrote:
[...]
A disadvantage of the devtools method is that a regular build after
load_all() seems to do a full 75 sec build: load_all caches things for
itself, but doesn't put them in the same place as
On Thu, Jun 24, 2021 at 8:55 PM Duncan Murdoch wrote:
[...]
> A disadvantage of the devtools method is that a regular build after
> load_all() seems to do a full 75 sec build: load_all caches things for
> itself, but doesn't put them in the same place as a regular build, so
> make doesn't see the
On 24/06/2021 5:15 a.m., Greg Minshall wrote:
hi.
when developing packages, my current work flow is to change the code,
(re-)build the package, detach/load the package, test (to find the
N+1'st bug, sigh).
the building step takes tens of seconds.
is there an obvious way to present some code to
Hi Greg,
On 24 June 2021 at 12:15, Greg Minshall wrote:
| when developing packages, my current work flow is to change the code,
| (re-)build the package, detach/load the package, test (to find the
| N+1'st bug, sigh).
|
| the building step takes tens of seconds.
You may benefit from looking in
Wolfgang,
> You might want to look into the load_all() function from 'devtools'.
thanks very much. that seems to do a great job.
cheers, Greg
__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
-package-devel@r-project.org
>Subject: [R-pkg-devel] speeding up package code/build/test cycle
>
>hi.
>
>when developing packages, my current work flow is to change the code,
>(re-)build the package, detach/load the package, test (to find the
>N+1'st bug, sigh).
>
>the
hi.
when developing packages, my current work flow is to change the code,
(re-)build the package, detach/load the package, test (to find the
N+1'st bug, sigh).
the building step takes tens of seconds.
is there an obvious way to present some code to the R command line and
have it replace the appr
16 matches
Mail list logo
