In the introduction to his book R packages, Hadley Wickham provides a neat function for making sure that everything is set for writing your own R extensions, by simply running the
devtools::has_devel(), which, if all goes well, should evaluate to
This did not work out for me and I had to fix this problem on 2 different occasions so I felt I need to share this info in case there are others also stumped by this hurdle.
The fix I found – after a full sweaty day – was in this conversation on GitHub and I would like to break it down very quickly:
- Make sure you have installed Rtools from CRAN
- Make sure that Rtools/bin as well as Rtools/MinGW/x64/ are added to your system PATH (if you don’t know how, click here)
- In addition, it is recommended that you install LATEX (the link is also found on the Rtools page mentioned on No. 1)
- Run the following lines of code
install_github("hadley/devtools") # to get the latest 'pre-CRAN' package updates
has_devel() # output should be TRUE
Like I said, I had this problem on 2 different machines (Windows 7 and 10) and the same fix worked on both of them.
Well, I just have to share this with whosoever is desperately looking for a solution to this problem and happens to stumble across this post.
It’s not easy being a newbie in any thing, and computing is no exception.
I have written a small program that I will be using for my work in the office and which would also benefit a few staffers. I wrote it in C++ and compiled it using Visual Studio. However, I couldn’t find the executable file (*.exe) anywhere on my computer!
I went over to the MSDN site, as well as StackOverflow, looking for a solution but there was none in sight. To make matters worse, I discovered that MANY beginner programmers were facing the same issue.
Then I found this video on YouTube – and voilá! – problem solved. The answer to my question is ridiculously straightforward; indeed, ignorance is very costly.
If you’re in a bind like I was, I hope this works for you the way it did for me!
This is a good blog. I use IDEs, but my take on them is this: It makes a lot of sense for learners to start with manual before moving on to automatic, because the day you’re forced to drive manual, you may find yourself unable to do so.
IDEs are simply programs to write programs. They are generally editing environments with tools
to help programmers write code quickly and efficiently. As an example, we can create PHP-driven
web applications using a combination of Eclipse and PHPEclipse. Core features typically include:
• Code completion or code insight: The ability of an IDE to know a language’s
keywords and function names is crucial. The IDE may use this knowledge to do such
things as highlight typographic errors, suggest a list of available functions based on the
appropriate situation, or offer a function’s definition from the official documentation.
• Resource management: When creating applications, languages often rely on
certain resources, like library or header files, to be at specific locations. IDEs
should be able to manage these resources. An IDE should be aware of any required
resources so that errors can be spotted at the development stage and not…
View original post 485 more words