"Dimitrie O. Paun" dpaun@rogers.com writes:
In fact, I had something a lot simpler in mind. Currently, we define a variable called resources in the .spec.c file, which is later used in the nt_header structure. The idea was to simply generate the resources tree in a separate .c file, rename it to something like __wine_<spec file name>_resources, and make it non-static. Later, we can use it in the nt_header structure, just like we do right now. We still need to transfer the size of the resources...
The biggest problem is if you want to support multiple resource files. But as long as you don't break the current .res support that wouldn't matter too much I guess.