If it's impossible to make correct .rc files (without the hassle of using backends), then Marc's way is a way to go. There is such tool by Wine, which uses .spec, it may need writing a MSVC-backend though,.
WBR, Aleksey Bragin.
On Nov 9, 2007, at 10:56 PM, Alex Ionescu wrote:
I think you're all missing the point.
As it stands now, MSVC won't even READ most of your resource files because you've decided to write them in a way that violates the .rc standard and that only binres/windres/whatever-you-call-that- incompatible-garbage can parse.
Mark's proposal, apart from fixing all the problems he brought up, will finally allow you to write resource files that both MSVC and your-retarded-rc-compiler-name-goes-here can understand, with minimum effort. Right now, you're all stuck rewriting all your .rc files and creating .msvc.rc files.
By the way Mark, you should extend this to definition files. Once again, MSVC is incompatible with all the ReactOS .def files, which have been tailored so that Mangle32-gcc can understand them, so you'll have to create msvc.def files as well.
The more rbuild can generate independently, the better. You get MSVC files *after* running "make msvc8", and it's that step that would be creating the .def/.rc files for MSVC anyway -- what exaclty is it all you're complaining about regarding "MSVC" compatibility? You don't have it, how the hell can you lose it, and more importantly, why is the only suggestion that will finally let you have it "disliked"?!
You make no sense.
-- Best regards, Alex Ionescu