Ok, success. Copying the plugin folder from pc to mac was the issue!

Ok, made it work now. Thank you so much.

I think we are talking past each other. You can of course build any project any way you like. An then make sure that your plugins link to the build result using the link options defined in projectdefinition.txt. But I think you want to include an already existing (non-plugin) project in the solution created by the Project Tool, right? And I think that is not possible. I guess you could add the project manually to the solution created by the Project Tool.

Hello, you find information how to run a plugin from within Visual Studio in the documentation: Development for Microsoft Windows - Running Plugins. best wishes, Sebastian

Hi c4dmac, thanks for following up here. With regard to the issue you've reported you can get fixed by reestablishing the executable bit on the kernel_app file found in the zip archive. To sum it up, upon downloading the project tool archive you have to: remove quarantine xattr -d "com.apple.quarantine" ./cinema4d_r21_project_tool_20190903.zip extract the archive (either via terminal or via finder) unzip -d ./cinema4d_r21_project_tool_20190903 ./cinema4d_r21_project_tool_20190903.zip re-establish the kernel_app executable bit chmod 555 ./cinema4d_r21_project_tool_20190903/kernel_app.app/Contents/MacOS/kernel_app Best, Riccardo

hello, if you can give us feedback that would be awesome. Cheers Manuel

I see, thanks for the quick reply. I will try it and if doesn't work I'll open a new thread about the topic. Cheers Christian

Thanks Sebastian, I will try that! /Filip

Thanks Sebastian! Looking forward for a fix. ;) Meanwhile I'll take care of your recommendation. Best, Robert

Here's an older blog post about VS property sheets. Still for VS2010, but the principle is still the same. Sharing project properties in Visual C++

I found the culprit. My cmyk.cpp file was inside of a folder. When I got it out and placed it alongside the main.cpp file, the project file created by the Project Tool finally opened in XCode. Now I'm getting other errors, but at least the problem reported in this post is solved.

Thanks Riccardo, I will look into that.

Hey that was it! Thanks

That's great, Andreas. Thanks! I'll kludge on until then.

Hi ello, no, you don't need to worry, the compiler won't check the remaining lines. It is a warning, we use internally to make people write better code. Usually smaller functions are easier to maintain and thinking about how to properly split and slice your code leads to better better results. By the way, compilers nowadays do quite a good job on inlining functions, so one does not need to be afraid of performance issues. But in the end this is probably also a matter of personal taste and so you can configure this in your projectdefinition.txt. See the Stylecheck options in our Project Tool documentation, there you have the option to set the maximum line count for functions (stylecheck.max-linecount=number). Please consider the use of tags and of our Q&A system. Cheers, Andreas

Hi, we have forwarded your ideas and suggestions toi our development. Add post build phases to the project. At least add a custom Run Script that runs a specified script so we can properly install the plugin. While I do see use cases for a post-build script/step option, it may not be needed for the purpose of installing a plugin. After all in R20 plugins can be located in arbitrary locations (like for example your project directory). You just need to add these locations via either preferences or via environment variable or command line option. (bug) XCode project gets corrupted if we add a file twice with Include. I'm not sure if I can follow here. Can you please check, if you are also lacking a release build option, if you run the project tool on a freshly unpacked sdk.zip? Actually you should have all the options shown in the screenshot below: Cheers, Andreas

Hi, glad you were able to solve your problem. We'll take this as a hint and see if we can improve our documentation in this regard. Cheers, Andreas

Hi rsodre, thanks for writing us. The Cinema 4D SDK has it's own structure which actually needs that both the plugins and the frameworks folder share the same parent folder and this is what the SDK toolset (sourceprocessor and projecttool) expects to work with. Any change to this structure may lead to unexpected behaviors and is highly discouraged. Using the workaround you pointed out in the projectdefinition.txt is not expected to work as you've already checked. On the contrary using symbolic links seems to work, but again this is not officially supported. For the sake of completeness the ln command I used is ln -s <path to frameworks> <path to plugins>/../. and I succeeded to compile all the shipped plugins under macOS 10.13.6 with Xcode 9.4.1 Cheers, Riccardo

Hi Riccardo! Thank you very very much for your detailed explanation. That helped me a lot and YEAHHHH....got it working Thanx in advance for your time! Best regards Andi

@césar-vonc said in C++ new plugin with Project tool fail: The informations a bit dispatched and I don't find the doc very clear, for example, there is no link to download Project Tool on the Project Tool page, and globally not enough examples in the sdk. Second sentence on this page: https://developers.maxon.net/docs/Cinema4DCPPSDK/html/page_maxonapi_projecttool.html Agreed, the link is not very well visible, but it says "The Project Tool can be obtained from developers.maxon.net" And of course, the docs are very helpful, it just needs a bit of reading. ;)