Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom plugin can't be detected by HitFilm pro 13 #81

Closed
ysdffsdf124324 opened this issue Jul 18, 2020 · 5 comments
Closed

Custom plugin can't be detected by HitFilm pro 13 #81

ysdffsdf124324 opened this issue Jul 18, 2020 · 5 comments

Comments

@ysdffsdf124324
Copy link

Plugin I developed can't be detected by hitFilm pro 13, I sure the compiled .ofx file is in the proper place, and in the proper bundle format. Can anyone tell me how to solve this problem?

@garyo
Copy link
Contributor

garyo commented Jul 18, 2020

OS? Check that you're exporting the OFX symbols and they're not C++-mangled.

@ysdffsdf124324
Copy link
Author

The operating system is windows10, and the exported plug-in extension is .ofx.
What does "C++-mangled" mean? ofx file was generated using Visual Studio 2017.

@garyo
Copy link
Contributor

garyo commented Jul 19, 2020

On Windows, you can use Dependency Walker to check what symbols are exported from a DLL (or .ofx). Make sure the OFX symbols use __declspec(dllexport) and extern "C".
For more, see MS extern "C" and MS __declspec

@Dithermaster
Copy link
Contributor

Dithermaster commented Jul 19, 2020 via email

@ysdffsdf124324
Copy link
Author

I found the reason, because some dynamic libraries used in the plug-in are not linked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants