I am attempting to use PMT. I have downloaded ONLY the binary installation. I can't seem to find any documentation on the installation of the binaries. The readme.html in the distribution discusses the building of the sources (remember, I only downloaded the binaries).
Additionally, the test applications have references to the ../../src folder which is only in the source distribution.
Does anyone know how to set things up using only the binary distribution. Should I report the issues with the readme as a bug?
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Even though the VC++ project settings contain searching the include path for ..\..\src, it is simply ignored in the binary builds. The include path also points to ..\..\inc, which is where the include files are successfully picked up for the binary build.
Ensure you have all the environment variables set up, as discussed below. The following directions on getting setup for building the PMT test programs with the binary PMT distribution might help.
a.) PMT_XERCES_INC_PATH - This points to the Xerces include directory.
My setting is: C:\ClearCaseViews\rupe_nightly\Fw\Toolkits\xerces-c\include
b.) PMT_XERCES_LIB_PATH - This points to the Xerces library directory.
My setting is: C:\ClearCaseViews\rupe_nightly\Fw\Toolkits\xerces-c\win32\lib
c.) KIESEXIFROOT - This points to the Kies toolkit directory.
My setting is: c:\CvsNow\Pmt\Toolkits\Kies
d.) IJLROOT - This points to the IJL toolkit directory.
My setting is: c:\CvsNow\Pmt\Toolkits\ijl
e.) JPEGROOT - This points to the JPEG toolkit directory.
My setting is: c:\CvsNow\Pmt\Toolkits\Jpeg
f.) TIFFROOT - This points to your OpenTiff toolkit directory.
My setting is: d:\OpenTiff\opentiff-1_0_1-src
5.) Setup your "path" environment variable to point to the "xerces-c_1_2.dll" file that came with the Xerces distribution. Also setup "path" to point to the "ijl15.dll" file that resides in the PMT distribution in the Toolkits\ijl\lib directory. (I have a special directory for development .DLL's, that my path points to. That way, I can just copy .DLL files like these into it.)
7.) Now you may build either of the test programs in the AccessorTest or PmtInterpreterTest directories.
I suggest building and testing the PmtInterpreterTest program first. This test code relies on one of the two libraries built by PMT: the library "PmtCored.lib". Open the workspace file "PmtInterpretestTest.dsw" in the test\PmtInterpreterTest directory. Make sure you set the active configuration to "PmtInterpreterTest - Win32 Debug" via the menu "Build > Set Active Configuration..." in VC++.
The PmtInterpreterTest program exercises parsing an XML schema file, and tests the base PmtMetadata interface a lot No image files are read or written to from the PmtInterpreterTest program.
To run the test, you may redirect the output to a temporary file. Make sure you run the test from the PmtInterpreterTest directory (not the debug directory under it), since certain files are looked for in the current directory. For example, from a DOS prompt, type in "debug\PmtInterpreterTest > look.txt". This file can then be compared to the file named "GroundTrue.txt" in a diff utility like WinDiff. The output of the two files should be identical (except for the date at the top).
8.) To build and test the AccessorTest code, again make sure you select the appropriate configuration after bringing in the "AccessorTest.dsw" workspace into VC++. Again, redirecting the output to a temporary file and comparing to "GroundTrue.txt" should result in identical comparison.
The Accessor test program relies on several more libraries that PmtInterpreterTest does, since the AccessorTest uses PMT's second library too, named "PmtAccessord.lib", and uses several image file toolkits (the ones pointed to by some of the environment variables set above).
The AccessorTest program exercises reading and writing from image files, via use of the PmtAccessor's interfaces. Since loading an XML schema and using the PmtMetadata interface is always necessary in using PMT, those things happen somewhat in the AccessorTest program too, but the primary testing of those things in detail is done mainly in the PmtInterpreterTest program.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just a FYI:
I tried compiling PMT against the latest version of xervesc (currently c.1.7), and compilation failed with warnings and errors against writeChars(). The problem went away when I compiled PMT against xercesc c_1_2.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am attempting to use PMT. I have downloaded ONLY the binary installation. I can't seem to find any documentation on the installation of the binaries. The readme.html in the distribution discusses the building of the sources (remember, I only downloaded the binaries).
Additionally, the test applications have references to the ../../src folder which is only in the source distribution.
Does anyone know how to set things up using only the binary distribution. Should I report the issues with the readme as a bug?
Robert
Robert,
Even though the VC++ project settings contain searching the include path for ..\..\src, it is simply ignored in the binary builds. The include path also points to ..\..\inc, which is where the include files are successfully picked up for the binary build.
Ensure you have all the environment variables set up, as discussed below. The following directions on getting setup for building the PMT test programs with the binary PMT distribution might help.
1.) Download and build OpenTiff. It is located on the SourceForge web site at: http://sourceforge.net/projects/opentiff
2.) Test the OpenTiff test program, located in the test directory.
3.) Download version 1.2.0a of the Xerces parser (binary version is sufficient) from: http://xml.apache.org/dist/xerces-c/stable/archives/Xerces-C_1_2_0a/
4.) Setup these environment variables on your PC:
a.) PMT_XERCES_INC_PATH - This points to the Xerces include directory.
My setting is: C:\ClearCaseViews\rupe_nightly\Fw\Toolkits\xerces-c\include
b.) PMT_XERCES_LIB_PATH - This points to the Xerces library directory.
My setting is: C:\ClearCaseViews\rupe_nightly\Fw\Toolkits\xerces-c\win32\lib
c.) KIESEXIFROOT - This points to the Kies toolkit directory.
My setting is: c:\CvsNow\Pmt\Toolkits\Kies
d.) IJLROOT - This points to the IJL toolkit directory.
My setting is: c:\CvsNow\Pmt\Toolkits\ijl
e.) JPEGROOT - This points to the JPEG toolkit directory.
My setting is: c:\CvsNow\Pmt\Toolkits\Jpeg
f.) TIFFROOT - This points to your OpenTiff toolkit directory.
My setting is: d:\OpenTiff\opentiff-1_0_1-src
5.) Setup your "path" environment variable to point to the "xerces-c_1_2.dll" file that came with the Xerces distribution. Also setup "path" to point to the "ijl15.dll" file that resides in the PMT distribution in the Toolkits\ijl\lib directory. (I have a special directory for development .DLL's, that my path points to. That way, I can just copy .DLL files like these into it.)
7.) Now you may build either of the test programs in the AccessorTest or PmtInterpreterTest directories.
I suggest building and testing the PmtInterpreterTest program first. This test code relies on one of the two libraries built by PMT: the library "PmtCored.lib". Open the workspace file "PmtInterpretestTest.dsw" in the test\PmtInterpreterTest directory. Make sure you set the active configuration to "PmtInterpreterTest - Win32 Debug" via the menu "Build > Set Active Configuration..." in VC++.
The PmtInterpreterTest program exercises parsing an XML schema file, and tests the base PmtMetadata interface a lot No image files are read or written to from the PmtInterpreterTest program.
To run the test, you may redirect the output to a temporary file. Make sure you run the test from the PmtInterpreterTest directory (not the debug directory under it), since certain files are looked for in the current directory. For example, from a DOS prompt, type in "debug\PmtInterpreterTest > look.txt". This file can then be compared to the file named "GroundTrue.txt" in a diff utility like WinDiff. The output of the two files should be identical (except for the date at the top).
8.) To build and test the AccessorTest code, again make sure you select the appropriate configuration after bringing in the "AccessorTest.dsw" workspace into VC++. Again, redirecting the output to a temporary file and comparing to "GroundTrue.txt" should result in identical comparison.
The Accessor test program relies on several more libraries that PmtInterpreterTest does, since the AccessorTest uses PMT's second library too, named "PmtAccessord.lib", and uses several image file toolkits (the ones pointed to by some of the environment variables set above).
The AccessorTest program exercises reading and writing from image files, via use of the PmtAccessor's interfaces. Since loading an XML schema and using the PmtMetadata interface is always necessary in using PMT, those things happen somewhat in the AccessorTest program too, but the primary testing of those things in detail is done mainly in the PmtInterpreterTest program.
Just a FYI:
I tried compiling PMT against the latest version of xervesc (currently c.1.7), and compilation failed with warnings and errors against writeChars(). The problem went away when I compiled PMT against xercesc c_1_2.