[icu-support] SOLVED: Bug in xcode ? //Problems with ICU dlls (make_install_name)
[icu-support] SOLVED: Bug in xcode ? //Problems with ICU dlls (make_install_name)
- Subject: [icu-support] SOLVED: Bug in xcode ? //Problems with ICU dlls (make_install_name)
- From: Ruslan Zasukhin <email@hidden>
- Date: Mon, 07 Nov 2005 21:54:46 +0200
- Resent-date: Mon, 07 Nov 2005 22:03:47 +0200
- Resent-from: Ruslan Zasukhin <email@hidden>
- Resent-message-id: <BF957DA6.41C79%email@hidden>
- Resent-to: xcode-Users List <email@hidden>
- Thread-topic: SOLVED: Bug in xcode ? //Problems with ICU dlls (make_install_name)
On 11/7/05 7:27 PM, "Ruslan Zasukhin" <email@hidden> wrote:
Hi All,
Problem was next:
* I did have libs in folder1
* XCODE project have this libs as items AND LIB SEARCH PATHS also
* when I have move libs to folder2, I have correct items in tree,
but did not note lib paths.
As result, XCODE have use libs from OLD path.
Not logical. IMHO this is BUG of XCODE
> Hi Jochen,
>
> I have strange problems with ICU.
>
> * I have copy 4 dlls into our
> /usr/local/lib/vcomponents
>
> * using script I have set for them all path as
> /usr/local/lib/vcomponents
>
> All looks correct and okay.
>
> * now I have correct kernel_2 project to point into this dlls,
> but not into our old location sources_ThirdParty
>
> * I build kernel dll. What you expect to see for it in otool ?
> I expect to see dependency on ICU dlls with my paths.
>
> But I see
>
> /usr/local/lib/vcomponents/libvkernel_ppc_debug.dylib:
> /usr/local/lib/vcomponents/libvkernel_ppc_debug.dylib (compatibility
> version 2.1.0, current version 2.1.0)
> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
> (compatibility version 2.0.0, current version 128.0.0)
> /usr/local/lib/vcomponents/VSDK.framework/Versions/A/VSDK
> (compatibility version 1.0.0, current version 1.0.0)
> /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version
> 1.2.3)
> libicuuc.dylib.30 (compatibility version 30.0.0, current version
> 30.0.0)
> libicudata.dylib.30 (compatibility version 30.0.0, current version
> 30.0.0)
> libicui18n.dylib.30 (compatibility version 30.0.0, current version
> 30.0.0)
> libicuio.dylib.30 (compatibility version 30.0.0, current version
> 30.0.0)
> /usr/local/lib/vcomponents/libvshared_ppc_debug.dylib (compatibility
> version 2.1.0, current version 2.1.0)
> /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
> version 7.3.0)
> /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
> version 1.0.0)
> /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current version
> 92.0.0)
> ----------------------------------
>
> So present old original names and paths for ICU.
> I do not see any reasons for this !
>
> Any ideas ?
>
--
Best regards,
Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc
Valentina - Joining Worlds of Information
http://www.paradigmasoft.com
[I feel the need: the need for speed]
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
icu-support mailing list - email@hidden
To Un/Subscribe: https://lists.sourceforge.net/lists/listinfo/icu-support
_______________________________________________
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