Menu
▾
▴
[MinGW-cvs] catgets FDL, NONE, 1.1 README, NONE, 1.1 ChangeLog, 1.23, 1.24 Makefile.in, 1.5, 1.6
|
From: Keith M. <kei...@us...> - 2008-01-01 18:45:15
|
Update of /cvsroot/mingw/catgets In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv12508 Modified Files: ChangeLog Makefile.in Added Files: FDL README Log Message: Establish package structure for distribution. Index: ChangeLog =================================================================== RCS file: /cvsroot/mingw/catgets/ChangeLog,v retrieving revision 1.23 retrieving revision 1.24 diff -C2 -d -r1.23 -r1.24 *** ChangeLog 31 Dec 2007 17:09:49 -0000 1.23 --- ChangeLog 1 Jan 2008 18:45:08 -0000 1.24 *************** *** 1,2 **** --- 1,26 ---- + 2008-01-01 Keith Marshall <kei...@us...> + + Establish package structure for distribution. + + * README, FDL: New files. + + * Makefile.in (scriptdir, docdir): New macros; define them. + (DISTDOC_SOURCES): New macro; define to include ChangeLog, README + and FDL as distributed files. + (OTHER_SOURCES): Include DISTDOC_SOURCES. + (INSTALL_PROGS): Macro renamed to... + (DEV_SCRIPTS): ...this. + (MISC_SOURCES): Update accordingly. + (INSTALL_SCRIPT): New macro; define per autoconf substitution. + (install-bin-progs, install-scripts): New make targets. + (install-progs): Use them. + (DISTNAME): Add SNAPSHOT placeholder macro. + (bindist-tag, devdist-tag): New macros; define them. + (bindist-docs-install): New target. + (devdist-headers-install): New target. + (devdist-docs-install, devdist-extra-docs-install): New targets. + (devdist): New target; use them. + (dist): Build it. + 2007-12-31 Keith Marshall <kei...@us...> Index: Makefile.in =================================================================== RCS file: /cvsroot/mingw/catgets/Makefile.in,v retrieving revision 1.5 retrieving revision 1.6 diff -C2 -d -r1.5 -r1.6 *** Makefile.in 31 Dec 2007 17:09:50 -0000 1.5 --- Makefile.in 1 Jan 2008 18:45:09 -0000 1.6 *************** *** 7,14 **** # $Id$ # ! # Copyright (C) 2006, 2007, Keith Marshall # # Written by Keith Marshall <kei...@us...> ! # Last modification: 13-Nov-2007 # # --- 7,14 ---- # $Id$ # ! # Copyright (C) 2006, 2007, 2008, Keith Marshall # # Written by Keith Marshall <kei...@us...> ! # Last modification: 01-Jan-2008 # # *************** *** 37,41 **** --- 37,43 ---- bindir = @bindir@ libdir = @libdir@ + scriptdir = @datadir@/$(PACKAGE)/scripts includedir = @includedir@ + docdir = @datadir@/doc/$(PACKAGE) mandir = @mandir@ *************** *** 92,98 **** GENCAT_OBJECTS = @GENCAT_OBJECTS@ ! OTHER_SOURCES = COPYING ChangeLog mkinstalldirs install-sh $(MISC_SOURCES) ! MISC_SOURCES = $(CONFIG_HEADERS) $(CONFIG_SOURCES) $(INSTALL_PROGS) MANPAGE_SOURCES = catopen.man catgets.man catclose.man gencat.man --- 94,101 ---- GENCAT_OBJECTS = @GENCAT_OBJECTS@ ! OTHER_SOURCES = $(DISTDOC_SOURCES) mkinstalldirs install-sh $(MISC_SOURCES) ! MISC_SOURCES = $(CONFIG_HEADERS) $(CONFIG_SOURCES) $(DEV_SCRIPTS) + DISTDOC_SOURCES = ChangeLog COPYING FDL README MANPAGE_SOURCES = catopen.man catgets.man catclose.man gencat.man *************** *** 131,135 **** DLLVERSION = @DLLVERSION@ ! INSTALL_PROGS = gendefs.awk # Generic rule, replacing the built-in default, to create an object file --- 134,138 ---- DLLVERSION = @DLLVERSION@ ! DEV_SCRIPTS = gendefs.awk # Generic rule, replacing the built-in default, to create an object file *************** *** 203,206 **** --- 206,210 ---- INSTALL = @INSTALL@ INSTALL_PROGRAM = @INSTALL_PROGRAM@ + INSTALL_SCRIPT = @INSTALL_SCRIPT@ INSTALL_DATA = @INSTALL_DATA@ *************** *** 214,232 **** cd cross-build; $(MAKE) install-headers install-libs ! install-bin install-progs: all ! $(mkinstalldirs) --require ${exec_prefix} ${bindir} ${libdir} ! for prog in $(BUILD_PROGS); do \ ! echo $(INSTALL_PROGRAM) $$prog ${bindir}/$(tool_prefix)$$prog; \ ! $(INSTALL_PROGRAM) $$prog ${bindir}/$(tool_prefix)$$prog; \ done ! for prog in $(INSTALL_PROGS); do \ ! echo $(INSTALL_PROGRAM) ${srcdir}/$$prog ${bindir}/$(tool_prefix)$$prog; \ ! $(INSTALL_PROGRAM) ${srcdir}/$$prog ${bindir}/$(tool_prefix)$$prog; \ done ! install-libs: all-libs $(all-dll) test -z "$(all-dll)" || for dll in $(BUILD_DLLS); do \ echo $(INSTALL_DATA) $$dll ${bindir}; \ $(INSTALL_DATA) $$dll ${bindir}; \ echo $(INSTALL_DATA) $(DLL_IMPORT_LIBNAME) ${libdir}; \ $(INSTALL_DATA) $(DLL_IMPORT_LIBNAME) ${libdir}; \ --- 218,249 ---- cd cross-build; $(MAKE) install-headers install-libs ! install-progs: install-bin-progs install-scripts ! ! install-bin-progs: $(BUILD_PROGS) ! $(mkinstalldirs) --require ${exec_prefix} ${bindir} ! for prog in $^; do \ ! progname=`IFS='\\/'; set x $$prog; eval echo '$$'$$#`; \ ! echo $(INSTALL_PROGRAM) $$prog ${bindir}/$(tool_prefix)$$progname; \ ! $(INSTALL_PROGRAM) $$prog ${bindir}/$(tool_prefix)$$progname; \ done ! ! install-scripts: $(DEV_SCRIPTS) ! $(mkinstalldirs) --require ${prefix} ${scriptdir} ! for script in $^; do \ ! prog=`IFS='\\/'; set x $$script; eval echo '$$'$$#`; \ ! echo $(INSTALL_SCRIPT) $$script ${scriptdir}/$(tool_prefix)$$prog; \ ! $(INSTALL_SCRIPT) $$script ${scriptdir}/$(tool_prefix)$$prog; \ done ! install-dll: $(all-dll) ! $(mkinstalldirs) --require ${exec_prefix} ${bindir} test -z "$(all-dll)" || for dll in $(BUILD_DLLS); do \ echo $(INSTALL_DATA) $$dll ${bindir}; \ $(INSTALL_DATA) $$dll ${bindir}; \ + done + + install-libs: all-libs $(all-dll) + $(mkinstalldirs) --require ${exec_prefix} ${bindir} ${libdir} + test -z "$(all-dll)" || for dll in $(BUILD_DLLS); do \ echo $(INSTALL_DATA) $(DLL_IMPORT_LIBNAME) ${libdir}; \ $(INSTALL_DATA) $(DLL_IMPORT_LIBNAME) ${libdir}; \ *************** *** 269,278 **** ## ============== ## ! dist: srcdist bindist dist_srcdir = @abs_top_srcdir@ DISTDIRS = include m4 repl repl/include man DISTFILES = $(GENCAT_SOURCES) $(CATGETS_SOURCES) $(OTHER_SOURCES) ! DISTNAME = $(PACKAGE)-$(VERSION) ZIP = gzip -c --- 286,298 ---- ## ============== ## ! dist: srcdist bindist devdist dist_srcdir = @abs_top_srcdir@ DISTDIRS = include m4 repl repl/include man DISTFILES = $(GENCAT_SOURCES) $(CATGETS_SOURCES) $(OTHER_SOURCES) ! DISTNAME = $(PACKAGE)-$(VERSION)$(SNAPSHOT) ! ! bindist-tag = bin ! devdist-tag = dev ZIP = gzip -c *************** *** 294,303 **** rm -rf $(DISTNAME) ! bindist: all rm -rf tmp; mkdir tmp ! $(MAKE) prefix=`pwd`/tmp install-progs install-libs install-doc ! cd tmp && tar chf - * | $(ZIP) > ../$(DISTNAME)-bin.$(ZIPTYPE) rm -rf tmp ## ========== ## --- 314,349 ---- rm -rf $(DISTNAME) ! bindist devdist: all rm -rf tmp; mkdir tmp ! $(MAKE) prefix=`pwd`/tmp $@-install ! cd tmp && tar chf - * | $(ZIP) > ../$(DISTNAME)-$($@-tag).$(ZIPTYPE) rm -rf tmp + bindist-install: bindist-docs-install install-dll + devdist-install: devdist-docs-install devdist-headers-install + devdist-install: install-progs install-libs install-doc + + bindist-docs-install: README COPYING + $(mkinstalldirs) ${docdir} + for file in $^; do \ + echo $(INSTALL_DATA) $$file ${docdir}; \ + $(INSTALL_DATA) $$file ${docdir}; \ + done + + devdist-docs-install: bindist-docs-install devdist-extra-docs-install + + devdist-extra-docs-install: FDL + for file in $^; do \ + echo $(INSTALL_DATA) $$file ${docdir}; \ + $(INSTALL_DATA) $$file ${docdir}; \ + done + + devdist-headers-install: nl_types.h langinfo.h + $(mkinstalldirs) ${includedir} + for file in $^; do \ + echo $(INSTALL_DATA) $$file ${includedir}; \ + $(INSTALL_DATA) $$file ${includedir}; \ + done + ## ========== ## --- NEW FILE: FDL --- GNU Free Documentation License Version 1.2, November 2002 Copyright (C) 2000,2001,2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition. The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. 2. VERBATIM COPYING You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. 3. COPYING IN QUANTITY If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. H. Include an unaltered copy of this License. I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section. O. Preserve any Warranty Disclaimers. If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. 5. COMBINING DOCUMENTS You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements". 6. COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. 8. TRANSLATION Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail. If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. 9. TERMINATION You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. ADDENDUM: How to use this License for your documents To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page: Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts." line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. --- NEW FILE: README --- MinGW catgets README $Id: README,v 1.1 2008/01/01 18:45:09 keithmarshall Exp $ Copyright (C) 2007, Keith Marshall Written by Keith Marshall <kei...@us...> Last modification: 20-Dec-2007 This package provides a native Win32 implementation of the POSIX National Language Support API, conforming generally to IEEE standard 1003.1-2001, and SUSv3, for adding national language message catalogue support to user applications. It comprises a development library, designated libcatgets.a for static linking, or catgets-<n>.dll with accompanying libcatgets.dll.a import library for dynamic linking, with supporting nl_types.h header file, delivering Win32 implementations of the catopen(), catgets() and catclose() functions, as required by the POSIX National Language Support API; this is accompanied by a suitable, standards conformant `gencat' utility program, which is used to generate the message catalogue files, which are bound to user applications making use of these library functions. The MinGW catgets package is free software It is provided AS IS, in the hope that it may be useful, but WITHOUT WARRANTY OF ANY KIND, not even an IMPLIED WARRANTY of MERCHANTABILITY, nor of FITNESS FOR ANY PARTICULAR PURPOSE. Permission is granted to redistribute this software, either "as is" or in modified form, under the terms of the GNU General Public License, as published by the Free Software Foundation; either version 2, or (at your option) any later version; see the file COPYING, for further details. Packaging Options ----------------- MinGW catgets is available for download in three package formats; (the full text of this README file is included with each):-- 1) mingw-catgets-<version>-bin.tar.gz Provides only the pre-built dynamic link library, for use by client applications which are delivered in binary format. The DLL is placed in the `bin' subdirectory of the directory in which the package is untarred; typically this should be the root of either the MinGW tree, or the MSYS tree. 2) mingw-catgets-<version>-dev.tar.gz Provides the header files and precompiled libraries, which are needed to develop `catgets' client applications, together with the associated `manpage' documentation, and the `gencat' tool which must be used to compile compatible message catalogues. It should be untarred in the root of the MinGW tree, and client applications should be linked with the `-lcatgets' option, specified *after* the dependent object modules, on the linking command line. 3) mingw-catgets-<version>-src.tar.gz Provides the full source code from which the above two packages have been built; it supports building for native deployment, as the above, or for deployment as components of a cross-compiler tool chain. Prerequisites for Building from Source -------------------------------------- To build and install the catgets development libraries and tools, you require a C compiler, and tool chain, such as that provided by MinGW, and a build environment capable of running Bourne shell scripts, and the GNU `make' utility, such as that provided by MSYS. Before attempting to build MinGW catgets from source, you must ensure that a suitable `iconv' implementation is installed. This is not normally the case, with a standard MinGW/MSYS installation, but the requirement may be satisfied by installing GNU libiconv; this *must* be libiconv-1.11 or later, and it *must* incorporate the 2007-04-23 patch, correcting a Win32 specific wchar_t conversion bug; you may ensure that this prerequisite is adequately satisfied, by installing libiconv-1.11 using the mingwPORT script from http://downloads.sourceforge.net/mingw/libiconv-1.11-mingwPORT-20070423-1.tar.bz2 Building from Source, for use "In Place" on Win32 ------------------------------------------------- The build procedure, using MinGW and MSYS, is as follows:-- 1) Choose a suitable directory, where you will build the package; (it must be a directory in which you have write permission). A typical example might be `~/src'; create it if necessary... mkdir -p ~/src cd ~/src 2) Extract the source distribution tarball... tar xzf [[/]path/to/]mingw-catgets-<version>.tar.gz 3) Create a build directory, and make it your working directory... mkdir mingw-catgets-<version>/build cd mingw-catgets-<version>/build 4) Configure the build... ../configure [options ...] For a typical MinGW installation, you will probably want to set, at least, the `--prefix=/mingw' option; if you don't, this setting will default to `--prefix=/usr/local', which is not what you want if you have installed MinGW and MSYS with their standard configurations. To see other available options, try... ../configure --help (You may wish to consider adjusting the `CFLAGS', or the `--mandir' settings). 5) Build the installable components... make 6) Install the basic development library components... make install 7) Install documentation... This step is optional, but recommended; if you have installed, or if you plan to install, the `man' package then... make install-man will allow you to access the manpages for gencat(1), catopen(3), catgets(3) and catclose(3) from any working directory. Building for Cross-Hosted Use ----------------------------- MinGW catgets may be built as a component of a cross-hosted compiler tool chain; this is supported directly by the build system, when a `--target' option differing from `--host' is specified at `configure' time. To build as a cross tool, the cross-compiler suite must already have been installed, and the `--target' option must be specified to match the prefix used to identify, and invoke the cross-compiler itself. For example, this is how I build it, for use with my GNU/Linux hosted i586-mingw32-gcc tool chain, (which is identified by the prefix `i586-mingw32'):-- 1) You may, if you wish, install GNU libiconv. However, your host may already have a suitable iconv implementation, such as that provided by glibc on GNU/Linux systems; if this is the case, it should suffice. 2) Create the working directory to host the source tree, as described in steps (1) and (2) of the standard Win32 "In Place" build procedure. 3) Create a build directory, in which to progress the first stage of the build, and make it your working directory... mkdir mingw-catgets-<version>/build cd mingw-catgets-<version>/build 4) Configure the build... ../configure [options ...] --prefix=<prefix> --target=i586-mingw32 As before, you may wish to review to options listed by... ../configure --help and adjust any you consider to be appropriate; it is important that you specify a <prefix> which matches the installation path of your cross compiler tool chain, and that you set the --target to match the name of your cross tools -- in my case, the cross compiler is i586-mingw32-gcc, and the entire tool chain shares the i586-mingw32 target prefix. 5) Build and install the cross tool components... make make install This results in building of the natively hosted tools, directly within the build directory, together with the subset of the library components which are needed to build these tools, and which are also compiled to native object code. Additionally, in the cross-build subdirectory, the appropriate target specific cross-compiler is invoked, to build the full set of libraries, as they will be required when subsequently deploying the cross-tools to create applications for the target platform. On successful completion of this cross-tools build, the cross-tools and the supporting cross-compiled libraries are installed into the prefix, directory, as specified in the configure command; at installation time, the names of the executable cross-tool programs are qualified by the addition of a program name prefix, to match the specified target. 6) Install documentation... As in the case of the natively built tool chain, step (5) does not install the man pages which accompany the package. These may be separately installed by issuing the command... make install-man In this case, the installed man pages retain the same basic names as used in the natively compiled case. If preferred, the man pages may be installed into an existing MANPATH directory, and distinguished their similarly named native counterparts, by in the first instance configuring with an explicit `--mandir=...' option, and then adding a target specific man page name prefix, such as... make man_prefix=i586-mingw32- install-man 7) Note that step (5) builds only the cross-compiled library components, which are the minimum required to support deployment of the cross-tools into an existing cross-compiler tool chain; in particular, it does not create a tool chain for eventual deployment on the target platform. If this is required, it may be prepared and packaged, without separate configuration, by completing the partial build which has already been initiated in the cross-build subdirectory... cd cross-build make make bindist Linking MinGW Applications to use Message Catalogues ---------------------------------------------------- This package provides POSIX conformant national language support for MinGW applications. Such support is added through calls to the POSIX standard `catopen', `catgets' and `catclose' functions, as described in the accompanying `man' pages. References to these functions are resolved by addition of the `-lcatgets' option to the command line, when linking the application; both static and dynamically linked variants of the associated library are provided. Preparing the Message Catalogues -------------------------------- Message catalogues, for use with the MinGW `catgets' implementation, are compiled using a POSIX conforming `gencat' tool; (when deployed as a component of a cross-hosted tool chain, this tool is named so as to maintain consistency with the cross-compiler naming convention; thus when the cross-compiler is built for, say, an i586-mingw32 target, invoked as i586-mingw32-gcc for example, then gencat would be consistently invoked as i586-mingw32-gencat. The command syntax, and the syntax for its message definition source files, is described in the accompanying `gencat' man page. $RCSfile: README,v $: end of file |