Cross-platform resource API

[Jean-Claude Gervais]

Thank you very much, Eric,

	For taking the time to help me.
	I'm afraid I may not have explained my problem very clearly:

	First, if I use Winelib, must I bind the resources to my executable?
The reason I ask is because since I am developing an application for the
Mac, can I bind resources to the Macintosh exectable? I thought that
that might be a problem.

	I understand that Wine has components in it that are like a system
loader, meaning that it is able to bring the executable image into
memory and then resolve the .DLL entry points it needs. This is more
than what I need, actually.

	Also, I don't expect that it can do this with a Macintosh executable,
or can it?

	That's why I was wondering if the resource-manipulation routines can
read .RES files, which should (in theory) be platform independant.

	OK, so in essence, what I am looking for is portable code that will be
able to walk a .RES file and load things from it.

	I'm not as familiar as many people on this list with the internals of
Wine, so that's why I am asking.

Thanks.

	
On Tue, 2003-11-11 at 15:08, Eric Pouech wrote:
> Jean-Claude Gervais wrote:
> > Hello,
> > 
> > I'm currently porting a Windows application to the Mac and Linux.
> > 
> > I've got many details worked out but the one that I am still researching
> > is how to load resources like strings and bitmaps.
> > 
> > What I would like to do is distribute the resources the application uses
> > as a .RES file that I would then manipulate with something like the
> > LoadResource function.
> > 
> > I have read that work has been done in the Wine project to make it able
> > to be used by other projects like ReactOS and Cygwin.
> > 
> > Is the Wine source-code structured in such a way that it would be
> > possible to extract the LoadResource function and do this?
> > 
> > Is there a simpler way?
> if you want your app to be a winelib app, then this is not an issue, 
> you'll be able to directly use any win32 api you want (starting with 
> LoadResource & LoadString), as well as putting the resource itself into 
> the executable.
> See the doc for the details to build a winelib app.
> A+
>