Hi Alex,
Don't know if Marc got your response before he left, so I will try to
take over.
No. I'm using CVS already.
I mean: Everything is ok. As long as I don't copy the gnustep folder
to another machine. Thereafter the Tab images aren't used anymore.
Actually if I copy the gnustep folder to an USB stick, delete it, and
copy it back to the same machine everything is working well. So I
assume GNUstep does some evil things outside of its folder.
Okay..hmm..You *are* sourcing GNUstep.sh on the machine you transfer
it to prior to copying it, yes?
No, I guess he didn't do that.
If not, the environment variables such as $GNUSTEP_SYSTEM_ROOT won't
be set.
I don't get this. I mean we are just coying files. How could sourcing
GNUstep.sh beforehand (the copy process) make a difference?
Are you executing apps from within msys, or from a windows command
prompt?
We tried both with equal effect.
If msys, make sure there are several $GNUSTEP_FOO envvars set, if
running the bin right from windows, make sure the envvars are set in
windows itself. I suspect this is the problem.
Could you be a bit more specific? Lloyd already tried to summarize what
would be necessary to deploy on a window machine. It is obvious that an
essential part is still missing. Any ideas? What could be the env var
responsible for letting GNUstep find the images for the close button
etc.?
Thanks a lot!
Regards,
Andreas
************************************************************************
***************
From: "Lloyd Dupont" <[EMAIL PROTECTED]>
Date: Do Mai 12, 2005 6:08:21 Uhr Europe/Berlin
To: "GNUstep Discussion" <[email protected]>
Subject: light GNUstep install on windows (for deployment)
Just to share with you my findings on what a light install of GNUstep
on windows would be:
�
1. copy these dlls (from $GNUSTEP/System/Tools) in your exe directory
(or in the application's path):
gnustep-base.dll
gnustep-gui.dll�
iconv.dll�������
jpeg62.dll������
libpng13.dll����
libtiff3.dll����
msvcr70.dll�����
objc.dll��������
zlib1.dll�������
�
Copy the directory $GNUSTEP/System/Library somewhere (in your
application directory?)
and in the main() of your application (before any GNUstep call) setup
the GNUSTEP_SYSTEM_ROOT env variable to the directory where /Library
was copied
(with something like putenv("GNUSTEP_SYSTEM_ROOT=.\"))
standart dos path are OK (like "GNUSTEP_SYSTEM_ROOT=C:\Program Files\My
Super GNUstep Program")
************************************************************************
***************
_______________________________________________
Discuss-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/discuss-gnustep
