Sorry for resuming this old thread but I have exactly the same problem. Any new idea about better solutions, i.e. due to improvements in newer Bridj versions?
Il giorno mercoledì 6 giugno 2012 11:50:05 UTC+2, @mit ha scritto: > > The library has a static/configuration data on which the native > functions work. This data is nothing but a Target (PCB/hardware) > configuration. > > Basically there are multiple user interface configurations - for each > such configuration we must attach a DLL. There is no limit on number > of such configurations. Every time user adds configuration we attach a > DLL to it (since it will have a seprate DLL configuration) > > I know it is really poor design. But the DLL is third party. To add to > issues there is no limit on number of DLLs loaded at a time. So you > can see that all has to be done at runtime. :( > > > -- You received this message because you are subscribed to the Google Groups "NativeLibs4Java" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
