ICU4C proposal: Deprecate the pkgdata -O argument

George Rhoten <[email protected]>
Newsgroups gmane.comp.lib.icu.general
Message-ID <OF60A04C6A.37B1075E-ON86256DA9.00563F43-88256DA9.0057BE67@us.ibm.com>
I'd like to deprecate the pkgdata -O argument on Windows only.  The 
pkgdata tool will no longer require the -O argument.  It will now presume 
that pkgdata is in the same directory as genccode and gencmn (required 
tools for pkgdata).

Here are the reasons for this change:

1) The argument starts with a D: or an R:.  This part of the argument 
isn't used, and it can easily be confused with a drive letter.
2) The -O argument has different syntax compared to the Unix builds.
3) The specified directory requires that the genccode and gencmn tools are 
in a subdirectory called "bin".  This makes it difficult to redistribute 
the tools.


Technical details:
When the -O argument isn't specified, pkgdata will do the following:

1) If pkgdata is invoked with a relative or explicit path, it will expand 
it to the full path and use that directory for gencmn and genccode.
2) otherwise it will presume that pkgdata was called by being in the PATH, 
and it will search for the location of pkgdata in the PATH environment 
variable.

I've already tried this code, and it works for me.  It definitely 
simplified of my Windows build scripts.

deadline for comments: Sept. 29th, 2003

George Rhoten
IBM Globalization Center of Competency/ICU  San José, CA, USA
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.