Thank you for downloading this release of the FACC 2.1 to EDCS 4.4 Mapping Software Development Kit (SDK). This SDK is intended as a "drop-in" into the EDCS SDK.
This release has been tested on multiple platforms, such as Linux, Irix, Sun, and Windows 98/Me/NT/2000.
For help, comments, and bug reports please send email to help@sedris.org. If you are an associate, please use se-coders@sedris.org.
Return to: Top
General:
- For the Microsoft Visual C++ IDE, updated the project files for the sample applications to address a dynamic linking issue.
FACC 2.1 feature mappings:
FACC 2.1 attribute mappings:
- None.
FACC 2.1 "code list" mappings:
- Code was erroneously indicating that CHANGE_IN_DATATYPE mappings were ONE_TO_ONE.
- ENUM to Boolean mappings are now CHANGE_IN_DATATYPE.
- Cases where an attribute has different targets for different cases are now SPECIAL_CASE where they were previously ONE_TO_ONE (affects FCO).
- NST and NS2 no longer replicate the qualifier supplied by the attribute mapping for each of the attribute value mappings.
- Added notes information on a number of mappings.
Return to: Top
This SDK is meant to be installed into an EDCS SDK installation. The files in this SDK should be extracted inside the EDCS SDK top level directory. If you have a previous installation of this SDK and you don't want to overwrite it, you should rename the "facc2p1_to_edcs4px" directory to some other name.
This SDK is distributed as a GNU-zipped tar file for Unix systems and a Zip file in Win32 systems. In the discussions that follow, the "[root]" directory is the top directory of an SDK installation.
IMPORTANT:Extract the contents of the compressed file into the "[root]" directory of the EDCS SDK:
- In Unix systems: tar xvzf facc2p1_to_edcs4px_[version].tar.gz
- In Win32 systems: use WinZip or other
decompression utility to extract the contents of the downloaded file.The extraction should have created a "facc2p1_to_edcs4px" subdirectory in the "[root]" directory of the EDCS SDK if it didn't exist.
Return to: Top
This section describes the steps needed to compile, link, and test the software included in this SDK. Applications and/or libraries that use this SDK will need to refer to the EDCS SDK "[root]/include" directory for compilation, and the libraries in the EDCS SDK "[root]/lib" subdirectories for linking, since those are the places where all headers and libraries from this SDK are placed. The applications in this SDK are similarly placed in the EDCS SDK "[root]/bin" subdirectories.
IMPORTANT: The libraries produced by this SDK depend on the EDCS Mapping Utilities library having been compiled and installed before you compile this SDK.
To compile this SDK, follow these steps:
- Unix
After installing this SDK as detailed in Installation, a "make" command in the EDCS SDK "[root]" directory will recursively go through the SDK directory structure and build all libraries and applications provided with the distribution using the default settings. For this release, the default settings are:
- BUILD_MODE = OPT
- BIND_STATIC = no
- USE_GNU = false (set to true under Linux)
These settings will compile the release using optimization and dynamic linking.
- Win32
Follow these steps to build all the SDK libraries and applications:
Prior to building this SDK you must build the EDCS SDK and the EDCS Mapping Utilities SDK.
If the EDCS Mapping Utilities SDK has not yet been installed, then from Windows Explorer, locate and open (i.e., double click) the "win32_headers.bat" file in the "[root]" directory of the EDCS Mapping Utilities SDK installation. This step copies the header files of that SDK into the EDCS SDK "[root]/include" directory.
From Windows Explorer, locate and open (i.e., double click) the "win32_headers.bat" file in the "[root]" directory of this SDK installation. This step copies the header files for this SDK into the EDCS SDK "[root]/include" directory.
Open the "vcpp_static.dsw" Visual C++ (VC++) project workspace file for this SDK.
From the Visual C++ IDE, select "all_sdk" as your "Active Project" and "Release" or "Debug" for your "Active Configuration". For example, to compile in "Release" mode, choose "Build->Set Active Configuration..." and select the "all_sdk - Win32 Release" entry.
From the "Build" menu, choose "Rebuild All".
Notes:
- You can build individual applications by making them the current "Active Project" ("Project->Set Active Project" menu), and choosing "Rebuild All".
- The "Release" option is similar to the Unix Build Environment "OPT" option for the "BUILD_MODE" variable.
To run the applications included in this SDK, see Use Examples to learn about the applications, and follow the same steps as described in the EDCS SDK documentation section Testing the Build for setting your environment variables.
To build your own applications using this SDK, see the provided applications for examples on how to create appropriate Makefiles for Unix or VC++ Project files for Win32.
Return to: Top
The SDK Documentation is divided into the following areas:
- Release Notes (this document)
- Describes this release, its contents, and supported platforms and compilers.
- FACC 2.1 to EDCS 4.4 Mapping Reference Manual
- Provides links to detailed documents for SDK functions, capabilities, and applications in this SDK.
Return to: Top
Questions, comments, and bug reports should be sent to help@sedris.org.
If you are an associate, please send email to se-coders@sedris.org.
Return to: Top
These links require Internet access.
Return to: Top
Copyright © 2011 SEDRIS™