Sample code to add an XP manifest to a program

Seldon · Post by **Seldon** » Thu Nov 13, 2003 9:55 pm

Definitely. Besides ResHacker has that bug and it can't be used always. I think it'd be very easy to allow the PBCompiler to accept other line parameters (that is a .RES file) that would pass directly to LccLnk. Fred, could you do this Fred for next release?

GPI · Post by **GPI** » Thu Nov 13, 2003 10:04 pm

Maybe a simple solution:

new CompilerCommand:

IncludeResource Type,Name,File
(For example for the manifest or additional icons)

IncludeResourceSource Type,Name,File
(Version-Resource must be compiled (to .res) before it can be used. At the moment jaPBe goRC; would be nice, when this is not needed anymore)

Seldon · Post by **Seldon** » Thu Nov 13, 2003 11:10 pm

That is good, though I'd leave the command line option too. For resource files already compiled, you'd only need:

IncludeResource "file.res"

as settings like name, type, etc.. are stored in the .RES file.

For source resource files (.rc) , PBCompiler could invoke the RC compiler by Microsoft (I think it's totally free) or LRC by LCC.

GPI · Post by **GPI** » Fri Nov 14, 2003 8:27 pm

And when the Fred will support resources, handling-routines would be nice, like addr=OpenResource(type,name), closeResource(adr), UseResourceIcon(name), UseResourceImage(name) ,....

GPI

Seldon · Post by **Seldon** » Fri Nov 14, 2003 9:56 pm

That would be nice, though API calls for resouces are easy to handle. Anyway.. I hope Fred will make the option to include our own .RES in the final EXE.
BTW... since I really DID NEED that for a project of mine, I've just hacked

the PBCompiler, so now it adds my resource to my DLL. Sorry, but I had no other choice. Of course, I won't give that modified version to anyone.