When I created a customer module, I compiled it and got the DLL.
When I give the DLL to someone else to use, why can't I recognize the module in his AWE designer and can't find it in the list?
I have to send the complete customer module project to someone else as well.
And I have to add module path manually in AWE designer before I can use this module.
So Is it enough for others to get the corresponding DLL file to use the custom module? If not, which ones are still necessary?
Best Regards
Yue
9:49am
Hi Yue,
There are two steps to adding a module:
1. Add the .dll into the same directory containing AWE_Server.exe (typically located in<install directory>/Bin/win32-vc142-rel/)
2. Go File-> Set Module Path, and add the path to the folder structure of your module.
Were you able to complete both of these steps on the second machine?
-Kyle
1:20am
Hi Kyle.
Thank you for your answer!
My answer to your question is "yes".
What I'm more concerned about is that when I provide a DLL to someone, do I have to provide all the module files as well?
If I don't want others to see my specific implementation, what are the necessary documents to be provided if possible?
BR
Yue
10:22am
Hi Yue,
The module gets compiled into the .dll, so the source code does not need to be shared, however there are still some folders with information needed to import the module into Audio Weaver. I've attached a screen shot of the minimum amount of folders (including whichever files are enclosed) and files that should still be zipped and sent with the .dll
Hope that helps! -Kyle
10:17pm
Hi, Kyle.
Thanks for your comment.
That' very helpful !