Hi. I haven't massively familiarized myself with your problem, but I just stumbled across this in the documentation and thought it sounded related:
DLLs needed by a plugin can be placed in myplugin\res\libs\win64; DYLIBs can be placed in myplugin\res\libs\osx.
That's great, Andreas. Thanks! I'll kludge on until then.
Hi. I haven't massively familiarized myself with your problem, but I just stumbled across this in the documentation and thought it sounded related:
DLLs needed by a plugin can be placed in myplugin\res\libs\win64; DYLIBs can be placed in myplugin\res\libs\osx.
I'm using the project tool to build a plugin. I'd like to reuse a library built in my regular project structure, but I'm having a bit of trouble adding it to the Project Tool structure.
Critically, it seems like source files added to a project with "Include.Win=" must have either .h or .cpp extensions. At least, all of the files I try to add with a .cc extension aren't taking.
I should also mention that I am adding files outside of the sdk directory using "../../../../../" style paths, which I know is not recommended, but has worked well for all of my .cpp files. Could this be the problem?
Before I start extensively copying and renaming, is my assumption correct? Is there no way to force the tool to add a .cc file to my project? If so, is this documented anywhere?
Regards,
Sean