similar to: Seeking advice regarding compilation of large libraries using RTools (Windows)

Yep - simpleITK is available at github.com/SimpleITK/SimpleITK. There's also github.com/SimpleITK/SimpleITKRInstaller - a devtools based installer for mac and linux. CMake has a range of build environments. I experimented with MSYS2 and mingw makefiles, but had trouble with incompatibilities in the path required by CMake and those options - from memory the sh in RTools/bin caused problems.

On Mon, Mar 6, 2017 at 8:21 PM, Richard Beare <richard.beare at gmail.com> wrote: > Yep - simpleITK is available at github.com/SimpleITK/SimpleITK. There's > also github.com/SimpleITK/SimpleITKRInstaller - a devtools based installer > for mac and linux. > > CMake has a range of build environments. I experimented with MSYS2 and > mingw makefiles, but had trouble with

On Mon, Mar 6, 2017 at 6:33 AM, Richard Beare <richard.beare at gmail.com> wrote: > I am working on the SimpleITK package for R. This is an enormous package > that is largely automatically generated via a set of swig/json/lua magic, > and is working well under linux and osx. Is it available somewhere so we can try it? > However we're having a lot of trouble with the

My apologies for cross-posting. I found this site, after I had posted on stack-overflow. I need to compile several static libraries (C & Fortran) which will later be linked with an R package. Rtools33 directory includes /i686-w64-mingw32 directory which I understand creates 32 bit binaries. Yet, there are other 64 bit directories as well. I have three related questions: 1. Can

I have just uploaded to CRAN a new version 3.2.0.1948 of Rtools for Windows. This will become visible there in a few hours, and be copied to mirrors thereafter. People who want to build packages that include compiled code can use this to supply the compilers, etc., that are necessary for the build. It also includes some extra materials for people who want to build R itself. This version

On 07/01/2015 5:20 PM, Jeroen Ooms wrote: > On Wed, Jan 7, 2015 at 8:00 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> >> This version includes only minor updates to the tools. I indicated last summer that I was hoping to update GCC from the current version 4.6.3 before the R 3.2.0 release, but this now looks unlikely, unless someone else with experience building

Hi, If I am not mistaken, all Rtools 4.2 (and 4.3) revisions have the same ARP [1] entries, i.e. all report version 4.2.0.1 (or 4.3.0.1). This makes it difficult to determine the installed version (is it possible to determine the installed revision?) and impossible for tools like winget [2] to update Rtools to the latest revision, AFAICT. Would it be possible to track the version in the

Very timely, as this is how I got into the problem I posted about earlier; maybe some of the problems I ran into will mean more to the you and the experts on this thread, Dr. Murdoch.For reference, I run Windows 7 64bit, and I am trying to build a 64 bit version of R-3.1.2. As we discussed offline, Dr. Murdoch, I've been trying to build R using more recent tools than GCC4.6.3 prerelease.

(Excerpts only). On Sat, Aug 3, 2019 at 12:48 AM Jeroen Ooms <jeroenooms at gmail.com> wrote: > > I'm assuming that Python is required to build R packages, on all operating > > systems. > Please don't assume but read the documentation (preferably before posting). I can't find one reference to Python in the documentation:

Oh, I forgot to mention that besides setting AR, RANLIB and the stack probing fix, you also need a very up to date binutils. 2.25 was out in december. Even with that , if you linker's default is not what you are compiling for (i.e. a multiarch toolchain), you need to set GNUTARGET also, i.e. -m32/-m64 is not enough. Some fix to autodetect non-default targets went in after christmas before the

On Fri, Feb 9, 2018 at 2:16 AM, Indrajit Sen Gupta <indrajitsg at gmail.com> wrote: > Hi Avraham, > > A quick question - I realized I did not have Perl installed. So I installed > ActiveState Perl right now. Also I see I need texinfo and texi2any. I was > able to installed texinfo from here: > http://gnuwin32.sourceforge.net/packages/texinfo.htm. But not sure where to >

On Fri, Feb 9, 2018 at 9:29 AM, Kenny Bell <kmbell56 at gmail.com> wrote: > I suggest that you work off the build process in the rwinlib repository so > you are starting from something that you know works and already incorporates > the set of dependencies you need. Hello, Kenny. For what it's worth I've been successfully building R+OpenBLAS on Windows64 since 2013, which

On 30/05/2015 13:14, Duncan Murdoch wrote: > On 29/05/2015 4:16 PM, Sue McDonald wrote: >> My apologies for cross-posting. I found this site, after I had posted on >> stack-overflow. >> >> I need to compile several static libraries (C & Fortran) which will later >> be linked with an R package. Rtools33 directory includes /i686-w64-mingw32 >> directory

On Wed, Jan 7, 2015 at 8:00 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > > This version includes only minor updates to the tools. I indicated last summer that I was hoping to update GCC from the current version 4.6.3 before the R 3.2.0 release, but this now looks unlikely, unless someone else with experience building it can help. I have been looking into this a bit over

On 2015-01-08 02:31, Duncan Murdoch wrote: > On 07/01/2015 5:20 PM, Jeroen Ooms wrote: >> On Wed, Jan 7, 2015 at 8:00 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >>> >>> This version includes only minor updates to the tools. I indicated last summer that I was hoping to update GCC from the current version 4.6.3 before the R 3.2.0 release, but this now

Hi, I am trying to compile R with ICU support. I am following https://cran.r-project.org/doc/manuals/R-admin.html#Building-from-source I have downloaded and extracted https://www.stats.ox.ac.uk/pub/Rtools/goodies/ICU_531.zip to W:\R-3.5._\App\R-Portable\ICU I have modified MkRules.local # set to use ICU USE_ICU = YES # path to parent of ICU headers ICU_PATH = w:/R-3.5._/App/R-Portable/ICU I

On Fri, Jan 9, 2015 at 12:19 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > On 09/01/2015 10:56 AM, Henric Winell wrote: >> On 2015-01-08 02:31, Duncan Murdoch wrote: >> >>> On 07/01/2015 5:20 PM, Jeroen Ooms wrote: >>>> On Wed, Jan 7, 2015 at 8:00 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >>>>>

On Tue, Feb 13, 2018 at 12:22 PM, Indrajit Sen Gupta <indrajitsg at gmail.com> wrote: > Hi Avraham, > > I tried with the patched version. The same error message. > > gcc -std=gnu99 -m64 -shared -s -mwindows -o R.dll R.def console.o dynload.o > editor.o embeddedR.o extra.o malloc.o opt.o pager.o preferences.o psignal.o > rhome.o rt_complete.o rui.o run.o shext.o

The r.dll crash is easy - you need to be using gcc-ar for ar, and gcc-ranlib for ranlib. I also posted a patch to fix the check failure for stack probing, as lto optimizes away the stack probing code, as it should. yes, lto build's speed gain is very impressive. ------------------------------ On Thu, Jan 8, 2015 2:01 PM GMT Henric Winell wrote: >On 2015-01-08 14:18, Avraham Adler

On Thu, Jan 8, 2015 at 10:48 AM, Hin-Tak Leung <htl10 at users.sourceforge.net> wrote: > > The r.dll crash is easy - you need to be using gcc-ar for ar, and gcc-ranlib for ranlib. I also posted a patch to fix the check failure for stack probing, as lto optimizes away the stack probing code, as it should. > > yes, lto build's speed gain is very impressive. > > I