a few things you should mention...
- you can compile resources as a dll under windows and then load the dll
with wine. That's what we do for canvas. This is probably not ideal, but
most of my problems porting were in the code. We very seldomly have to
change the resources for the porting process. But wrc does work for most
cases...
- if you have questions about loading dlls, I can give you some answers. We
had to do a lot of dll loading backflips for canvas to run... We load our
cvres32.dll, which is a native windows dll compiles in msvc for our
resources. We load libwine.so and all the little dlls. And we also load our
own *.cvt files which are really .so files. They're our external tools. We
compile them in gcc with the -shared flag. They also have their own
resources. Wrc gives you a .a file, which must be compiled with as. as
gives you a .o file, which you link into your executable (or in this case
your shared library)
Do we still have to run the resources through gcc with the -E flag first in
the latest wrc?
- the error messages can be turned off or turned up with options to
configure like --enable-trace-msgs=wireoff or --enable-trace-msgs=wireon .
Take a look at configure.
- you probably want to compile your winelib with --disable-debugger, at
least for the release version of your app.
I think we should beef up this faq and our documentation for wine1.0.
People who want to do big projects with wine are probably going to need
lots of documentation. I know it would've helped us...
___________________________________________________________________________
Michael Cardenas
http://www.fiu.edu/~mcarde02
http://www.deneba.com/linux
