The R Project SVN R

Rev

Rev 75092 | Rev 88498 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 75092 Rev 75653
Line 28... Line 28...
28 
  \command{R CMD SHLIB} can both compile and link files into a
 28 
  \command{R CMD SHLIB} can both compile and link files into a
29 
  shared object: since it knows what run-time libraries are needed
 29 
  shared object: since it knows what run-time libraries are needed
30 
  when passed C++, Fortran and Objective C(++) sources, passing source
 30 
  when passed C++, Fortran and Objective C(++) sources, passing source
31 
  files to \command{R CMD SHLIB} is more reliable.
 31 
  files to \command{R CMD SHLIB} is more reliable.
32 
 
 32 
 
33 
  Ratfor is not supported.  If you have Ratfor source code, you need to
 - 
 
34 
  convert it to FORTRAN.  (On some Solaris systems mixing Ratfor and
 - 
 
35 
  FORTRAN code will work.)
 - 
 
36 
 
 - 
 
37 
  Objective C and Objective C++ support is optional and will work only
 33 
  Objective C and Objective C++ support is optional and will work only
38 
  if the corresponding compilers were available at \R configure time:
 34 
  if the corresponding compilers were available at \R configure time:
39 
  their main usage is on macOS.
 35 
  their main usage is on macOS.
40 
 
 36 
 
41 
  Compilation arranges to include the paths to the \R public C/C++ headers.
 37 
  Compilation arranges to include the paths to the \R public C/C++ headers.