octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Question about mkoctfile


From: Michael Goffioul
Subject: RE: Question about mkoctfile
Date: Thu, 15 Mar 2007 16:46:16 +0100

On 3/15/07, John W. Eaton <address@hidden> wrote:
On 26-Feb-2007, address@hidden wrote:

| In mkoctfile, any oct file is linked against a bunch of libraries in addition 
to
| liboctave, liboctinterp and libcruft: -lz, -lblas, -lfftw, -lhdf5....
| If the target oct file does not use any symbol of those libs, do they still 
need
| to be specified on the link command line? Or is -loctave, -loctinterp and
| -lcruft enough? (I'm not sure how gcc handle this)

I'm not sure what is correct, but if there is a better way of doing
this that works on all platforms, or platform-specific ways that we
can easily determine at configure time, then I'd consider patches.

The fact is that I don't know how it works on other platforms; this
was more or less what I wanted to know. With MSVC, you only need
to linked against the libs from which you actually use symbols.

I was asking because it could have an impact on the files included
and/or installed by the binary package under Windows (MSVC splits
the DLL and the import library, the latter being used when you want
to linked against it). But maybe I should simply package and install
everything.

Michael.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]