Skip to main content
R
R0b_Evans
Known Participant
May 9, 2018
Answered

LNK1104: cannot open file 'libcpmt.lib'

  • May 9, 2018
  • 4 replies
  • 4066 views

I downloaded the Acrobat SDK samples and opened the 'All' solution.  When I try to build, for example, BatesNumbering, I get a LNK1104 error because it cannot open LIBCPMT.lib.

I am using the Visual Studio 2013 (v120) Platform Toolset within Visual Studio 2017.

This topic has been closed for replies.
Correct answer Test Screen Name

This will probably be making your life MUCH harder and I'd strongly recommend you work with the intended release. That said, it's a standard Microsoft library and you should be able to find it and adjust your project settings if you're comfortable with C linking setups.

4 replies

T
Test Screen Name
Legend
May 10, 2018

I'm sure the problem is soluble, and so will each of the other problems that comes up. It just may take longer and be more frustrating. As I said, this is a Microsoft standard LIB file, so just locate it and adjust the settings.

T
Test Screen Name
Legend
May 10, 2018

That's the recommended path. I use VMs to keep these things tidy.

R
R0b_EvansAuthor
Known Participant
May 10, 2018

I will install VS 2013 today and report on the outcome.

T
Test Screen NameCorrect answer
Legend
May 10, 2018

This will probably be making your life MUCH harder and I'd strongly recommend you work with the intended release. That said, it's a standard Microsoft library and you should be able to find it and adjust your project settings if you're comfortable with C linking setups.

R
R0b_EvansAuthor
Known Participant
May 10, 2018

So, what you are saying is that I should install VS 2013 and use it instead of using VS 2017 with the 2013 toolset?

T
Test Screen Name
Legend
May 10, 2018

Is that the Visual Studio release it was designed for? If not you’re probably going to have to do a lot of troubleshooting and adapting; I can’t recommend that course.

R
R0b_EvansAuthor
Known Participant
May 10, 2018

According to the SDK documentation, it was designed for Visual Studio 2013 (v120).  I do not have VS 2013 installed, but, of course, VS 2017 has that toolset available in the property settings.  When I initially opened the All solution in VS 2017, I did not convert the projects away from VS 2013.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices