resent. got bounced on winehq (no route to host) from the MTA Eric Pouech wrote: > > michael cardenas wrote: > > > > That's no good. I'll figure out how to make a unified .so, that's what I need. > > > > I think we should still have an option for this in configure. > well, I'm not so sure it's a good idea: > > I assume that you want to ship a configuration by its own of your pgm > where you don't rely/mess with any other installed software (and you're > afraid of the 20 or so .so files embedding DLLs) > > if you package your app like ELF-main executable + libwine.so, then > there's still a risk that some of your users, installing some other > wine packages overwrite/erase/modify/put before in shared lib load > order another libwine.so file. that's not safe either > > anyway, issues with .so file will appear as soon as you use .so file > (no matter you use 1 of them or 20 of them) > > solutions that come to my mind are: > 1/ build your app as a single exec (libwine.a comes into play) > 2/ build your app as an exec plus a libwine.so file. > 3/ build your app as an exec plus a bunch of .so files > > from a distribution stand point: > 1/ is the easiest one. 2 and 3 can cause trouble if users change > the .so files somehow... you can in 2/ use another name for > libwine.so, like libwine_for_my_app_no_noone_can_use_it.so, but > there's no gain with solution 1 (except if you have several > execs sharing this .so file) > > from an execution speed point of view: > 3/ is the best one (less memory: only loads needed code), less > time (because less things to do) > > from a memory allocation point of view: > 3/ is also the best > > no, I'm not so convinced 2 (which is, AFAIU, what you request) is > the best solution. 1 or 3 seem better to me. > > obviously, 3 is not a valid solution today. as every day brings its > load of bug fixes, enhancements... people willing to ship need to > build their apps on something more rock solid. that's definitively > a limitation for 3/ (until wine 1.0 is ready). > > so my proposal would be: > - use 1 until wine 1.0 ships > - use 3 as soon as wine 1.0 exists, and build your apps on top of it > (as it's done with XFree, KDE...) > > A+ > -- > --------------- > Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) > "The future will be better tomorrow", Vice President Dan Quayle -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle
