Firstly, be sure to read (and perhaps print out) this entire page. It has must know info about memory and objects, etc.:
###What’s new in SketchUp 2017 M0
We updated our compilers for Windows and macOS. On Windows we are now using Visual Studio 2015 SP1 (targeting Windows 7). On MacOs we are using XCode 7.2.1 (with deployment target 10.10).
… (I know, you’d not be expecting the information you need to be “hidden” within another API’s release notes.)
###Build and Release Considerations
The C API library for Windows is built using Microsoft Visual Studio 2010 SP1.
SketchUp 2016 for Windows is built using Visual Studio 2010 SP1, and so plugins should be built with the Platform Toolset set to Visual Studio 2010 (v100). Using a different Platform Toolset will likely cause the plugin to fail to load and cause SketchUp to crash.
It also says:
It includes both 32-bit and 64-bit binaries.
Which is TRUE for SketchUp 2016, but NOT for SketchUp 2017.
So it seems the C SDK documentation has not entirely been updated for release cycle 17.
@ChrisFullmer @adam @tt_su
Wouldn’t a table be better in the SDK “Build and Release Considerations” section, giving columns for:
SDK release, Visual Studio version, XCode version, etc.
I was referring to an (now 3 year old) migration guide that was written for the 2014 release.
It is an HTML file, in the root of the SDK package.
It’s name is “
migration_guide.html” but I have not found an online url to it, (so open it from the root of the downloaded SDK package.)
This guide page may refer to this:
SketchUpDeprecatedModelExporterInterface : Old style exporters must implement this interface. Note that this interface is being deprecated.
New exporters must implement
There is also this page in the SDK documentation: