On Tue, 18 Nov 2008, Szak�ts Viktor wrote: Hi Viktor,
>>> Anyhow, it turns out - miracle - that there is about >>> 50MB worth of _static libs inside_, plus the executable. >> There is no even single static library or binary in GoogleEarthLinux.bin. >> All libraries and executable files are linked dynamically. >> So it's rather bad example ;-) > Okay, let's pick nits and let's try to avoid my point. > So sorry for saying the wrong word. They are _privately stored > dynamic libs_. Conceptually it's the exact same as if they were > linked right inside - staticly - to the executable. In any case > they are shipping the dynamic libs along with the executable and > storing them in the exact same directory. It's the same as if > hbrun would get shipped a harbour.dylib along with it in the same > dir, and if my app would ship with a local libssh2.so, instead > of using the OS one. > So physically they are separate but logically they belong together, > they are installed in one dir, and there is no additional/external > OS dependency. I do not see any way that you may change you preferences. Inside the start script of this applications you have all settings necessary in any *nix like system to create custom shared library set you were asking in the past. You do not see it but you are finding it as confirmation for keeping static builds. As Marek said few times in the past we can talk but you will make what you want. Please do it. I believe you will create perfect installation packages for MacOSX, created by f.e. mpkg_macosx.sh. You will check how and where perl, python, gcc and other languages are installed in MacOSX, if necessary you will consult the localization and installation form with some MacOSX gurus and the result will make all MacOSX users happy. Please only be so kind and do not change existing functionality as long as this alternative version will not be ready. I'll commit small modification for hb-func.sh so you will be able to easy control default -static/-shared switch state in final hb* scripts. And I'll reactivate the envelope code use in mpkg_tgz.sh using some other textutil/fileutil commands which should work with most of POSIX systems. I hope they will work also for MaxOSX so it should help you if you will need some simple installer. This is all what I can do. Other work on MaxOSX installer will have to be done by real MacOSX users in new MaxOSX build script. For me this closes the subject. best regards, Przemek _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
