I am developing with PictureMetadataToolkit, but I am not able to configure correctly VC++ 6.0 under Win2000. There are link errors on library. The readme.html file just refers to installation under Win98 and NT 3.51 with SP4. Can you help me, please? Thanks...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi.. I'm working on WinXP and Visual Studio.NET platform. I've rebuilt my OpenTiff program after reading this post, and have double checked my environment variables and path. I still receive this LNK2001, and LNK2019 errors. Please advise.
Cyndi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you doing a dynamic (DLL) build? If so, try doing a static build. We have an issue with DLL builds in the latest release. We will be releasing a new version of PMT pretty soon, which will hopefully solve your issue.
We don't include WinXP with VS.NET in our current testing, but I'll give it a try to see if that is the problem.
Ricky
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Ricky,
glad to hear from you. I'm no longer trying to compile the source codes (BuildAllStatic/BuildAllDynamic). I've resorted to using the bin-win32 version, where I have followed instructions in the pmtUserGuide.pdf very closely, and am only trying to compile the test programs (AccessorTest and pmtInterpretatorTest). Although I've set my path and environment variables, somehow I note that the Path does not appear updated from the BuildLog after the LNK errors.
My objective in using PMT is to integrate it into a VB.NET Web Application for academic purpose. Currently, I'm reading up on the API. Sure hope to hear good news from you.
Cyndi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are using the .Net compiler, you will need to build the source because our binaries were built with VC6. We are currently working on getting out a 1.1alpha release, and we plan on including .NET binary distribution. Hopefully, this will be out in a few days or less.
Ricky
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Ricky,
using the .NET compiler I've built the source. However, the problem of the LNK errors when compiling the test files have returned. Please advise.
Cyndi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just built PMT (1.0.3h) successfully using the .Net compiler. Here's a list of things I had to do:
- Rebuilt OpenTiff with the .Net compiler (couldn't link to the libraries built with VC6
- Opened projects\Win32\Vc6.0\BuildAllStatic.dsw in VisualStudio.Net, and had all the project files converted over to the new format. Selected the Release configuration.
- I made the following change in the PmtAccessor project properties:
In the C/C++ -> Command Line -> Additional Options, I had to remove the /I
- I made the following change in the PmtInterpreterTest project properties:
In the C/C++ -> Command Line -> Additional Options, I had to add /Zm200
After this, I was able to build successfully. Let me know if this works for you or not. If not, please copy and paste the error message.
Thanks and good luck,
Ricky
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ricky,
I've been able to build succesfully too. But now, when I tried "Start" from the "Debug" drop-down menu, here's my Error message:
AccessorTest.exe - Unable to Locate Component
"This application has failed to start because MSVCRTD.dll was not found. Re-installing the application may fix this problem"
Pardon me, what application is referred upon in the context?
<cyndi>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ricky,
I've been able to build succesfully too. But now, when I tried "Start" from the "Debug" drop-down menu, here's my Error message:
AccessorTest.exe - Unable to Locate Component
"This application has failed to start because MSVCRTD.dll was not found. Re-installing the application may fix this problem"
Pardon me, what application is referred upon in the context?
<cyndi>
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Ricky,
Yes, I'm still building with my .NET compiler. I believe that MSVCRTD.dll should reside in the Winnt/System32 folder, but it's not. This link below should be of interest to you, titled: "Where is msvcrtd.dll for the 7.0 compiler" which informs that "The DLL CRT has been renamed in VS.NET to msvcr70.dll, and the debug version
is msvcr70d.dll"
As such, the solution to resolve this error has become beyond my capability. I've mentioned earlier that I'm using WinXP Pro, and Mike Smith wrote that "The old runtime (MSVCRT.DLL) has been shipped with NT at least as far back
as 4.0".
What if I download a copy of this dll into the appropriate folder? I'll give that a shot. Please notify me if the consequence of this action is undesirable.
Cyndi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ricky,
I've placed a copy of MSVCRT.DLL into the Windows/System32 folder. Currently, the building the BuildAllStatic Solution no longer complains about the missing dll, but I have LNK4221 errors.
E.g. EkRefCount.obj : warning LNK4221: no public symbols found; archive member will be inaccessible
In order to portray my problem, I've set up a webpage for you to access the BuildLogs from my .NET compiler.
Hi Cyndi!
We released a .Net (VC7) binary distribution for pmt-1.1beta. The documentation isn't up to date, but it will be for our 1.1 release. The project settings in the AccessorTest and PmtInterpreterTest are set up so that all you have to do is:
- Download the win32 binary distribution of xerces version 1.2 from http://xml.apache.org/xerces-c/
- Set environment variables PMT_XERCES_INC_PATH and PMT_XERCES_LIB_PATH to the include and lib directories, respectively, in the xerces distribution. For example: C:\xerces-c_1_2_0-win32\inc and C:\xerces-c_1_2_0-win32\lib
- Add pmt-1.1beta\bin and xerces-c_1_2_0-win32\bin to your Path
- Build test\AccessorTest\AccessorTest.sln and test\AccessorTest\AccessorTesti.sln and run the tests. Compare the results to GroundTrue.txt.
- Build test\PmtInterpreterTest\PmtInterpreterTest.sln and test\PmtInterpreterTest\PmtInterpreterTesti.sln and run the tests. Compare the results to GroundTrue.txt.
NOTE: There are some issues with the PmtAccessor DLL build, so I don't expect AccessorTesti to work. But the static libraries should work fine.
I hope this helps!
Ricky
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am developing with PictureMetadataToolkit, but I am not able to configure correctly VC++ 6.0 under Win2000. There are link errors on library. The readme.html file just refers to installation under Win98 and NT 3.51 with SP4. Can you help me, please? Thanks...
What are the specific link errors you're getting?
Dan
Thanks Daniel for your attention, I am not able to resolve errors about LNK2001: unresolved external symbols. Thanks again,
Christian Cucculelli
It sounds like you may have not have built the OpenTiff project. The OpenTiff program current comes in a source code distribution, and must be built.
Hi.. I'm working on WinXP and Visual Studio.NET platform. I've rebuilt my OpenTiff program after reading this post, and have double checked my environment variables and path. I still receive this LNK2001, and LNK2019 errors. Please advise.
Cyndi
Cyndi,
Are you doing a dynamic (DLL) build? If so, try doing a static build. We have an issue with DLL builds in the latest release. We will be releasing a new version of PMT pretty soon, which will hopefully solve your issue.
We don't include WinXP with VS.NET in our current testing, but I'll give it a try to see if that is the problem.
Ricky
Hi Ricky,
glad to hear from you. I'm no longer trying to compile the source codes (BuildAllStatic/BuildAllDynamic). I've resorted to using the bin-win32 version, where I have followed instructions in the pmtUserGuide.pdf very closely, and am only trying to compile the test programs (AccessorTest and pmtInterpretatorTest). Although I've set my path and environment variables, somehow I note that the Path does not appear updated from the BuildLog after the LNK errors.
My objective in using PMT is to integrate it into a VB.NET Web Application for academic purpose. Currently, I'm reading up on the API. Sure hope to hear good news from you.
Cyndi
If you are using the .Net compiler, you will need to build the source because our binaries were built with VC6. We are currently working on getting out a 1.1alpha release, and we plan on including .NET binary distribution. Hopefully, this will be out in a few days or less.
Ricky
Hi Ricky,
using the .NET compiler I've built the source. However, the problem of the LNK errors when compiling the test files have returned. Please advise.
Cyndi
Cyndi,
I just built PMT (1.0.3h) successfully using the .Net compiler. Here's a list of things I had to do:
- Rebuilt OpenTiff with the .Net compiler (couldn't link to the libraries built with VC6
- Opened projects\Win32\Vc6.0\BuildAllStatic.dsw in VisualStudio.Net, and had all the project files converted over to the new format. Selected the Release configuration.
- I made the following change in the PmtAccessor project properties:
In the C/C++ -> Command Line -> Additional Options, I had to remove the /I
- I made the following change in the PmtInterpreterTest project properties:
In the C/C++ -> Command Line -> Additional Options, I had to add /Zm200
After this, I was able to build successfully. Let me know if this works for you or not. If not, please copy and paste the error message.
Thanks and good luck,
Ricky
Ricky,
I've been able to build succesfully too. But now, when I tried "Start" from the "Debug" drop-down menu, here's my Error message:
AccessorTest.exe - Unable to Locate Component
"This application has failed to start because MSVCRTD.dll was not found. Re-installing the application may fix this problem"
Pardon me, what application is referred upon in the context?
<cyndi>
Ricky,
I've been able to build succesfully too. But now, when I tried "Start" from the "Debug" drop-down menu, here's my Error message:
AccessorTest.exe - Unable to Locate Component
"This application has failed to start because MSVCRTD.dll was not found. Re-installing the application may fix this problem"
Pardon me, what application is referred upon in the context?
<cyndi>
Cyndi,
Search for MSVCRTD.dll on your system. This file comes with Visual Studio. You need to add the path to it in your PATH (environment variable).
Are you still building using the .Net compiler?
Ricky
Hi Ricky,
Yes, I'm still building with my .NET compiler. I believe that MSVCRTD.dll should reside in the Winnt/System32 folder, but it's not. This link below should be of interest to you, titled: "Where is msvcrtd.dll for the 7.0 compiler" which informs that "The DLL CRT has been renamed in VS.NET to msvcr70.dll, and the debug version
is msvcr70d.dll"
http://www.dotnet247.com/247reference/msgs/1/7824.aspx
As such, the solution to resolve this error has become beyond my capability. I've mentioned earlier that I'm using WinXP Pro, and Mike Smith wrote that "The old runtime (MSVCRT.DLL) has been shipped with NT at least as far back
as 4.0".
What if I download a copy of this dll into the appropriate folder? I'll give that a shot. Please notify me if the consequence of this action is undesirable.
Cyndi
Ricky,
I've placed a copy of MSVCRT.DLL into the Windows/System32 folder. Currently, the building the BuildAllStatic Solution no longer complains about the missing dll, but I have LNK4221 errors.
E.g. EkRefCount.obj : warning LNK4221: no public symbols found; archive member will be inaccessible
In order to portray my problem, I've set up a webpage for you to access the BuildLogs from my .NET compiler.
http://cyndilum.tripod.com/
Cyndi
ps: is this helpful?
Hi Cyndi!
We released a .Net (VC7) binary distribution for pmt-1.1beta. The documentation isn't up to date, but it will be for our 1.1 release. The project settings in the AccessorTest and PmtInterpreterTest are set up so that all you have to do is:
- Download the win32 binary distribution of xerces version 1.2 from http://xml.apache.org/xerces-c/
- Set environment variables PMT_XERCES_INC_PATH and PMT_XERCES_LIB_PATH to the include and lib directories, respectively, in the xerces distribution. For example: C:\xerces-c_1_2_0-win32\inc and C:\xerces-c_1_2_0-win32\lib
- Add pmt-1.1beta\bin and xerces-c_1_2_0-win32\bin to your Path
- Build test\AccessorTest\AccessorTest.sln and test\AccessorTest\AccessorTesti.sln and run the tests. Compare the results to GroundTrue.txt.
- Build test\PmtInterpreterTest\PmtInterpreterTest.sln and test\PmtInterpreterTest\PmtInterpreterTesti.sln and run the tests. Compare the results to GroundTrue.txt.
NOTE: There are some issues with the PmtAccessor DLL build, so I don't expect AccessorTesti to work. But the static libraries should work fine.
I hope this helps!
Ricky