Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign uprevive? #5
revive? #5
Comments
|
It is alive!! We use it daily at work. i) Windows support I don't need so I don't work much on it. But you may have a point that these days it may just need a rebuild given that we have g++-4.9 in Rtools. Did you try? Can you try? |
|
Now that you mention it ... there is more to it. I did look into it. Apparently last summer. It turns out that we need "real" C++11 and g++-4.9 is ever so close ... but not there. Now, you may just get lucky as we needed similar features in the very recent nanotime package where @dcdillon was mostly kindly working exactly what we need here too. Else maybe just maybe we could get by with But he or she who really needs Windows support should really drive this. We all are mostly just happy on Linux and OS X... |
|
Oh great! I'm currently on a windows machine as my mbp is on the fritz. Happy to help you debug for windows support. I first removed the unix_only and tried to build and got the following:
This corresponds to the following function
As you mentioned, I had seen mention on SO of gmtime_ for a different time parser, however my very very naive attempt on how to override the inline function on windows failed. Any tips on what to try to see to see if mktime00 and gmtime_ are sufficient? I would be happy to poke around, don't know if I'd qualify as a driver in Cpp but if you would be willing to bear with me I can do my best! |
|
Good! So I have a fragment here where I seemingly tried to bring in a But in a very funny way I sort-of re-realized these days that Rcpp actually exports R's reimplementations of |
|
great! so I just tried to install Rcpp from the tip and actuall got a failure (don't know if I should post this to Rcpp repo instead)
I thought it could be my comp, so I grabbed another windows computer and also tried to install
and got the exact same error. Given this gets fixed, when you say just need the linkingTo, you mean that shouldn't need to change the inline function at all, just make sure to have a (working) development version of Rcpp should suffice? |
|
Weird. I just ported that / updated that. I need to look into that. But the good news for you is that the underlying functions have been there "forever". Just use the CRAN version. Just be careful: it is |
|
Ok, that needs a fix and will get it. Lines 1350-ish, that end of the file, needs to be //#ifdef HAVE_TM_GMTOFF
#if ! (defined(__MINGW32__) || defined(__MINGW64__))
tmp->tm_gmtoff = offset;
#endif
//#endif
return tmp;Rest of the tests running now. |
|
attempted fix in PR #6 |
|
And the test fails. Fiddle sticks. So Rcpp is not quite there yet with the change from last week. |
|
well, if you want to ping me on changes, I'm happy to compile and give it a shot any time. |
|
I poked around some more. Looks like Rcpp's master branch was simply a little behind testing standards on Windows; that is the price we pay for not bothering with appveyor on each commit... I should have a handle on this tomorrow with access to my windows vm. As for RcppTOML: Let's do this. Worst case we can build something which may miss one or two features related to dates. But we should have the components. So let's bring this baby to windows. |
|
awesome!! My cursory check looked like the dates parsed ok :-) If it comes to it, I'd also be happy to take the 'burden' of writing up any regression tests if we do run into bug(s) |
Hi Dirk,
I was wondering how difficult it would be to revive this, along with windows support, given the updates to the window toolchain in 3.3+
Is that possible?
I attempted to muck around however C++ is completely out of my league.