Hi,
As I understand one can use richview without buying it.
Is that true?
I have installed the components and and set up the paths to C:\Program Files\Borland\CBuilder6\Projects\Lib
For the library and C:\Program Files\Borland\CBuilder6\Projects\Bpl\
When I add a component to the form it looks for richview.h
I also changed it to richview.hpp but it still doesn’t compile.
I have the TaeRichEdit component also installed.
Should I uninstall it?
Regards
Greg
Problems compiling Richview projects
-
- Site Admin
- Posts: 17569
- Joined: Sat Aug 27, 2005 10:28 am
- Contact:
Yes, trial versions can be used without registering. They display registration reminders, but otherwise they are fully functional.
There is also very old freeware version available (as far as I remember, it does not have CB6 package)
After normal installing, C++Builder must add in units RichView.hpp and other HPP files, not RichView.H.
Usually this problem occurs when paths to TRichView are not added to C++Builder include path.
Menu Tools | Environment Options, tab Library, add path to TRichView files (where dcu, obj and hpp files are located) in "Library path".
In addition, it may be necessary to add this path in the project options:
menu Project | Options, tab Directories/Conditionals, add the path to trichview units both in "Include path" and "Library path".
After that, units must be generated correctly (with links to HPP instead of H), and projects can be compiled.
There is also very old freeware version available (as far as I remember, it does not have CB6 package)
After normal installing, C++Builder must add in units RichView.hpp and other HPP files, not RichView.H.
Usually this problem occurs when paths to TRichView are not added to C++Builder include path.
Menu Tools | Environment Options, tab Library, add path to TRichView files (where dcu, obj and hpp files are located) in "Library path".
In addition, it may be necessary to add this path in the project options:
menu Project | Options, tab Directories/Conditionals, add the path to trichview units both in "Include path" and "Library path".
After that, units must be generated correctly (with links to HPP instead of H), and projects can be compiled.