-
Notifications
You must be signed in to change notification settings - Fork 512
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
How can I rename the library name, specific for module? #715
Comments
Try the And yes, it's fine to ask questions here. |
@tritao That still applies the shared name to all of the modules. What I need is specific name for each module (in particular the name of the header file) |
You could use CheckSymbols = true but this will only work if you pass your libraries themselves to your set up, per module - module.LibraryPaths.Add("path_to_dll_a") and module.Libraries.Add("dll_a"). |
Alternatively, @tritao 's suggestion works too. SharedLibraryName is a per module setting as well so you can have different ones as necessary. |
@ddobrev I've tried setting it up per module, but it still applied one of them (it applied |
I have following set up 4 dlls:
dll_a, dll_b, dll_c, dll_d
. Some of them use each other. Each has it's own separate headerdll_a.h, dll_b.h, dll_c.h, dll_d.h
(sorry if I write something that sounds weird to C guy, I don't know C much). Each of the header is located in the different folder, and has additional includes.My current setup is next (simplified);
This generates different classes for extern calls (named
dll_a
,dll_b
...), but every of them has[DllImport("PLT", ...]
, when I want[DllImport("dll_a", ..
fordll_a
,[DllImport("dll_b", ..]
fordll_b
.I've also tried having separate
ILibrary
for each of the header, but this generates copies of data structures (for exampledll_c
has datastructure used in API fordll_a
anddll_b
, thus it is generated 3 times). They become not interchangable, so I cannot call:P.S. Is this correct way to ask questions? As I understood google group is not monitored too much.
The text was updated successfully, but these errors were encountered: