Resource compiler problem

[hutch--]

Mike,

It sounds like if your build environment cannot be adjusted to work with resource.h and will only work with equates in C format, you need some other mechanism to construct the assembler equates as the two forms are incompatible. Where I have to use resource compilers that mess around with the RC file, I use the RC notation to "#include" problematic RC files so they can be edited by themselves without messing up the rest. RC.EXE supports the "#include" directive.

I doubt there is an automatic method around if you resource ID numbers keep changing, somewhere along the line you will need to do the conversion from the C format to ASM format, perhaps write yourself a parser that will do that if your build environment is so inflexible.

[Gunner]

The resource editor in radasm and probably the standalone resource editor from keitlo, allow you to export as equates

[dedndave]

ok - the IDE gets the resource.h file from someplace !!!!!
i sincerely doubt it is embedded in the EXE
add your #include to that

[mike2]

I don't want to sound unthankful, but I already wrote that (and how) I solved my problem 7 posts ago.

I have no idea why I always should mess with the *.h include files since the resource compiler understands #define. I could #include a million other *.h files and still not a single one would bring me even one step closer to the problem I asked here in the first place.

[hutch--]

Mike,

I am please to hear that you have solved your problem but issues that have been addressed are a bit wider than the specifics of how you have ended up solving your own problem. I have been using deviant resource editors since before 1990 and many have unusual quirks that were designed to suit the environment they were provided with but RC.EXE has worked much the same way for the last 20 years or so and it is generally the reference, not a resource editor. RESOURCE.H as a collection of equates for resource types is an old standard and while I have had resource editors that deviated from this in the past and wrote their own, they deviate from the historical standard.

[mike2]

I think we can definitely say that today not RC.EXE is the de facto standard for Windows programming but Visual Studio. All Windows C++ developement environments developed in the last 15 years (or even more) have the resource equates located in "windows.h" (#include winuser.h)

But no matter how this *.h file is called, it is - forgive my words - total bullshit to edit any global include files and to insert application specific constants there.

[dedndave]

perhaps the best thing you can do is to look for a different IDE