Re: (Win32) How do we re-distribute ObjC programms?

[Fred Kiefer]

The way to handle this with GNUstep on Windows is to use the
"standalone" file system layout in GNUstep make. Best to start reading
the documentation here :-) Start with the README.MINGW one as this has a
section "HOW TO SHIP YOUR GNUSTEP APPLICATION TO WINDOWS USERS". This
explains what needs to be done. Next try the --with-layout=standalone
switch for make and rebuild the whole of GNUstep plus your application.
As far as I remember this is currently undocumented but should do about
the same as explained in the README file.

If you still have questions after reading and trying all that, feel free
to mail to me personally (even in German) for further questions.

Hope this helps,
Fred

On 29.11.2013 21:30, Kevin Ingwersen 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 <ivucica@gmail.com>:
> 
>> 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 <ingwie2000@googlemail.com> 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!