Downloads
Install Instructions
Boost provides free peer-reviewed portable C source libraries. We emphasize libraries that work well with the C Standard Library. Boost libraries are intended to be widely useful, and usable across a broad spectrum of applications. Feb 26, 2020 The unzipped directory structure is shown here: The C/C headers are contained in include directory. The static and dynamic libs are located in the libStatic and libDyn directories. Universal libs may be created by running the makeUniversalLibs.sh script.
- Download and unzip to any directory. The unzipped directory structure is shown here:
- The C/C++ headers are contained in include directory.
- The static and dynamic libs are located in the libStatic and libDyn directories.
- Universal libs may be created by running the makeUniversalLibs.sh script. (Make sure this script has execute permission first 'chmod a+x makeUniversalLibs.sh') The contents of this shell script are shown here:
- This download is both the trial and full version.
Chilkat libraries are fully functional for 30-day evaluations. - Release Notes are available on the Chilkat blog.
- See also: Chilkat Reference Documentation
- See also: Chilkat Sample Code
- See also: Chilkat Blog
How to Distribute a dylib with your Application
C++ Library Forbids Macroizing Keywords
(This information is general and applies to any dylib on Mac OS X.) On Mac OS X, a dynamic library (dylib) has an 'install name'. The install name is a path baked into the dynamic library that says where to find the library at runtime. When an application is linked against a dylib, the path is saved in the app's binary so that it can find the dylib at runtime.
The install name of a dylib can be viewed by using otool. For example:
This means that unless the DYLD_LIBRARY_PATH environment variable is set to allow the runtime linker find the dylib, the dylib must be placed in the exact location as specified by the install name.
However, the install name of a dylib can be changed by using the install_name_tool utility. The @loader_path keyword can be used to make it relative to an install directory.
Chilkat recommends becoming familiar with the install_name_tool command and it's various options. For example, this command changes the install name of libchilkat.dylib to be relative to the location of the binary using it:
News
2020-03-11: ICU 66 released. It updates to Unicode 13 & CLDR 36.1. New, extra Q1 releases for low-risk integration of Unicode 13.
2019-10-03: ICU 65 released. It updates to CLDR 36 locale data with many additions and corrections, and some new measurement units. The Java LocaleMatcher API is improved, and ported to C++. For building ICU data, there are new filtering options, and new tracing support for data loading in ICU4C.
2019-04-17: ICU 64.2 released. This maintenance update for ICU 64 includes draft Unicode 12.1 update, CLDR 35.1 locale data and support for new Japanese era Reiwa (令和).
C++ Libraries Machine Learning
2019-04-12: ICU 63.2 / 62.2 / 61.2 / 60.3 / 59.2 / 58.3 / 57.2 / 56.2 / 55.2 / 54.2 / 53.2 / 52.2 / 51.3 / 50.2 / 4.8.2 released. These maintenance updates for past ICU versions include support for new Japanese era Reiwa (令和).
2019-03-27: ICU 64 (64.1) released. ICU 64 updates to Unicode 12 and to CLDR 35 locale data with many additions and corrections, and some new languages. ICU adds a data filtering/subsetting mechanism, improved formatting API, and a C++ LocaleBuilder.
