I noticed that others have more information when they look at the checkres file.
My application creates res.log not checkres.log and it only shows the type of resource and a number.
For example:
BMP
0
BMP
/0('(,(')/
FONT
0
I would really like to see what program and line # associated with the resource.
Nobody can even point me in the right direction? I really want to track down the resource problems.
Gale,
Do you compile with -l parameter (no line numbers) ? Try to compile without this parameter.
I use commercial xHarbour so I don't normally set any parameters, but I will check. If line numbers were not included, would tracelog() still show a trace with line number? Here is an example of what mine looks like.
[c:\projects\diwin11\DIWIN.PRG->MAIN] (91)
Type: C >>>Test Trace Log Entry<<<
OK I checked the compiler log and it does not use -l. Here is one of the compile lines in the log
xhb.exe -o"obj\DIWIN.c" -m -n -pOobj\ -q -gc0 -B -I"C:\fwh\include" -I"C:\xHB\include" -I"C:\xHB\include\w32" "c:\projects\diwin11\DIWIN.PRG"<<<
Ok, I might have found the problem.
Either there is an older checkres inside fivehcm.lib and it is linked before fivehmx.lib
or
fivehmx.lib has an older version in it.
If I compile and link c:\fwh\source\function\checkres.prg directly in the application, checkres() works as expected.
Does someone have an updated .xbp file to re-created fivehmx.lib