Re: Winelib Getting Started 1.3.2. Test Drive
Robert Muller wrote: Dee Ayy wrote: | As a newbie, the statement It can be found in the programs subdirectory. | had me lost. [...] At this point, the sentance that gave you problems could be modified to say: It can be found in the programs subdirectory of the wine source. There is one other part that is out-of-date: the procedure described won't create the 'notepad2' script. It would be better to change that part of section 1.3.2 to suggest you run 'wine notepad2.exe.so' or to run 'ln -s ../../tools/winewrapper notepad2' to create the script. Aside from that, the instructions look good to me. Eric
Re: Winelib Getting Started 1.3.2. Test Drive
Eric Frias [EMAIL PROTECTED] writes: There is one other part that is out-of-date: the procedure described won't create the 'notepad2' script. It would be better to change that part of section 1.3.2 to suggest you run 'wine notepad2.exe.so' or to run 'ln -s ../../tools/winewrapper notepad2' to create the script. Aside from that, the instructions look good to me. winegcc should create the script. If it doesn't it's probably because winemaker is not invoking it correctly. -- Alexandre Julliard [EMAIL PROTECTED]
Re: Winelib Getting Started 1.3.2. Test Drive
Alexandre Julliard wrote:
Eric Frias [EMAIL PROTECTED] writes:
here is one other part that is out-of-date: the procedure described
won't create the 'notepad2' script.
winegcc should create the script. If it doesn't it's probably because
winemaker is not invoking it correctly.
That was the problem. Winemaker was invoking 'winegcc -o foo.exe.so',
which suppresses the wrapper script. If it's invoked as 'winegcc -o
foo.exe' it generates the wrapper script as desired. Something like the
attached patch should fix the problem.
Eric
--- wine-0.9.15/tools/winemaker 2006-06-08 15:06:43.0 +
+++ ../wine-0.9.15/tools/winemaker 2006-06-20 14:17:36.0 +
@@ -1749,7 +1749,11 @@
} else {
print FILEO \t\$(CC);
}
- print FILEO \$(${canon}_LDFLAGS) -o \$\@ \$(${canon}_OBJS)
\$(${canon}_LIBRARY_PATH) \$(DEFLIB) \$(${canon}_DLLS:%=-l%)
\$(${canon}_LIBRARIES:%=-l%)\n;
+
+ # for .EXEs, tell winegcc to generate 'foo.exe', which will cause it
+ # to generate both 'foo.exe.so' and the 'foo' wrapper script.
+ my $output_file = @$target[$T_TYPE] == $TT_DLL ? \$\@ :
\$(${canon}_MODULE);
+ print FILEO \$(${canon}_LDFLAGS) -o $output_file \$(${canon}_OBJS)
\$(${canon}_LIBRARY_PATH) \$(DEFLIB) \$(${canon}_DLLS:%=-l%)
\$(${canon}_LIBRARIES:%=-l%)\n;
print FILEO \n\n;
}
}
Re: Winelib Getting Started 1.3.2. Test Drive
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dee Ayy wrote: | As a newbie, the statement It can be found in the programs subdirectory. | had me lost. It seems that the Winelib guide assumes that you know how to download the wine sources already. (Quick and dirty meathod of downloading the latest official tarball: On the main WineHQ page, the latest announcement Wine 0.9.x released or somesuch has a link available now; move it to an appropriate place, then unarchive it: $tar -xjf wine-0.9.15.tar.bz2 or somesuch) At this point, the sentance that gave you problems could be modified to say: It can be found in the programs subdirectory of the wine source. - -RFMuller -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFElz0yjfMdLxNd9ZERAqW4AKD2XDfJCevbr/qipE4mT0FVhX60eQCgzSm0 Hp4nNg6jwdIsMrik6hA7kFs= =lg1u -END PGP SIGNATURE-
