Moving Forward with c-treeACE V9
More and more developers are taking advantage of the many new features of c-treeACE V9. Why haven't you? The list of new features introduced in V9 should help nearly every application provide a better -- and faster -- experience.
- Extensive Interface Support
- Productivity Enhancing Tools
- Server Quiesce Mode
- Enhanced Dynamic Dump
- Advanced Encryption of SQL Tables
- Huge Performance Gains of Complex Queries
- Up to 50% Faster Through Scalability Additions
- New Deployment Options
- Flexible Pricing
Along with this impressive array of new features, an easier to navigate SDK was introduced. In many cases, simply link against provided binaries and you're off and running.
Improved Navigation
c-treeACE simplifies your development, including providing the build tools as described above. Previous c-tree developers were accustomed to building their libraries with the mtmake utility and this utility continues to be available. These c-treeACE make utilities are conveniently located in the /pro directory of your c-treeACE installation. This easy to find location is shown below for comparison to the previous c-tree Plus V8.14 location.
c-tree Plus V8.14 mtmake location
C:\FairCom\V8.14\ctreeSDK\ctreeAPI\mtree
|
c-treeACE V9 mtmake location
FairCom\V9.0.0\win32\pro
|
How do I Convert my Existing Builds?
While there are new locations for many of the c-treeACE SDK components, it is still remarkably easy to build. Here are a few simple steps to adjust your build.
Use the provided multithreaded client libraries!
- Include the c-treeACE /include directory.
C:\FairCom\V9.1.1\win32\include
- Include the c-treeACE /include/sdk/<API> directory. This replaces the /custom.cli directory of V8 and prior versions. For example. When building a traditional Windows ISAM application include the following:
C:\FairCom\V9.1.1\win32\include\sdk\ctree.isam
- Link against the proper library binary. These are found in the /lib<API> directory.
C:\FairCom\V9.1.1\win32\lib\ctree.isam\Microsoft Visual Studio 2008\mtclient.lib
Building your own libraries?
It's still easy to build your own libraries for the ultimate control. mtmake is now located in the /pro directory. When you run mtmake you'll be prompted to create a new project directory so you can easily keep all of your related code together, and no longer overwrite existing libraries. After configuring the makefile, change to your new project directory and run the mk batch script. That's it! You'll find the following are now required to modify to your existing builds:
- Include the c-treeACE /include directory.
C:\FairCom\V9.1.1\win32\include
- Include the c-treeACE /include/sdk/<API> directory. This replaces the /custom.cli directory of V8 and prior versions and includes the platform dependent headers. For example. When building a traditional Windows ISAM application include the following:
C:\FairCom\V9.1.1\win32\include\sdk\ctree.isam
- Include you new project directory containing the custom ctoptn.h header:
C:\FairCom\V9.1.1\win32\pro\myProject1
- Link against your custom built c-tree library
C:\FairCom\V9.1.1\win32\pro\myProject1\obj\Debug\ctclient.lib
Tip!
mk generates a debug build of the c-tree library by default. Use mk release to easily create the release build.
See Also
|
