Do you know how to force the link to the static library from within
XCode 3.2?
Thanks!
Paul
On Sep 30, 2009, at 5:39 AM, css...@mac.com wrote:
On Sep 28, 2009, at 5:23 PM, Paul Dennis Simonson wrote:
All of the *.a files build just fine using MacPorts. I build and
link my programs using
I am not familiar with the -static option. Could you explain?
Thanks,
Paul
On Sep 30, 2009, at 6:11 AM, Jochen Küpper wrote:
On 30.09.2009, at 12:39, css...@mac.com wrote:
On Sep 28, 2009, at 5:23 PM, Paul Dennis Simonson wrote:
All of the *.a files build just fine using MacPorts. I
to
have MacPorts installed, if possible).
On Sep 29, 2009, at 12:15 AM, Andrea D'Amore wrote:
On 29/set/09, at 00:36, Paul Dennis Simonson wrote:
Reason: no suitable image found. Did find:
/opt/local/lib/libfreeimage.3.dylib: mach-o, but wrong architecture
This seems to imply
(compatibility version 1.0.0, current
version 123.0.0)
So, it is definitely linking to the .dylib libraries. Why is it doing
this, and how can I get it to link against the .a libraries instead?
On Sep 29, 2009, at 2:26 AM, Jochen Küpper wrote:
On 29.09.2009, at 00:23, Paul Dennis Simonson
Is there any way to force MacPorts to make a static library that we
can link to and distribute easily? It used to do this!!!
On Sep 17, 2009, at 6:39 PM, Jim Busser wrote:
On 2009-09-17, at 3:15 PM, Travis Griggs wrote:
Static linking isn't an option for us. And your point about it
: no suitable image found. Did find:
/opt/local/lib/libfreeimage.3.dylib: mach-o, but wrong architecture
Trace/BPT trap
logout
[Process completed]
On Sep 28, 2009, at 5:23 PM, Paul Dennis Simonson wrote:
All of the *.a files build just fine using MacPorts. I build and
link my programs using
, 2009, at 1:52 PM, Ryan Schmidt wrote:
On Sep 8, 2009, at 13:48, Paul Dennis Simonson wrote:
On Sep 7, 2009, at 11:08 PM, Ryan Schmidt wrote:
On Snow Leopard (in MacPorts and otherwise), software builds for
architecture x86_64 by default, as opposed to i386, which is what
Leopard and Tiger
when I am linking to foo.a. Can anyone explain this to me?
Thanks,
Paul
On Sep 9, 2009, at 3:11 PM, Ryan Schmidt wrote:
On Sep 9, 2009, at 15:10, Paul Dennis Simonson wrote:
Thanks for the tip. I tried using
sudo port upgrade --enforce-variants freeimage +universal
and it seemed to compile
How exactly do I rebuild the ports with the +universal variant? I am
not familiar with this.
On Sep 7, 2009, at 11:08 PM, Ryan Schmidt wrote:
On Sep 7, 2009, at 22:04, Paul Simonson wrote:
Help! I have recently upgraded to Snow Leopard and upgraded to the
new
MacPorts for Snow Leopard