MW Ron wrote:
> Jonathan Turkanis wrote:
>> MW Ron wrote:
>>> Drag the depenedent target to the host target, it will be in italics
>>> under that then click on the link icon
>>>
>>> it will look like this
>>> + Test project
>>> + lib.mcp
>>> Library (in italics) * (under links)
>>>
>>> See if that works for you
>>
>> Okay, I think I'm finally catching on ;-) It looks like:
>>
>> 1. An arrow icon indicates a dependency
>> 2. A dot under the link icon tell the linker to link agains the
>> output file of the dependent target.
>
> The arrow just selects the current target :) it is the same as
> changing the target in the pop up windows when you are in the Files
> or Link tab
I think I'm getting dumber every day :-D
Just to be clear: I'm talking about the arrows on the dependencies, not
the
top-level targets. Here's what I have (forgive the corny names):
Targets Link
- -> hellobeatles Debug
- libjohnpaul.mcp
-> libjohnpaul Debug *
libjohnpaul Release
- libgeorgeringo.mcp
-> libgeorgeringo Debug *
libgeorgeringo Release
Here "->" represents an arrow icon. With this configuration, everything
works.
If I remove the asterisks, I get linker errors; if I remove the arrows
from
libjohnpaul Debug and libgeorgeringo Debug, the dependencies aren't built
automatically.
So I've got something that works; I just want to know if it's the normal
way to
do things.
> Three should be some examples of libraries in the CodeWarrior Examples
> what version of CW do you have?
8.3 and 9.4 for Windows. I think I have version 5 for Mac lying around
somewere,
too ;-)
>The examples usually have a project
> for the library and a test project that has that as a dependency.
Okay, (CodeWarrior Examples)/MFC Examples/Ray the Tracer/Ray.mcp looks
like a
good example. It seems to be set up just like my Beatles example above.
Thanks for putting up with my thickheadedness!
> Ron
Jonathan
|
