I was trying to compile a custom version of POVWin that doesn't need to use
the registry using Borland C++ Builder 3, and I got the following error
messages:
[C++Error] pvtext.c(1188): Undefined symbol 'REBARBANDINFO'.
[C++Error] pvtext.c(1188): Statement missing ;.
[C++Error] pvtext.c(1191): Undefined symbol 'rbBand'.
[C++Error] pvtext.c(1191): Not an allowed type.
[C++Error] pvtext.c(1207): Function call missing ).
[C++Warning] pvtext.c(1208): Possible use of 'hwnd' before definition.
[C++Warning] pvtext.c(1222): Conversion may lose significant digits.
[C++Warning] pvtext.c(1223): Conversion may lose significant digits.
[C++Error] pvtext.c(1227): Undefined symbol 'TB_SETIMAGELIST'.
[C++Error] pvtext.c(1231): Undefined symbol 'RBBIM_COLORS'.
[C++Error] pvtext.c(1231): Undefined symbol 'RBBIM_CHILD'.
[C++Error] pvtext.c(1231): Undefined symbol 'RBBIM_CHILDSIZE'.
[C++Error] pvtext.c(1231): Undefined symbol 'RBBIM_STYLE'.
[C++Error] pvtext.c(1231): Undefined symbol 'RBBIM_BACKGROUND'.
[C++Error] pvtext.c(1231): Undefined symbol 'RBBIM_ID'.
[C++Error] pvtext.c(1231): Undefined symbol 'RBBIM_SIZE'.
[C++Error] pvtext.c(1232): Undefined symbol 'RBBS_NOVERT'.
[C++Error] pvtext.c(1232): Undefined symbol 'RBBS_CHILDEDGE'.
[C++Error] pvtext.c(1232): Undefined symbol 'RBBS_FIXEDBMP'.
[C++Error] pvtext.c(1232): Undefined symbol 'RBBS_GRIPPERALWAYS'.
[C++Error] pvtext.c(1239): Undefined symbol 'RB_INSERTBAND'.
[C++Error] pvtext.c(1239): Undefined symbol 'LPREBARBANDINFO'.
[C++Error] pvtext.c(1257): Undefined symbol 'RBBS_FIXEDSIZE'.
[C++Error] pvtext.c(1265): Undefined symbol 'RBBIM_TEXT'.
[C++Error] pvtext.c(1288): Undefined symbol 'RBBS_BREAK'.
[C++Error] pvtext.c(1308): Undefined symbol 'TBSTYLE_FLAT'.
[C++Error] pvtext.c(1308): Undefined symbol 'TBSTYLE_LIST'.
[C++Warning] pvtext.c(1324): Conversion may lose significant digits.
[C++Error] pvtext.c(1348): Undefined symbol 'INITCOMMONCONTROLSEX'.

What is going on and how do I fix it?  It looks like an include file is
missing; however, I did not make any modifications to the code except for
the parts where it reads/writes the registry, and commenting out 4 lines in
windows.h that were interfering with compilation (C++ Builder insists on
treating the program as if it were written in C++).

Mark

Post a reply to this message

On Fri, 3 Sep 1999 00:31:36 -0400, Mark Wagner wrote:
>I was trying to compile a custom version of POVWin that doesn't need to use
>the registry using Borland C++ Builder 3, and I got the following error
>messages:

[...]

>What is going on and how do I fix it?  It looks like an include file is
>missing; however, I did not make any modifications to the code except for
>the parts where it reads/writes the registry, and commenting out 4 lines in
>windows.h that were interfering with compilation (C++ Builder insists on
>treating the program as if it were written in C++).

You need to add a declaration for COMMONCTRL_VERSION=0x400 in such a way 
that it applies to all source files.  In MSIE, this is in the project 
settings dialog.  I'm sure Builder has something similar.  If that doesn't
do what you need, you might also need to get the latest platform SDK include 
files from msdn.microsoft.com.

Post a reply to this message

Ron Parker wrote in message <37cfcc22@news.povray.org>...
>On Fri, 3 Sep 1999 00:31:36 -0400, Mark Wagner wrote:
>>I was trying to compile a custom version of POVWin that doesn't need to
use
>>the registry using Borland C++ Builder 3, and I got the following error
>>messages:
>
>[...]
>
>>What is going on and how do I fix it?  It looks like an include file is
>>missing; however, I did not make any modifications to the code except for
>>the parts where it reads/writes the registry, and commenting out 4 lines
in
>>windows.h that were interfering with compilation (C++ Builder insists on
>>treating the program as if it were written in C++).
>
>You need to add a declaration for COMMONCTRL_VERSION=0x400 in such a way
>that it applies to all source files.  In MSIE, this is in the project
>settings dialog.  I'm sure Builder has something similar.  If that doesn't
>do what you need, you might also need to get the latest platform SDK
include
>files from msdn.microsoft.com.


That fixed the problems I was having.  Now to track down the latest batch...

Mark

Post a reply to this message