Main Page | Namespace List | Class Hierarchy | Class List | File List | Namespace Members | Class Members | File Members | Related Pages


The easiest way to include the library is to include the AxPipe project into your solution or workspace. It's configured to work as a statically linked library. There is currently no DLL interface, and there won't likely be one, it's not that kind of library.

You should include AxPipe.h at the least, it should be fairly obvious what other includes are necessary. Your project should define the path to where-ever you placed the AxPipe source code as an extra include directory.

You should normally compile your project with the Multi Threaded Run Time Library. AxPipe is configured to, and you'll get a linker error message otherwise. If you're sure you won't be using the multi- threaded capability you can of course change this to single-threaded, but there's no real gain in doing so in most cases.

AxPipe has one external dependency currently, and that's ZLib. If you don't need the AxPipe::Stock::CPipeInflate class, you can mark CPipeInflate.cpp as not part of the compile. Optionally, you may also choose to include AxPipe on a file-by-file basis directly into your own project, and only include those parts that are relevant to you.


The external dependency is to ZLib 1.2.1, you can pick your very own copy at The standard project is setup to expect a directory named 'Contrib' at the same level as 'AxPipe', and for this case a subdirectory named zlib121. In other words, the file CPipeInflate.cpp has an additional include directory setup as ../Contrib/zlib121. If there's nothing there, and you include CPipeInflate.cpp in the build, you'll get a compilation error about zlib.h not found.

See also:
Introduction, Installation, A First Example, A Second Examle, Definitions of Terms, Stock Transformations, Utilities and Overrides

Generated on Mon Feb 2 13:19:21 2004 for AxPipe by doxygen 1.3.5