How to handle link dependencies under Xcode vs. MS Visual C++
How to handle link dependencies under Xcode vs. MS Visual C++
- Subject: How to handle link dependencies under Xcode vs. MS Visual C++
- From: email@hidden
- Date: Thu, 23 Jun 2005 15:45:19 +0200
- Importance: High
Hello,
I am porting code from MS Visual C++
to Mac OS X. I have some difficulties to
link the final files together.
I had some .dll on windows, that I tried
to compile and link to .bundles under
MAC.
The linker than makes errors for double
definitions when I link the final
application file.
Did anyone port already .dll form window
to Mac OS X ?
What are convient options for the linking
?
What are the corresponding Linker parameters
in Xcode to tell the linker the depencies ?
In MS Visual C++ I used the project
dependencies menu to tell build and link dependencies.
In Xcode I use Direct Dependencies in
the General Tab in the Target Info of my targets to add dependencies.
But I think this only influences that
the depencies a build before, the resulting .dylib or .bundle is not added
automatically to the -filelist. I had a look at that automatically generated
file, the dependent project files are not in there. As the file is generated
everytime, I do not know how to influence this.
Thanks in advance
Jürgen Jäger
mail: 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