if I look at the issues:
- filename conversion (including #include to lowercase) = wine maker
handles this
Although wine supports this, it was bad coding that created this
problem, so wine is not at fault here.
if you have portability in mind, yes you should have your #include be
case
I would also like to try this below, but its not quite working, could
anyone offer some sugestions please?
from what I see:
- missing parts in ole. if you have the native ole DLLs handly, you
could try to run them.
- on the missing .pkg files, I believe you checked those files existed
on your
Hi,
Eric Pouech wrote:
Dan Kegel wrote:
http://codingstyle.com/articles/using-ms-vcpp-with-gnu-wine.html
was just mentioned at
http://developers.slashdot.org/developers/03/02/23/1939225.shtml?tid=156
Yup, I've been doing this, and the author is right: the
commandline tools show off a few rough
Hi
Dan Kegel wrote:
Eric Pouech wrote:
- the console creation at wcmd startup should we removed when run
under wineconsole (but, this would be rather annoying for some users).
I have a patch for this, but it would mean that there are two ways of
running wcmd: 'wineconsole wcmd
Dan Kegel wrote:
http://codingstyle.com/articles/using-ms-vcpp-with-gnu-wine.html
was just mentioned at
http://developers.slashdot.org/developers/03/02/23/1939225.shtml?tid=156
Yup, I've been doing this, and the author is right: the
commandline tools show off a few rough edges of Wine.
As more
Eric Pouech wrote:
- the console creation at wcmd startup should we removed when run under
wineconsole (but, this would be rather annoying for some users). I have
a patch for this, but it would mean that there are two ways of running
wcmd: 'wineconsole wcmd /switch_for_no_new_console' or 'wcmd'
http://codingstyle.com/articles/using-ms-vcpp-with-gnu-wine.html
was just mentioned at
http://developers.slashdot.org/developers/03/02/23/1939225.shtml?tid=156
Yup, I've been doing this, and the author is right: the
commandline tools show off a few rough edges of Wine.
As more people start using
