Skip to main content
Participating Frequently
November 25, 2024
Question

Indesign SDK C++: Samples Not Compiling

  • November 25, 2024
  • 2 replies
  • 1065 views

Brand new to C++ Plug In Development and trying to get the SDK Samples to run.

 

Using:

Indesign SDK 20.0.0.95

Indesign Debug Version 20.0.1D

Visual Studio 17.9.6

 

Can only get the "BasicLocalization" project to compile and run. The handful of other samples  "WriteFishPrice, BasicDialog..." I tried all encounter the same build error of "_MAX_INT_DIG:undeclared identifier" in xlocnum_back_vs2022_17_1.h.

 

What is causing this and how do I fix it?

This topic has been closed for replies.

2 replies

Inspiring
November 26, 2024

Make sure you are using the following -

 

VS 2022 - Version 17.9.6
Win SDK - 10.0.22621.0

Participating Frequently
November 26, 2024

Where do you see that the Win SDK should be 10.0.22621.0? 

Inspiring
November 27, 2024

@ryany27707769  - Read the SDK Documentation.

 

Also, you have validate by opening sample projects provided in the SDK.

Legend
November 26, 2024

Open the SDK documents index page. Check the compiler version in the requirements.  I don't have it around right now. Your 17.9.6 might be slightly off, when the header file already is named …17_1.h 

 

The xlocnum hack is notorious for compiler version dependency, down to the minor version number.

 

You'd either install the correct compiler version (at least something closer, e.g. 17.1.x), or hope that someone has provided an updated version of xlocnum_hack (e.g. in the developer area hosted on the prerelease site) and your use of a not specified compiler does not break at another point.

 

Apply similar considerations for the Xcode version. Xcode is also picky about the OS version - even a dot version can break things.

 

While major VStudio versions often can coexist, I've experienced a few times that a newer version broke the toolset of an older one. Installing older versions on top of a newer one is worse. I'm using virtual machines to preserve and isolate working environments, others sit on a pile of hardware - worth a second thought given recent changes at VMware.

Participating Frequently
November 26, 2024

I've posted my version numbers in the pictures. Can someone please confirm all my version numbers are correct?