On 22/07/2016 at 08:54, xxxxxxxx wrote:
User Information:
Cinema 4D Version: 17
Platform: Windows ;
Language(s) : C++ ;
---------
Hi,
it's not that big issue, but maybe someone has a quick tipp: Building any project with VS 2013 for R17 requires cinema.framework to be newly compiled. This is true also for the cinemasdk project. Seems that VS isn't able to store the status. I've already removed the file locks, without any effect.
Any suggestions are welcome.
On 25/07/2016 at 00:49, xxxxxxxx wrote:
Hello,
that's strange behavior, it typically should only be build once. I never experienced such behavior so I can only guess what might be happening on your system. Maybe it is related to some read/write rights. Are you working with a Cinema 4D installation in Window's "Programs" folders?
Best wishes,
Sebastian
On 25/07/2016 at 02:37, xxxxxxxx wrote:
I have to be a bit more clear: VS THINKS the framework would have to be compiled and thus shows the dialog window "famework outdated". When compiling the project, building is started but ends immidiately with the result:
1>------ Erstellen gestartet: Projekt: cinema.framework, Konfiguration: Debug x64 ------
1> cinema.framework.vcxproj -> C:\Program Files\MAXON\CINEMA 4D R17\plugins\ideematec_safefix\_obj\cinema.framework\x64_Debug\cinema.framework_Debug_64bit.lib
Yes, I run VS in administration mode with the plugin project in the C4D installation. I switched off showing the outdated dialog, so it's ok now.
On 26/07/2016 at 07:02, xxxxxxxx wrote:
Hi,
thanks, Klaus, for making us aware. We have found the cause of this behavior and it will most likely be fixed in one of the next releases.
On 05/10/2016 at 06:03, xxxxxxxx wrote:
Just to prevent this thread from beeing solved:
Unfortunately the problem has become worse with the 17.055 update. Now the framework is really completely built with each call of the compiler or debugger!
On 07/10/2016 at 08:31, xxxxxxxx wrote:
Hello Klaus,
I have found the reason, but I'm not sure yet, what caused it. We will have to investigate, what happened on our build servers. The reason your framework (and also the cinema4dsdk) project is always being rebuilt is, that several files (project files, sources and headers and also resource headers, string and resource files) have a file modification date in future. So VS is actually right to rebuild the projects if MAXON seemingly provides patches from the future.
A quick fix is to touch all files under frameworks and in plugins/cinema4dsdk. I did it here on the command line, using MobaXterm and the "touch" command. But there are also GUI tools to accomplish this. Like e.g. BulkFileChanger, but be warned, I haven't tried it here and MAXON will take no warranty whatsoever for any explosions of your computer or animals. So better look for a tool of your choice and trust.
We will now go and see, how to prevent this with any future releases.