On Sat, Jul 25, 2015 at 9:41 AM, Gavin Smith gavinsmith0...@gmail.com
wrote:
I'd suggest not hard-coding the name of the shared library in the Perl
code. It could be extracted from the *.la file. That would likely
improve portability. I don't see any way to avoid looking in .libs.
Thank you
On 28 July 2015 at 16:58, Guillaume Marcais guilla...@marcais.net wrote:
On Sat, Jul 25, 2015 at 9:41 AM, Gavin Smith gavinsmith0...@gmail.com
wrote:
I'd suggest not hard-coding the name of the shared library in the Perl
code. It could be extracted from the *.la file. That would likely
On 24 July 2015 at 20:13, Guillaume Marcais guilla...@marcais.net wrote:
I am improving/writing a C++ project (called MUMmer) which creates a shared
library with libtool. In the same project, I also create a SWIG binding to
access in Perl some of the functionality of this shared library.
Hello all,
I am improving/writing a C++ project (called MUMmer) which creates a shared
library with libtool. In the same project, I also create a SWIG binding to
access in Perl some of the functionality of this shared library.
Libtool creates the shared library in a hidden directory:
