| |
Building EOCP
This page describes methods to use when building the EOCP on your system.
Please pay attention to the kind of build you want to do, which
should be based on the deployment strategy you have. If you will be deploying
on the same platform (i.e., operating system and processor type),
or unmatched platforms, the process may require more or less effort.
Matching platforms for build and deploy
This section describes what you have to do to build the EOCP for use
in matching build and deploy patforms. That is, this assumes you will
be building on the same machine (or the same OS and processor type) as
that which you will be deploying your final executables.
- Get the latest version of the
EOCP/src from CVS.
- Download, build, and install STLPort-5.0.0.
Make sure you set your paths correctly. Close out all
Visual Studios before continuing, if you are using the VC platform to
build.
Now that you have the necessary prerequisites, you are ready to run the
build.
Visual Studio 6.0, sp5
Load the EOCP/src/OCP/OCP.dsw file in Visual Studio and
build either Release_CXX Or Debug_CXX profiles
after setting the OCP to be your Active Project.
Visual Studio .Net (7.1)
TBD.
Crosscompiling (nonmatching platforms for build and deploy)
This section describes what you have to do in order to build the EOCP
for use in a crosscompile toolchain scenario. This assumes you will be
using a different deployment platform from your build platform. As of
this time, we (anticipate to) support building this crosscompiled version
ONLY using the cygwin or *nix BASH interface.
- Build and install the crosscompiler toolchain.
- Download, build, and install STLPort-5.0.0
for your crosscompiler.
- After setting the paths for your compiler, you need to crosscompile
the EOCP for your target platform. This is our current stage of support
development...
Mods to EOCP to enable embedded build types
This section describes changes made to the OCP to turn it into "EOCP",
which is what we are calling the Embedded OCP.
- Created new environment variable
OCP_HOME=$OCP_ROOT/../..
- Changed some dependencies on Substitutes (with various
../../..
paths)
to belong to $(OCP_HOME)/src/vendors/<various>
- Modified all .dsp files which used relative paths to the
tao_idl compiler
to use the path $(OCP_HOME)\_Libfiles\tao_idl
- Defined
PROJ_ROOT="." to satisfy massive dependencies
which will be changed anyway...I don't think this PROJ_ROOT is a useful
name
in any case.
- Removed all includes of "substitute" definitions (e.g.,
STL fake-outs) and replaced with appropriate
<vector>, <map>
etc. implementations...
- added '
bool.h' and 'css_version.h' to the include path
- Modified
operator== to have trailing method signature
const for struct USRsharedStateStruct (required
for compilation with new STL implementations)
- Added
,$(OCP_ROOT)/../vendors/XASTRO,$(OCP_ROOT)/../vendors
as include paths for (most) projects in the OCP VC Workspace.
|
