[Top][All Lists]

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

[Octave-bug-tracker] [bug #42002] pkg/mkoctfile need to support '-framew

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #42002] pkg/mkoctfile need to support '-framework' flags; patch supplied
Date: Mon, 31 Mar 2014 18:38:41 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20100101 Firefox/17.0

Update of bug #42002 (project octave):

                  Status:                    None => Need Info              


Follow-up Comment #3:

First off, I'm not a Mac user, but I understand that -framework is Apple's way
of linking libraries, that's fine.

Wouldn't something like BLAS, or vecLib in this case, already be known to
Octave so it should already be linked in as an implicit link dependency of all
future calls to mkoctfile? What's the interaction between linking Octave with
vecLib, using the link-all-deps option, and using mkoctfile to build

What Octave Forge packages rely on passing "-framework vecLib" to mkoctfile to
install? Or is this added to the build as a Mac packaging thing?

Or are you just using vecLib as an example, but maybe a user would be building
an oct-file and linking with some *other* framework that Octave doesn't know

Just trying to understand the actual use case that results in this bug. For
example, if I had to somehow pass -lblas to a pkg install command on Linux, I
would consider that a bug in the build system for oct-files and packages. The
mkoctfile command should automatically link in all dependency libraries (or
frameworks) that Octave was built with.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

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