All-- Does anyone know if the update from R 2.15.2 to 3.0 is likely to change they way these binaries would need to be built? I don't think that the NAMESPACE & .First.lib changes will matter, but I don't understand the implications of long.vectors. http://developer.r-project.org/30update.txt
The 64-bit MSwin binaries of ncdf available from unidata: http://www.unidata.ucar.edu/software/netcdf/win_netcdf/#binaries state that they are set up for use with Visual Studio. I may call in a (big!) favor to have a Visual Studio / C friend work on this with me, and then make the 64-bit MSwin binary available to all, but I don't want to have to do it twice. While I would rather take the easy path & migrate back to linux, I work for the same agency as JohnG and thus am required to use MSwin. Tom 2 On Sat, Feb 9, 2013 at 1:19 PM, JohnG <john_gr...@nps.gov> wrote: > Yep. That's what the developers tell me. I'm grateful they've been > willing > to work on this, saving me the pain. When the one working on this returns, > I'll post more precise info on the issues and error messages. The Unidata > site makes it look simple, but it obviously is not. > > Thanks for having a look! > johng > > > > -- > View this message in context: > http://r-sig-geo.2731867.n2.nabble.com/64-bit-ncdf4-for-Windows-tp7582474p7582549.html > Sent from the R-sig-geo mailing list archive at Nabble.com. > > _______________________________________________ > R-sig-Geo mailing list > R-sig-Geo@r-project.org > https://stat.ethz.ch/mailman/listinfo/r-sig-geo > [[alternative HTML version deleted]] _______________________________________________ R-sig-Geo mailing list R-sig-Geo@r-project.org https://stat.ethz.ch/mailman/listinfo/r-sig-geo
