XCode and ncurses
XCode and ncurses
- Subject: XCode and ncurses
- From: Chinh Nguyen <email@hidden>
- Date: Tue, 3 Jan 2006 12:55:33 -0600
I've got a console version of my GUI app that requires I link with
ncurses. I'm using XCode 2.2 so I'm compiling in Tiger. However, my
executable linked against the version of ncurses on Tiger
(libncurses.5.4.dylib) does not run on pre-Tiger machines. I think no
problem, I'll just explicitly link to /usr/lib/libncurses.5.dylib.
That still doesn't work. The linker in XCode still insists on linking
against libncurses.5.4.dylib. I temporarily renamed the older version
to the newer version thinking perhaps it was hardcoded but XCode failed
to link (as well as causing other problems).
So I then just compiled my console version using my own compile scripts
and gcc from a shell and explicitly linked against the version of
ncurses that I wanted. That worked--the executable ran on pre-Tiger
machines as well as Tiger. With this method however, my aggregate
target in XCode no longer compiles every version of my app I need. I
know I could add a shell script target that simply runs my compile
scripts but how would I know if the compile failed?
Why does XCode 2.2 insist on linking libncurses.5.4.dylib even when I
specify the older version?
-Chinh Nguyen
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden