Re: Including vImage
Re: Including vImage
- Subject: Re: Including vImage
- From: j o a r <email@hidden>
- Date: Mon, 22 Nov 2004 15:12:50 +0100
On 2004-11-22, at 14.55, Jan E. Schotsman wrote:
Is this some sort of IQ test?
Accelerate.framework > Frameworks > vecLib.framework > Headers >
vBasicOps.h
> vImage.framework > Headers > vImage.h
I don't see any difference.
I'm sorry if it came across as some sort of test, that was not my
intention. Here:
/System/Library/Frameworks/Accelerate.framework/Headers/Accelerate.h
/System/Library/Frameworks/vecLib.framework/Headers/vBasicOps.h (and
others)
In both cases the headers you include exists as "top level" headers in
the framework bundle. If you check the path to the version of the
vecLib framework that you've added to Xcode you'll probably (?) find
that you've referenced the one in /System/Library/Frameworks (and not
the one inside the Accelerate framework), and that's why the short-hand
notation for the include statement works like you wrote it. At least
that's my layman explanation - someone please correct me if I'm off
track...
In any case, as the Accelerate header includes the other two, you
probably only need that one.
Btw. Isn't it weird that Apple have two separate copies of the vecLib
framework installed?
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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