This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Packaging lapack, blas, etc

James R. Phillips schrieb:
I am looking at packaging numerical libraries such as lapack and blas for use
by a cygwin version of gnu octave.  I would like some guidance on a couple

I would a bit with a release until the gcc-3.4 dwarf2 EH problems (performance degradation with new libstdc++ exceptions) are settled. Shouldn't be that far anymore.
See the octave or gcc list on known octave issues.

1) I anticipate developing the libraries in a dll format, and there may be
multiple versions, optimized for different processor architecture.  What is the
best way to support (ie select from) multiple installed library versions at run
time?  Simply make certain the correct version is copied to /usr/bin, or add
the path to the correct version to the $PATH environmental string?  Or
something else?

To /usr/bin if you depend on them on startup.
However as it looks like, if you demand-load (dlopen) them later after doing some cpu detection, you can put them anywhere, preferably into /usr/lib/<package> or /usr/libexec/<package>
Reini Urban

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]