I have a plugin that compiles, links and run under R20.
Now I want to port it to R21.207.
I downloaded the latest Project Tool, changed projectsettings.txt (for the solution and for the plugin).
I use Windows 10 and VC++2017 version 15.9.17.

Now I get the following error:

The first 5 are cinema 4d errors.
The last 3, 'strange' errors in my code.

Here some more info.

The solution projectsettings.txt

Platform=Win64;OSX
Type=Solution
Solution=\
	plugins/cinema4dsdk;\
	plugins/maxonsdk.module;\
	plugins/CommandLineRendering

And the project projectsettings.txt

// Supported platforms
Platform=Win64;OSX

// Type of project
Type=DLL

// this plugin depends on these frameworks:
APIS=\
  cinema.framework; \
  misc.framework; \
  image.framework; \
  core.framework; \
  python.framework

// Enable some advanced classic API support; not needed for hybrid plugins
C4D=true

// Plug-in code-style check level
stylecheck.level=0

// Custom ID
ModuleId=net.maxonexample.commandlinerender

• you're using different IDE project files for R19 and R20?

• you've just ported the code from R20 to R19 and not copied-pasted project related settings?
  I took an old R19 project and started from there.
  I just copied the sources from R20 to the R19 project.

• you're able to compile the cinema4dsdk on R19 without any problem?
  No issues when compiling.

Here the Solution Explorer.

Projectsettings.prop

<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup Label="UserMacros">
    <MAXON_ROOTDIR>..\..</MAXON_ROOTDIR>
  </PropertyGroup>
  <PropertyGroup>
    <_ProjectFileVersion>10.0.40219.1</_ProjectFileVersion>
  </PropertyGroup>
  <ItemGroup>
    <BuildMacro Include="MAXON_ROOTDIR">
      <Value>$(MAXON_ROOTDIR)</Value>
    </BuildMacro>
  </ItemGroup>
</Project>

Where can I check the Cinema 4D static libs?

Yes, I think so too.
Thanks.

We developed a new plugin for R20, but we still have users on R19.
So, we need to compile the plugin also for R19.
Compiling is ok, but when linking I get the following error:

Severity	Code	Description	Project	File	Line	Suppression State
Error	LNK2001	unresolved external symbol "void __cdecl maxon::_ConsoleOutputC4D(enum maxon::OUTPUT,class String const &,__int64,char const *)" (?_ConsoleOutputC4D@maxon@@YAXW4OUTPUT@1@AEBVString@@_JPEBD@Z)	commandlinerendering	C:\Program Files\Maxon\CINEMA 4D R19.024\plugins\CommandLineRendering\commandlinerender.obj	1	

What am I missing?

Maxime pointed me this great example ExecutePythonScript() of running a python script from c++.
See https://plugincafe.maxon.net/topic/12439/reading-script-file-into-memory/4

I succeeded to compile this example in R20.
Now, because we still have user running R19, I want to do the same in R19.

Is this possible?
Is there a similar example for R19.
Especially, setting scope variables is really good and what I need.

I can use the example from https://plugincafe.maxon.net/topic/8164/10638_can-c-execute-python-solved/5, but that one does not support scope variables (I guess).

And yes, it works.
Thanks.

Yes, I am referring to that page.
I saw that statement, but I assumed it was the main definition for the python plugin.

  // set __name__ = __main__
  scope.Add("__name__"_s, maxon::Data("__main__"_s)) iferr_return;

If I understand you correctly, I can add different parameters with different values.
For example:

  // set __param1__ = "c:/temp"
  scope.Add("param1"_s, maxon::Data("c:/temp"_s)) iferr_return;
  scope.Add("param2"_s, maxon::Data(220)) iferr_return;

I use the example from the Python Manual, to start a python script from C++.
How can I pass additional variable to the python script.
For example, a path?

To summarise, there are 2 projectdefinition.txt files.

1. on main / sdk level, Define which project (plugins, etc.)
   Example:

Platform=Win64;OSX
Type=Solution
 
// defines the level of rigour of the source processor's style check
stylecheck.level=0

Solution=\
	plugins/cinema4dsdk;\
	plugins/maxonsdk.module;\
	plugins/commandline;\
    plugins/CommandLineRendering

2. on plugin level, // Configuration of a custom solution in the projectdefinition.txt file
   Example:

// Supported platforms
Platform=Win64;OSX

// Type of project
Type=DLL

// this plugin depends on these frameworks:
APIS=\
  cinema.framework; \
  misc.framework; \
  image.framework; \
  core.framework; \
  python.framework

// Enable some advanced classic API support; not needed for hybrid plugins
C4D=true

// Plug-in code-style check level
stylecheck.level=0

// Custom ID
ModuleId=net.maxonexample.commandlinerender

@PluginStudent said in Reading script file into memory:

You have to define the APIS in the projectdefinition.txt of your plugin.

Not in the projectdefinition.txt of the solution.

Great, tht solved it. Thanks!