R.app 1.51 for R 2.15.0

git-svn-id: https://svn.r-project.org/R-packages/trunk/Mac-GUI@6148 694ef91d-65df-0310-b7bb-92e67a308ead

InfoPlist.h

@@ -8,9 +8,9 @@
  */
 
 /* GUI version as shown in infos e.g. 1.27-devel */
-#define GUI_VER 1.51-dev
+#define GUI_VER 1.51
 /* R postfix used to denote release versions of GUI - set to R release version (e.g. 2.8.0) or to anything that will be shown in between R and GUI (e.g. - or for Mac) */
-#define R_RELEASE for Mac OS X
+#define R_RELEASE 2.15.0
 
 #if LEOPARD_CFG
 #define CFG_NAME Leopard build 32-bit

NEWS

@@ -1,5 +1,11 @@
 NEWS for R.app GUI for Mac OS X
 
+-- Release Version 1.51 (6148) - supplied with R 2.15.0 --
+
+Last-update: 2012-03-02 [HJBB]
+*	Fixes for Lion (among others drag-n-drop while R.app is not
+	running) and performance updates
+
 -- Release Version 1.50 (6126) - supplied with R 2.14.2 --
 
 Last-update: 2012-02-22 [HJBB]

R.xcodeproj/project.pbxproj

@@ -1119,7 +1119,6 @@
 			isa = PBXProject;
 			buildConfigurationList = 680F0B3A0997CE66009CDBE8 /* Build configuration list for PBXProject "R" */;
 			compatibilityVersion = "Xcode 2.4";
-			developmentRegion = English;
 			hasScannedForEncodings = 1;
 			knownRegions = (
 				English,

docs/RMacOSX-FAQ.texi

@@ -4,9 +4,9 @@
 @settitle R for Mac OS X FAQ
 @setchapternewpage on
 @set FAQ-YEAR 2012
-@set FAQ-VERSION 2.14-2 @value{FAQ-YEAR}-02-29
-@set REL-VERSION 2.14.2
-@set GUI-VERSION 1.50
+@set FAQ-VERSION 2.15-0 @value{FAQ-YEAR}-03-30
+@set REL-VERSION 2.15.0
+@set GUI-VERSION 1.51
 @documentlanguage en
 @documentencoding ISO-8859-1
 @c %**end of header
@@ -194,7 +194,9 @@ R installer since version 2.7.0 attempts to detect and resolve the above problem
 
 If you have a clean, recent Mac OS X (10.5 Leopard or 10.6 Snow Leopard) and want quick instructions how to build your own R binary, read this section. In all other cases please read the details in the following sections.
 
-First, you need to install developer tools - that is Xcode 3.1 for Mac OS X 10.5 (Leopard) or Xcode 3.2 for Mac OS X 10.6 (Snow Leopard). Xcode is present on the OS X installation DVD or can be downloaded from @uref{http://developer.apple.com/mac/}. Then download the matching FORTRAN compiler from @uref{http://R.research.att.com/tools/}.
+First, you need to install developer tools - that is Xcode 3.1 for Mac OS X 10.5 (Leopard) or Xcode 3.2 for Mac OS X 10.6 (Snow Leopard) or any higher version. Xcode is present on the OS X installation DVD (where applicable) or can be downloaded from @uref{http://developer.apple.com/mac/}. Then download the matching FORTRAN compiler from @uref{http://R.research.att.com/tools/}.
+
+Xcode 4.3 and higher (available for Mac OS X 10.7 and higher) no longer installs command line tools in the system location, they need to be downloaded and installed separately. Look for ``Command Line Tools for Xcode'' at the Apple's Developer site or in the App Store. Alternatively it is also possible to add the full path to the tools present inside the Xcode application to the @code{PATH} environment variable (recommended only for advanced users since it is a bit tricky to get it right).
 
 Optionally you can also install TeX (@uref{http://www.tug.org/mactex/}) to build documntation. You can pick useful external libraries from @uref{http://r.research.att.com/libs/} (such as readline, libpng, jpeg) but they are not required. You can install them using the Terminal (in Application/Utilities) for example:
 
@@ -207,16 +209,16 @@ Download, configure and build R. In the following we assume you have an Intel-ba
 
 @smallexample
 # download R
-curl -O http://cran.r-project.org/src/base/R-2/R-2.14.0.tar.gz
+curl -O http://cran.r-project.org/src/base/R-2/R-2.15.0.tar.gz
 # unpack R
-tar fxz R-2.14.0.tar.gz
+tar fxz R-2.15.0.tar.gz
 # choose the architecture (x86_64, i386, ppc or ppc64)
 arch=x86_64
 # create a build directory
 mkdir R-$arch
 cd R-$arch
 # configure R
-../R-2.14.0/configure r_arch=$arch  CC="gcc -arch $arch" \
+../R-2.15.0/configure r_arch=$arch  CC="gcc -arch $arch" \
      CXX="g++ -arch $arch" F77="gfortran -arch $arch" \
      FC="gfortran -arch $arch" OBJC="gcc -arch $arch" \
      --x-includes=/usr/X11/include --x-libraries=/usr/X11/lib \
@@ -259,6 +261,10 @@ The requirements for building @R{} vary, depending whether the build machine is
 @node C/C++ compiler (gcc 3.3 or later), Fortran compiler (g77 3.3 or later), What is needed to build R, What is needed to build R
 @subsection C/C++ compiler (gcc 3.3 or later)
 
+If you have Mac OS X 10.7 (Lion) or higher and Xcode 4.3 or higher, you will need to install ``Command Line Tools for Xcode``. Those are available from the Apple Mac Developer website or the App Store. Xcode alone is no longer sufficient because with Xcode 4.3 Apple has removed the capability of Xcode to install system-wide command line tools.
+
+Note that some versions of Xcode 4.2 and higher no longer include @code{gcc-4.2} in the Xcode installation, so you may have to use llvm gcc or clang instead.
+
 If you have Mac OS X 10.3 (aka Panther) or higher you just need to install the software from the Xcode Tools CD or DVD. This is only true if you bought retail version of Mac OS X. If your computer came with pre-installed version of OS X, look into @file{/Applications/Installers}. Recent installations feature @file{Xcode Tools} folder containing the necessary installer. If neither of the above works for you, download Xcode from @uref{http://developer.apple.com/tools/xcode/}.
 
 If you are using Mac OS X 10.2 (aka Jaguar) then you should download and install the 
@@ -332,7 +338,7 @@ Mac OS X 10.2 (Jaguar) does not include X11 installer. However, there are two op
 @node Cairo graphics library (optional), X11 TclTk headers and libraries (optional), X11 window server (optional), What is needed to build R
 @subsection Cairo graphics library (optional)
 
-R 2.7.0 and later include support for cairo graphics library as one of the options in X11 support. Mac OS X does not include cairo library, therefore we have to build our own. In order to simplify the distribution, we use a static build of cairo. Therefore the library is not needed at run time as it's already part of R. However, if you want to compile R, you can obtain the same binary we use for the release from @uref{http://r.research.att.com/devpack4-darwin8-bin4.tar.gz}. Read more on CRAN in the ``tools'' directory.
+R 2.7.0 and later include support for cairo graphics library as one of the options in X11 support. Mac OS X does not include cairo library, therefore we have to build our own. In order to simplify the distribution, we use a static build of cairo. Therefore the library is not needed at run time as it's already part of R. However, if you want to compile R, you can obtain the same binary we use for the release from @uref{http://r.research.att.com/libs/}. Read more on CRAN in the ``tools'' directory.
 
 In general cairo grapics library can be obtained from @uref{http://www.cairographics.org/}. More recent versions can use either native ATSUI/Quartz font back-end or FreeType. If the latter is used, make sure you get the most recent (even development) version available, because there are known bugs in FreeType with respect to Mac font support.
 
@@ -394,11 +400,11 @@ Mac@TeX{} (@uref{http://www.tug.org/mactex/}) is a more recent alternative, but
 @node How to configure and build R, How to install R, What is needed to build R, Building R from sources
 @section How to configure and build R
 Download the latest sources of R from @CRAN{} or fetch them using SVN. Unpack the archive with tar -zxf @emph{name_of_R_sources_archive} and cd
-inside the R sources directory. Then you need to configure R for your system and build R. It is recommended to use separate directory for building from the sources. For example if you unpackged @R{} as R-2.14.0 type:
+inside the R sources directory. Then you need to configure R for your system and build R. It is recommended to use separate directory for building from the sources. For example if you unpackged @R{} as R-2.15.0 type:
 @example
 mkdir build
 cd build
-../R-2.14.0/configure
+../R-2.15.0/configure
 make
 @end example
 This will configure R to be built as a Framework to be installed inside your @emph{/Library/Frameworks} directory with the name @emph{R.framework}. @code{make} will compile R. Such compiled @R{} can already be used by running the @code{bin/R} script.
@@ -475,12 +481,12 @@ In addition, the compilers must support both architectures as well. You will nee
 
 The next step is to build a binary for each architecture. This can be either done natively on two machines - one PowerPC and one Intel based Mac, or by cross-compiling the PowerPC part on an Intel Mac. In either case, the configuration is the same.
 
-Configure, build and install the @samp{ppc} binary (assuming @samp{R-2.14.0.tar.gz} is in the current directory, replace @samp{R-2.14.0} with any other version or name as appropriate):
+Configure, build and install the @samp{ppc} binary (assuming @samp{R-2.15.0.tar.gz} is in the current directory, replace @samp{R-2.15.0} with any other version or name as appropriate):
 @example
-tar fxz R-2.14.0.tar.gz
+tar fxz R-2.15.0.tar.gz
 mkdir R-ppc
 cd R-ppc
-../R-2.14.0/configure r_arch=ppc CC="gcc -arch ppc" \
+../R-2.15.0/configure r_arch=ppc CC="gcc -arch ppc" \
 CXX="g++ -arch ppc" F77="gfortran -arch ppc" \
 FC="gfortran -arch ppc" OBJC="gcc -arch ppc"
 make
@@ -493,7 +499,7 @@ Depending on your permissions, you may need to run @samp{sudo make install}. The
 @example
 mkdir R-i386
 cd R-i386
-../R-2.14.0/configure r_arch=i386 CC="gcc -arch i386" \
+../R-2.15.0/configure r_arch=i386 CC="gcc -arch i386" \
 CXX="g++ -arch i386" F77="gfortran -arch i386" \
 FC="gfortran -arch i386" OBJC="gcc -arch i386"
 make
@@ -517,7 +523,7 @@ to default to the current native architecture. It addition, it may be a good ide
 
 To run a specific architecture use the @samp{--arch} flag when starting @R{}, e.g., @samp{R --arch x86_64} for 64-bit R on Intel platform.
 
-Starting with R 2.10.0 installations on Mac OS X 10.6 (Snow Leopard) default to 64-bit if the host CPU supports is. All other installations use the native platform type (which is 32-bit in most cases).
+Starting with R 2.10.0 CRAN installations on Mac OS X 10.6 (Snow Leopard) default to 64-bit if the host CPU supports is. All other installations use the native platform type (which is 32-bit in most cases).
 
 @node Command line version of R, R.app, Building R from sources, Top
 @chapter Command line version of R
@@ -1387,7 +1393,7 @@ In some recent versions of R there is a conflict between the history of R itself
 
 When executing system commands (for example directly via @code{system} or indirectly via functions that call other programs such as @code{install.packages}) the locations in which the shell is looking for programs is governed by the @code{PATH} environment variable. That variable may be set differently for R started from an interactive shell and for R started in the GUI. You can use @code{Sys.getenv("PATH")} to verify the current setting.
 
-When R is started from a shell (e.g., on the command line of the Terminal), it will inherit settings from that shell. Those are typically modified by shell-specific configuration files, such as @code{.profile} or @code{.bashrc}. Those apply only to the shell, not to the system as a whole. In addition, some installers (such as MacTeX) will modify global shell settings to make user's life more comfortable on the command line, but, again, those do not apply to programs not started from the shell - such as GUIs.
+When R is started from a shell (e.g., on the command line of the Terminal), it will inherit settings from that shell. Those are typically modified by shell-specific configuration files, such as @code{.profile} or @code{.bashrc}. Those apply only to the shell, not to the system as a whole. In addition, some installers (such as MacTeX) will modify global shell settings to make user's life more comfortable on the command line, but, again, those do not apply to programs not started from the shell - such as GUIs. See @uref{http://developer.apple.com/library/mac/#qa/qa1067, Apple Technical Q&A QA1067} for what Apple says about the topic.
 
 In order to standardize your @code{PATH} setting in R, you can set it in your @code{.Renviron} file (in your home - see @code{?Startup} in R for details on how R uses configuration files on startup). This setting will apply to R regardless of how it is started. You can also add more elaborate constructs to @code{.Rprofile} instead if you wish to selectively modify the existing @code{PATH} variable via @code{Sys.getenv} and @code{Sys.setenv}.