| Emeric Vigier | 2f62582 | 2012-08-06 11:09:52 -0400 | [diff] [blame] | 1 | This directory contains special make/project files for Win32 |
| 2 | environments. There is files included from Common C++ that help |
| 3 | make this happen, and you can include these files locally or attach |
| 4 | symlinks as needed to make the Visual C++ project build work correctly |
| 5 | from cvs. The distribution tarball will include these files already |
| 6 | in their proper places, but a pure cvs checkout will not without copying |
| 7 | or symlinking the additional Common C++ files. |
| 8 | |
| 9 | * msvcpp/: contains Visual C++ workspace and project files for |
| 10 | ccRTP. The library will be compiled as dll under the Release and Debug |
| 11 | directories. |
| 12 | |
| 13 | * mingw32/: Mingw32 makefile. |
| 14 | |
| 15 | The principle symlinks are: |
| 16 | |
| 17 | ccrtp/w32/common/cc++ -> commoncpp2/w32/cc++ |
| 18 | ccrtp/w32/include/cc++ -> commoncpp2/w32/include/cc++ |
| 19 | ccrtp/w32/template/cc++ -> commoncpp2/w32/template |
| 20 | ccrtp/w32/src -> commoncpp2/w32/src |
| 21 | |
| 22 | CCRTP can automatically create these symlinks for you during configure. |
| 23 | To do this, you would specify the --with-commoncpp=dir option to |
| 24 | configure. The dir you use is the full path to the "base" directory |
| 25 | where Common C++ sources were unpacked. The configure script will then |
| 26 | add the extra sym links needed to support a w32 build, and these extra |
| 27 | w32 support files will be added to your distribution tarball for you. |
| 28 | --without-commoncpp may also be used to clear all symlinks. |
| 29 | |
| 30 | In addition, a special ccgnu2 and ccext2 .dsp file is included here that |
| 31 | locally builds GNU Common C++, which is then used as a dependency in the |
| 32 | ccrtp1 package build. |
| 33 | |