|
Apr
30 |
|
comment |
Creating a cross-compiler environment to build package binaries Thanks for clarifying that Hadley. I'll just got myself some mac hardware for testing purposes and will checkout how everything runs after xcode is available
|
|
Apr
29 |
|
comment |
Creating a cross-compiler environment to build package binaries @DanielFischer: awesome! Haven't thought of virtual machines yet! That's sounds like the best alternative at the moment, thanks! |
|
Apr
29 |
|
comment |
Creating a cross-compiler environment to build package binaries thanks man, I'll give that a try |
|
Apr
29 |
|
comment |
Creating a cross-compiler environment to build package binaries No, that's the thing I hoped to get around. Plus I've read that the Xcode tools aren't free of charge anymore: r-bloggers.com/… |
|
Apr
29 |
|
comment |
Creating a cross-compiler environment to build package binaries Well, I need to correct myself: I didn't try R CMD INSTALL --binary myPkg.tar.gz but used install.packages("path/to/mypkg.tar.gz", type="source") (which failed). That should have the same effect as running R CMD INSTALL, shouldn't it?
|
|
Apr
29 |
|
comment |
Creating a cross-compiler environment to build package binaries @DanielFischer: got it, no problem ;-) |
|
Apr
29 |
|
comment |
Creating a cross-compiler environment to build package binaries By the way: setting up the development tools on windows is absolutely hassle free thanks to Duncan Murdoch's Rtools: cran.r-project.org/bin/windows/Rtools. If you could tell me what I need to do in Mac OS to put everything I need into place, I'd appreciate a pointer. |
|
Apr
29 |
|
comment |
Creating a cross-compiler environment to build package binaries @DanielFischer: Well, first of: thanks for removing the "silly question". Second: I tried giving them a tar.gz of my package, but R complained about something not being the way Mac OS would expect it. Therefore the question.
|
|
Apr
29 |
|
comment |
Creating a cross-compiler environment to build package binaries This something I could use? wiki.osdev.org/GCC_Cross-Compiler |
|
Apr
29 |
|
asked | Creating a cross-compiler environment to build package binaries |
|
Apr
28 |
|
accepted | Avoid server certificate error when posting form via RCurl |
|
Apr
27 |
|
comment |
How to handle dependencies (`Depends:`) of imported packages (`Imports:`) In that respect: can't I tell R explicitly to look in imports:mypkg first, "no matter what" in the sense of "also when calling a package's function that relies on packages that have not been declared as imports in the package's NAMESPACE files"? Because mypkg would take care of importing the dependency, so its functions would actually be available in imports:mypkg
|
|
Apr
27 |
|
comment |
How to handle dependencies (`Depends:`) of imported packages (`Imports:`) Ahhh, okay! Thanks for the pointer! One more question though: when my functions call functions in packages that my package imports, do I need to do anything special to tell R "hey, look in the imports:mypkg environment first before going to the search path" (e.g. by using ::) or does R figure that out itself?
|
|
Apr
27 |
|
comment |
How to handle dependencies (`Depends:`) of imported packages (`Imports:`) I carried out the actual import via import(imported.pkg) and import(digest) in my NAMESPACE file (entire packages), that should do as well, shouldn't it? If something failed, there would also be no digest in the imports:mypkg environment - which there is.
|
|
Apr
27 |
|
asked | How to handle dependencies (`Depends:`) of imported packages (`Imports:`) |
|
Apr
27 |
|
awarded | Popular Question |
|
Apr
19 |
|
awarded | Tumbleweed |
|
Apr
18 |
|
revised |
How do I set the Java path in Eclipse so I can run it on an external drive? added 466 characters in body |
|
Apr
18 |
|
answered | How do I set the Java path in Eclipse so I can run it on an external drive? |
|
Apr
15 |
|
revised |
Include code in Inno Setup script that copies files to specifiable target directory added 533 characters in body |
