It is possible to do things like env PKG_LIB="-L/opt/foo/lib -lbar" R CMD SHLIB *.c to add libraries to the creation of a shared object, but I have from time to time wondered if we should allow R CMD SHLIB *.c -L/opt/foo/lib -lbar not least as users seems to expect it to work. It looks simple to do (at least under Unix) if we pass -L* -l* *.a directly to the link command. Would this be worthwhile? -- Brian D. Ripley, ripley at stats.ox.ac.uk Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595
On Tue, 16 May 2006, Prof Brian Ripley wrote:> It is possible to do things like > > env PKG_LIB="-L/opt/foo/lib -lbar" R CMD SHLIB *.c > > to add libraries to the creation of a shared object, but I have from time > to time wondered if we should allow > > R CMD SHLIB *.c -L/opt/foo/lib -lbar > > not least as users seems to expect it to work. It looks simple to do (at > least under Unix) if we pass -L* -l* *.a directly to the link command. > > Would this be worthwhile?Yes. My only reservation is that users may then expect all compiler/linker flags to work, not just -L/-l -thomas Thomas Lumley Assoc. Professor, Biostatistics tlumley at u.washington.edu University of Washington, Seattle