Dimitrie O. Paun
dpaun at rogers.com
Thu Nov 21 18:53:44 CST 2002
On November 21, 2002 07:07 pm, Alexandre Julliard wrote:
> Sure, but as Wine developer it's easy for you to write a small wrapper
> script to run from inside the source tree.
The discussion got too theoretical. All I am saying is that right
now, working with Winelib is not pleasant. I can talk from personal
experience. And I think it's in our best interest to remove any
unnecessary hoops that you have to jump through to get apps compiled
with Winelib. It's just gonna get us more programmers.
Please keep in mind that for you, such changes are trivial. However,
Wine is a very, very complex beast, and even these things take time,
effort, and patience to figure out. And these are finite resources.
I'd much rather have developers worry about other things, then how
to make their app work with their Wine tree. For development, this
is an important point, and there's nowhere to turn to to figure this
one out. I've gone through the exercise, and it took me while. Plus
with Visual-MinGW which was dying on startup, I didn't know that
my script was OK. Hell, I didn't know that I was supposed to use
wineapplauncher until you told me! :)
I've appended the patch I had in mind for wineapploader. It's small,
doesn't hurt no one, and just helps people that want to work on
Winelib. It's untested, but that's what I have in mind.
--- programs/wineapploader.in.orig 2002-06-09 01:41:57.000000000 -0400
+++ programs/wineapploader.in 2002-11-21 19:43:28.000000000 -0500
@@ -48,5 +48,19 @@
if [ -x "$appdir/wine" ]; then exec "$appdir/wine" "$appname" "$@"; fi
+# now try to see if we're running out of the tree
+winedir=`ls -l "$appdir/$appnm" | sed 's/.*->//'`
+winedir=`cd $winedir/.. && pwd`
+if [ -x "$winedir/miscemu/wine" ]; then
+ export LD_LIBRARY_PATH WINEDLLPATH WINESERVER WINELOADER
+ exec "$WINELOADER" "$appdir/$appname" "$@"
# finally look in PATH
exec wine "$appname" "$@"
More information about the wine-devel