On Monday, 26 June 2017 at 13:10:17 UTC, bachmeier wrote:
>
> Thanks for giving it a try. I have a feeling that this is a job for Dub, SCons, or more likely, an R package that figures out this stuff. Windows development seems to have more moving parts. An R package on Linux requires adding a Makefile with one line.

I don't know how well dub will handle it as my dub projects never get this complicated. I haven't used SCons, but might make sense. Reggae is another choice (though I haven't used that either).

On Mon, 2017-06-26 at 16:30 +0000, jmh530 via Digitalmars-d wrote:
> 
[…]
> I don't know how well dub will handle it as my dub projects never get this complicated. I haven't used SCons, but might make sense. Reggae is another choice (though I haven't used that either).

Although I have been quite involved with SCons for a while, I am not
sure it is the future of build. Systems such as Meson/Ninja are much
nicer to work with.  Reggae is very much in the same camp as Meson. The
difference is that Meson has a big community giving it traction.

-- 
Russel. ============================================================================= Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder@ekiga.net 41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel@winder.org.uk London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder

On Monday, 26 June 2017 at 12:20:02 UTC, jmh530 wrote:

[...]
> I might make another effort on this after work if I have time.

I think this will be fairly easily handled within the embedr R package. I should be able to put R.lib inside the package. R knows where to find R.dll. The only thing that remains is to find the LDC installation. I don't know how to automate that, but the user could give the path as input.

I'll post here after updating and testing the embedr package.

On Tuesday, 27 June 2017 at 02:38:31 UTC, bachmeier wrote:
>
> I'll post here after updating and testing the embedr package.

Great. I'll give it a go again when it's ready.

On Tuesday, 27 June 2017 at 02:40:37 UTC, jmh530 wrote:
> On Tuesday, 27 June 2017 at 02:38:31 UTC, bachmeier wrote:
>>
>> I'll post here after updating and testing the embedr package.
>
> Great. I'll give it a go again when it's ready.

You can try this:
https://bitbucket.org/bachmeil/embedrwin

It's not in any sense a release. This is for early testing and everything will be added to embedr in the future. It works for me, so hopefully it will work for you.

On Tuesday, 27 June 2017 at 02:40:37 UTC, jmh530 wrote:
> On Tuesday, 27 June 2017 at 02:38:31 UTC, bachmeier wrote:
>>
>> I'll post here after updating and testing the embedr package.
>
> Great. I'll give it a go again when it's ready.

An update. It looks like I will be able to get all of my research programs to work on Windows. It might be easier to use D in R packages on Windows than to use C/C++/Fortran because there is no need to mess with R tools, which many end users find confusing. The final piece of the puzzle would be an LDC installer for Windows that puts it in the path. Then it would definitely be easier to use D than C/C++/Fortran.

On Friday, 30 June 2017 at 20:36:47 UTC, bachmeier wrote:
>
> An update. It looks like I will be able to get all of my research programs to work on Windows. It might be easier to use D in R packages on Windows than to use C/C++/Fortran because there is no need to mess with R tools, which many end users find confusing. The final piece of the puzzle would be an LDC installer for Windows that puts it in the path. Then it would definitely be easier to use D than C/C++/Fortran.

Cool. I still need to give embedrwin a try...

On Friday, 30 June 2017 at 20:36:47 UTC, bachmeier wrote:
> On Tuesday, 27 June 2017 at 02:40:37 UTC, jmh530 wrote:
>> On Tuesday, 27 June 2017 at 02:38:31 UTC, bachmeier wrote:
>>>
>>> I'll post here after updating and testing the embedr package.
>>
>> Great. I'll give it a go again when it's ready.
>
> An update. It looks like I will be able to get all of my research programs to work on Windows. It might be easier to use D in R packages on Windows than to use C/C++/Fortran because there is no need to mess with R tools, which many end users find confusing. The final piece of the puzzle would be an LDC installer for Windows that puts it in the path. Then it would definitely be easier to use D than C/C++/Fortran.

I just gave it a try. Got an error. As far as I can tell, the problem is that my user name has a space in it (firstname[space]lastname).

> library(embedrwin)
> setwd("C:\\test\\")
> compile("librtest", "C:\\D\\ldc2\\ldc2-1.3.0-beta1-win64-msvc\\bin")
[1] "\"C:\\D\\ldc2\\ldc2-1.3.0-beta1-win64-msvc\\bin\\ldmd2.exe\" -shared -m64 librtest.d C:/Users/firstname[space]lastname/Documents/R/win-library/3.3/embedrwin\\embedrwin\\r.d -version=inline R.lib"
[1] "Error: module firstname is in file 'C:\\Users\\firstname.d' which cannot be read"
[2] "import path[0] = C:\\D\\ldc2\\LDC2-1~1.0-B\\bin\\..\\import\\ldc"
[3] "import path[1] = C:\\D\\ldc2\\LDC2-1~1.0-B\\bin\\..\\import"
attr(,"status")
[1] 1
Error in inDL(x, as.logical(local), as.logical(now), ...) :
  unable to load shared object 'C:/test/librtest.dll':
  LoadLibrary failure:  The specified module could not be found.
In addition: Warning messages:
1: In file.copy(paste0(loc, "/embedr/R.lib"), getwd()) :
  problem copying C:\Users\firstname[space]lastname\Documents\R\win-library\3.3\embedrwin\embedr\R.lib to C:\test\R.lib: No such file or directory
2: running command '"C:\D\ldc2\ldc2-1.3.0-beta1-win64-msvc\bin\ldmd2.exe" -shared -m64 librtest.d C:/Users/firstname[space]lastname/Documents/R/win-library/3.3/embedrwin\embedrwin\r.d -version=inline R.lib' had status 1

On Tuesday, 4 July 2017 at 03:41:35 UTC, jmh530 wrote:

> I just gave it a try. Got an error. As far as I can tell, the problem is that my user name has a space in it (firstname[space]lastname).
>
>> library(embedrwin)
>> setwd("C:\\test\\")
>> compile("librtest", "C:\\D\\ldc2\\ldc2-1.3.0-beta1-win64-msvc\\bin")
> [1] "\"C:\\D\\ldc2\\ldc2-1.3.0-beta1-win64-msvc\\bin\\ldmd2.exe\" -shared -m64 librtest.d C:/Users/firstname[space]lastname/Documents/R/win-library/3.3/embedrwin\\embedrwin\\r.d -version=inline R.lib"
> [1] "Error: module firstname is in file 'C:\\Users\\firstname.d' which cannot be read"
> [2] "import path[0] = C:\\D\\ldc2\\LDC2-1~1.0-B\\bin\\..\\import\\ldc"
> [3] "import path[1] = C:\\D\\ldc2\\LDC2-1~1.0-B\\bin\\..\\import"

Thanks. I forgot a pair of quotes.

It's probably better to file issues on Bitbucket or use Gitter[1] if possible. Or send an email to me at the address here[2]. Someone will get upset with me for using this mailing list for my package.

[1] https://gitter.im/dlang-embedr/Lobby
[2] http://www.k-state.edu/economics/staff/bios/bachmeier.html