From hin-tak.leung at cimr.cam.ac.uk  Sat Dec 22 20:09:04 2007
From: hin-tak.leung at cimr.cam.ac.uk (Hin-Tak Leung)
Date: Sat, 22 Dec 2007 19:09:04 +0000
Subject: [Rd] SHLIB steps on a Makefile
In-Reply-To: <dba1e14b0712201428n3c55c57fx71de164f3ea50f7@mail.gmail.com>
References: <dba1e14b0712201349t552a9409mb96b1007b3b6a483@mail.gmail.com>	<Pine.LNX.4.64.0712202206210.11123@gannet.stats.ox.ac.uk>
	<dba1e14b0712201428n3c55c57fx71de164f3ea50f7@mail.gmail.com>
Message-ID: <476D60D0.2040706@cimr.cam.ac.uk>

Hmm, I don't think you need a whole Makefile - while it is a
bit complicated to set locations, etc, essentially if your C code
needs an extra DLL (well, you'll have to bundle it with your package,
etc because the otherwise link-loader won't find it), it is mostly
just in Makevars.win

PGK_LDGLAGS=-lotherlib

'compiling against a DLL in a another package' is alright, but resolving 
the DLL at runtime won't be trivial (unless you set explicit dependency 
of your package against this other one) ; so you might be better off 
compiling against a static build of the other with yours.

Iago Mosqueira wrote:
<snipped>
> Many thanks for the information. I am trying to make a package C code
> compile against a DLL already present in another package, so I need to
> include its location in the call to gcc.  I'll see what the most
> portable system could be and will test widely.
> 
> Regards,
> 
> 
> Iago Mosqueira
> 
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel



[Rd] SHLIB steps on a Makefile
Hin-Tak Leung