Orpheus is a large collection of visual and non-visual components for Delphi and Borland C++. Orpheus is available for download from SourceForge.net
This installation was done on XP Pro for Borland Builder 6 (Ent). These notes should apply to any Windows OS and any version of BCB. Your milage may vary!
Following the instructions in the ReadMe.txt file, the user will encounter the error "Project Rule Not Found" and the loading of the file will abort. SourceForge.net has some instructions to fix this error. I have included portions of these instructions along with my comments. Note: These instructions are composed of two different threads in SourceForge's Help forum for this product. My comments will be in blue.
Following are detailed instructions for building the packages in BCB6.
Notes:
- We only tested the open source product with Delphi 5, 6, and 7.
- The package files expect the source code files to be in the same directory. In the SourceForge release, they are not. The easiest way to fix the problem is to move the package files into the source file directory before building them.
Open and compile (install) the following packages in the following order...
Before doing the following steps, you will need to comment out the license block in each package. You will have to do this in another editor since BCB won't load the files.
Bracket the license commentary lines at the top of each 0406*61.bpk file with XML comment notation "<!-- comments -->" as shown below
<!--
# * ***** BEGIN LICENSE BLOCK *****
...
# * ***** END LICENSE BLOCK *****
-->
[tab]1. Open and compile O406_R61.BPK.
I ran into an error complaining about allor.dcu not being found. The problem is that allor.pas is being called form the packages directory. It should be called from the source directory. I had to remove the allor.pas and add it with the correct direcotry.
[tab]2. Open, compile and install O406_D61.BPK package.
I had the same problem was above with allordesign.pas. The fix was the same as above.
[tab]3. Open and compile O406BR61.BPK.
The same problem with allopb.pas.
[tab]4. Open, compile and install O406BD61.BPK
This package has a couple of problems.
[tab][tab]A. I had to change all references to O405* to O406* in the BPK file. You can do this either in your favorite editor or open the package and then do Project|Edit Open Source.
[tab][tab]B. I had the same problem with invalid paths as above for the following files: OvcDBAe0.pas, OvcDBAe1.pas, OvcDBAe2.pas, OvcDBAe3.pas, OvcDBHdb.pas, OvcDBTb0.pas, OvcDBTb1.pas, OvcRegBD.pas, and OvcRegDB.pas.
IMPORTANT NOTES FOR C++BUILDER USERS:
[tab]If you are using Orpheus with different versions of C++Builder, the header files for C++Builder 3, C++Builder 4, and C++Builder 5 are not compatible and so they must be stored in separate directories. Under your Orpheus directory, you will need to create a separate directory called hpp6, (where the * stands for your BCB version.). By default, the compiler creates the new header files in the same directory where the source code files are. After you are finished building the packages, you should *MOVE* the newly generated header files into the appropriate *.hpp directory.
With Regards,
Phillip H. Blanton
Senior Software Engineer
TurboPower Software Company
********************************************************
I have not yet tested the components.
James P. Cottingham
When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity.
[tab][tab]Albert Einstein explaining his Theory of Relativity to a group of journalists.
This installation was done on XP Pro for Borland Builder 6 (Ent). These notes should apply to any Windows OS and any version of BCB. Your milage may vary!
Following the instructions in the ReadMe.txt file, the user will encounter the error "Project Rule Not Found" and the loading of the file will abort. SourceForge.net has some instructions to fix this error. I have included portions of these instructions along with my comments. Note: These instructions are composed of two different threads in SourceForge's Help forum for this product. My comments will be in blue.
Following are detailed instructions for building the packages in BCB6.
Notes:
- We only tested the open source product with Delphi 5, 6, and 7.
- The package files expect the source code files to be in the same directory. In the SourceForge release, they are not. The easiest way to fix the problem is to move the package files into the source file directory before building them.
Open and compile (install) the following packages in the following order...
Before doing the following steps, you will need to comment out the license block in each package. You will have to do this in another editor since BCB won't load the files.
Bracket the license commentary lines at the top of each 0406*61.bpk file with XML comment notation "<!-- comments -->" as shown below
<!--
# * ***** BEGIN LICENSE BLOCK *****
...
# * ***** END LICENSE BLOCK *****
-->
[tab]1. Open and compile O406_R61.BPK.
I ran into an error complaining about allor.dcu not being found. The problem is that allor.pas is being called form the packages directory. It should be called from the source directory. I had to remove the allor.pas and add it with the correct direcotry.
[tab]2. Open, compile and install O406_D61.BPK package.
I had the same problem was above with allordesign.pas. The fix was the same as above.
[tab]3. Open and compile O406BR61.BPK.
The same problem with allopb.pas.
[tab]4. Open, compile and install O406BD61.BPK
This package has a couple of problems.
[tab][tab]A. I had to change all references to O405* to O406* in the BPK file. You can do this either in your favorite editor or open the package and then do Project|Edit Open Source.
[tab][tab]B. I had the same problem with invalid paths as above for the following files: OvcDBAe0.pas, OvcDBAe1.pas, OvcDBAe2.pas, OvcDBAe3.pas, OvcDBHdb.pas, OvcDBTb0.pas, OvcDBTb1.pas, OvcRegBD.pas, and OvcRegDB.pas.
IMPORTANT NOTES FOR C++BUILDER USERS:
[tab]If you are using Orpheus with different versions of C++Builder, the header files for C++Builder 3, C++Builder 4, and C++Builder 5 are not compatible and so they must be stored in separate directories. Under your Orpheus directory, you will need to create a separate directory called hpp6, (where the * stands for your BCB version.). By default, the compiler creates the new header files in the same directory where the source code files are. After you are finished building the packages, you should *MOVE* the newly generated header files into the appropriate *.hpp directory.
With Regards,
Phillip H. Blanton
Senior Software Engineer
TurboPower Software Company
********************************************************
I have not yet tested the components.
James P. Cottingham
When a man sits with a pretty girl for an hour, it seems like a minute. But let him sit on a hot stove for a minute and it's longer than any hour. That's relativity.
[tab][tab]Albert Einstein explaining his Theory of Relativity to a group of journalists.