On wtorek 26 paÅdziernik 2004 11:52 am, Juan Lang wrote: > Michael wrote: > > There is also a DES implementation in dlls/advapi32/crypt_des.c. > > However, this one is not exported by advapi32.dll. I could copy the > > code over to dlls/rsaenh, but this would mean unnecessary code > > duplication. How are such cases handled in wine typically? > > They are typically handled by copying the code. If linking between the > two requires a private export, then our DLLs can't work with native ones, > and that's something we try to avoid. If we use a static library, the > number of static libraries can potentially get very large, and the > makefiles unmanageable. It's really best to accept code duplication, > especially for something like DES that is quite stable.
What about simply linking in the required object files in rsaenh w/o generating an intermediate static library? Cheers, Kuba Ober
