On Jan 3, 2007, at 15:36, Kevin Ballard wrote:
In addition, the Mozilla project has a script (unfortunately I
forget the exact name) which takes 2 single-architecture trees and
combines them via lipo. It creates a new tree that contains all
files that are the same in the 2 old trees. Any d
On 3 Jan, 2007, at 18:02, Dr. Ernie Prabhakar wrote:
I'd be interested! It would nice if we could figure out some way
to semi-automate at least part of that process...
The python library macholib can do this as well. It includes the tool
macho_standalone that copies non-system libraries i
In addition, the Mozilla project has a script (unfortunately I forget
the exact name) which takes 2 single-architecture trees and combines
them via lipo. It creates a new tree that contains all files that are
the same in the 2 old trees. Any differing files that are binaries it
combines via
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dr. Ernie Prabhakar wrote:
> I'd be interested! It would nice if we could figure out some way to
> semi-automate at least part of that process...
>
> On Jan 2, 2007, at 11:06 PM, John Labovitz wrote:
>
>> I've successfully used a combination of lipo
I'd be interested! It would nice if we could figure out some way to
semi-automate at least part of that process...
On Jan 2, 2007, at 11:06 PM, John Labovitz wrote:
I've successfully used a combination of lipo(1) and
install_name_tool(1) to build universal versions of MacPorts
libraries (
I've successfully used a combination of lipo(1) and install_name_tool
(1) to build universal versions of MacPorts libraries (built on
separate PPC/Intel machines, alas) so that everything the app needed
lived in /Contents/Frameworks. I used install_name_tool to
change any links to, eg, /opt
On Jan 2, 2007, at 5:41 PM, Jordan K. Hubbard wrote:
On Jan 2, 2007, at 2:08 PM, Kevin Ballard wrote:
If you're going to distribute software, you don't want to build it
with macports (because all the linker paths will be absolute and
pointing at /opt/local, which is not how you want to dist
well, i'm already distributing binaries that gets compiled/linked
against /usr/local/ libraries. with those libs bundled in the app. so i
guess my binaries gets linked in a way they do not keep absolute paths
to libs.
Kevin Ballard wrote:
If you're going to distribute software, you don't wan
On Jan 2, 2007, at 2:08 PM, Kevin Ballard wrote:
If you're going to distribute software, you don't want to build it
with macports (because all the linker paths will be absolute and
pointing at /opt/local, which is not how you want to distribute
anything). Because of this, I don't think cro
If you're going to distribute software, you don't want to build it
with macports (because all the linker paths will be absolute and
pointing at /opt/local, which is not how you want to distribute
anything). Because of this, I don't think crosscompiling is an issue,
since when building just
On 2 Jan, 2007, at 16:52, Pau Arumi wrote:
hi all,
nowadays is very common that osx software is distributed as
universal binaries, so i'm quite sure somebody have tried to
crosscompile (intel+powerpc) some macports libraries.
i'd need to do that for a handful of libraries, so, before starti
hi all,
nowadays is very common that osx software is distributed as universal
binaries, so i'm quite sure somebody have tried to crosscompile
(intel+powerpc) some macports libraries.
i'd need to do that for a handful of libraries, so, before starting my
experiments i'd like to hear some previou
12 matches
Mail list logo
