Re: [icu-support] intregrating ICU into build environment

[Simon M. <smc...@au...>]

Thanks,

That is still a bit tricky for me since I may not have write access to '
/usr/local/special'  on all my build platforms. Maybe I could link them 
through /tmp. That will mean rebuilding all my ICU on every platform too 
:-(.

Isn't "pkgadd -O <ICUROOT>" supposed to handle this problem? I couldn't 
get it to work (see other post). Is there an environment variable it uses 
for this?

Cheers,

Simon McMahon
Software Engineer
Australia Development Laboratory
IBM
+61 7 5552 4002
+61 432294180




David Bertoni <dbe...@gm...> 
Sent by: icu...@li...
23/05/2008 02:44 AM
Please respond to
ICU support mailing list <icu...@li...>


To
ICU support mailing list <icu...@li...>
cc

Subject
Re: [icu-support] intregaring ICU into build envirnoment






Simon McMahon wrote:
> Hi,
> 
> I have to link ICU into my application and it is build under a source 
code 
> control system (CMVC). I also need to add the ICU components to the 
> repository so the app can be built from there.
> 
> The problem is that the extract is done to a non-fixed path and ICU 
likes 
> to be 'installed' in the same place to run properly as 'pkgdata' pulls 
> stuff from the install path.
> 
> 'pkgdata' takes a -O arg. is this what I need to use if I move the ICU 
> installation?
> Does it have to be an absolute file path or can it be a relative, to 
> current directory, path?
> I thought I saw somewhere that this flag was deprecated. Is it still 
valid 
> to use this?
I had to deal with this issue constantly when I worked in the DB2 LUW 
group at IBM.  I encourage you to build the ICU with a consistent prefix 
that you know will work on all of your supported platforms.  Then, as 
part of your build process, create symlinks to the ICU directories where 
they were extracted.

For example:

./runConfigureICU Linux --prefix=/usr/local/special

then:

ln -s /my/extraction/point/bin /usr/local/special/bin
ln -s /my/extraction/point/include /usr/local/special/include
ln -s /my/extraction/point/lib /usr/local/special/lib
ln -s /my/extraction/point/man /usr/local/special/man
ln -s /my/extraction/point/sbin /usr/local/special/sbin
ln -s /my/extraction/point/share /usr/local/special/share

If you have a shared network file system available on all of your 
platforms, you could also build and install the ICU there.

Other solutions, like hacking the icu-config might work, but they are 
fragile and difficult to maintain.

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
icu-support mailing list - icu...@li...
To Un/Subscribe: https://lists.sourceforge.net/lists/listinfo/icu-support