Header files not loading in VS2010 & R13



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/09/2011 at 12:33, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:   13 
    Platform:   Windows  ;   
    Language(s) :     C++  ;

    ---------
    I've been making stand alone plugins just fine with VS2010 & the R12demo.
    What I do is this:
    -Create an empty project
    -Add the debug & release property sheets
    -From the source folder. Add my main.cpp & plugin.cpp files

    What would happen next is VS would then automatically load all the .h files from the cinema4dsdk into my "External Dependencies" folder.
    But with R13. That's not happening.😢

    Any ideas how I can get all of those .h files loaded?

    -ScottA



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 13/09/2011 at 15:35, xxxxxxxx wrote:

    I noticed that they changed some things in the property sheets.

    R12: description,..\..\
    R13: description,$(C4D_API_PATH)
    And
    R12: OutputDirectory="$(SolutionDir)obj$(ProjectName)$(PlatformName)_$(ConfigurationName)"
    R13: OutputDirectory="$(ProjectDir)"

    Could this be the reason why the dependencies are not loading properly?
    Why did they even change these files? R12 was the first version that actually compiled properly without having to edit any of these files right out of the box.
    Now it looks like we're back to problems again.

    -ScottA



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 14/09/2011 at 05:54, xxxxxxxx wrote:

    Hey ScottA,

    When I start a new project, I copy the cinema4dsdk folder and delete all sources/main, unnecessary files. After that, I use NotePad++ and replace all cinema4dsdk words to my pluginname. Works good.



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 14/09/2011 at 07:32, xxxxxxxx wrote:

    I don't like doing it that way because it includes the API folder. Which is a duplication of the same header files in my plugin's External References.
    It's been a long time since I saved a plugin with the API folder included. But I remember when I did it it really pumped up the file size. So I quickly found a better way through referencing the API.

    I much prefer to reference the API.
    That way I can store just my plugins as source files. Which are kb in size opposed to meg.
    And if I want to compile them to work on them. I can just add the property sheets, Set a few attributes, then build them.

    If I can't get an answer about what's been changed in R13. And why the header files don't import properly anymore. Then I'll have no choice to use that method of copying the SDK and cutting things out. But Blech...I really hate that method.🤢
    Referencing the API is soooo much nicer.

    -ScottA



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 14/09/2011 at 08:10, xxxxxxxx wrote:

    Just some preliminary information about the R13 SDK and VS2008/2010.

    http://sdk.maxonpodcast.de/r13_sdk_1.pdf
    http://sdk.maxonpodcast.de/r13_sdk_2.pdf

    This info will be included in the docs of course.

    cheers,
    Matthias



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 14/09/2011 at 09:18, xxxxxxxx wrote:

    God Bless you sir. You always come through for me.🍺

    I don't know if this is frowned upon or not. But I don't use the copy SDK method.
    Instead. I build from scratch. This way I do not have the API folder in my projects.

    I copied the projectsettings.props file from the cinema4dsdk into my project's folder.
    Then in VS, I used the property manager to load it using the "Add Existing Property Sheet" option. The same way that you add the debug & release property sheets.
    When I did this all of the header files loaded into my External Dependencies folder as expected.
    There was also no need to do anything with the macro option or edit the files.

    Thanks for the help,
    -ScottA



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 14/09/2011 at 11:25, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    God Bless you sir. You always come through for me.🍺

    You are welcome :)

    I don't know if this is frowned upon or not. But I don't use the copy SDK method.
    Instead. I build from scratch. This way I do not have the API folder in my projects.

    I don't quite understand. Since Cinema R10 the API folder isn't included in the cinema4dsdk folder anymore.

    cheers,
    Matthias



  • THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

    On 14/09/2011 at 12:04, xxxxxxxx wrote:

    Forgive me. I'm still in the "What does thing thing do" stage with VS.
    I probably shouldn't have called it an API folder.

    Here's an image of the _api included in the sdk that I don't include in my plugins when I make them from scratch. To make the overall file size smaller:

    I'm not sure if this is frowned upon or not. But it does cut down on the file size if I don't include it in my own plugins.

    -ScottA


Log in to reply