Just words of encouragement: Congratulations! Now you're a researcher and an explorer. Be sure to document your journey along the way ;)
The easiest route to take would be to get people to install core GNUstep libraries first, but if you want to distribute minimum GNUstep runtime along with the executables, you'll simply have to figure out yourself. I think there was some work on shipping "standalone" app bundles, but again -- you should explore this yourself. On Fri, Nov 29, 2013 at 8:30 PM, Kevin Ingwersen <[email protected]>wrote: > Well I basically just wanted to figure out which parts of GNUstep i must > add to the executable in case of redistributing to a target which does not > have a trail of GNUstep. > Do you have a suggestion how that could be done? > Am 29.11.2013 um 21:28 schrieb Ivan Vučica <[email protected]>: > > > Microsoft's Dependency Walker. I believe it comes with Visual Studio. > > > > Although if you don't know what you're doing, you might end up > distributing less or more dlls than you should. Ideally your build system > should handle this for you, and if it doesn't, you should make it handle it. > > > > Regards, > > > > Ivan Vučica > > via phone > > > >> On 29 Nov 2013, at 17:43, Kevin Ingwersen <[email protected]> > wrote: > >> > >> Hey there. > >> > >> I just talked with a friend, and me sort of reminded me, that some .exe > files require their DLLs in the same folder as they themselves are located. > On a mac, I can find out all the linked dynamic libraries using apple’s > otool: > >> > >> $ otool -L php > >> php: > >> /usr/lib/libz.1.dylib (compatibility version 1.0.0, current version > 1.2.5) > >> /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current > version 1.0.0) > >> @executable_path/../usr/lib/libssh2.1.dylib (compatibility version > 2.0.0, current version 2.1.0) > >> /usr/lib/libedit.3.dylib (compatibility version 2.0.0, current > version 3.0.0) > >> /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current > version 5.4.0) > >> /usr/lib/libpanel.5.4.dylib (compatibility version 5.4.0, current > version 5.4.0) > >> @executable_path/../usr/lib/libmcrypt.4.dylib (compatibility version > 9.0.0, current version 9.8.0) > >> @executable_path/../usr/lib/libltdl.3.dylib (compatibility version > 5.0.0, current version 5.0.0) > >> /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current > version 7.0.0) > >> @executable_path/../usr/lib/libgpgme.11.dylib (compatibility version > 20.0.0, current version 20.1.0) > >> @executable_path/../usr/lib/libpng16.16.dylib (compatibility version > 20.0.0, current version 20.0.0) > >> @executable_path/../usr/lib/libcurl.4.dylib (compatibility version > 8.0.0, current version 8.0.0) > >> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current > version 1197.1.1) > >> @executable_path/../usr/lib/libassuan.0.dylib (compatibility version > 5.0.0, current version 5.1.0) > >> @executable_path/../usr/lib/libgpg-error.0.dylib (compatibility > version 11.0.0, current version 11.0.0) > >> @executable_path/../usr/lib/libgcrypt.11.dylib (compatibility version > 20.0.0, current version 20.2.0) > >> /usr/lib/libxml2.2.dylib (compatibility version 10.0.0, current > version 10.9.0) > >> /usr/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current > version 50.0.0) > >> /usr/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current > version 50.0.0) > >> /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP > (compatibility version 1.0.0, current version 2.4.0) > >> > >> On linux, there is „lld“ as far as I remember. But…whats the tool to do > this on a Windows maschine? o.o’ > >> > >> Kind regards, Ingwie! > >> _______________________________________________ > >> Discuss-gnustep mailing list > >> [email protected] > >> https://lists.gnu.org/mailman/listinfo/discuss-gnustep > > -- Ivan Vučica - [email protected]
_______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
