|
Hi All, A recent checkin which was largely focused on cross-compilation for embedded targets introduced a new convention for software "build targets", which are used in the names of directories where compilation results are placed. Normally such a change would not have much impact since all such names are recreated in a clean build in any case. The changed target names introduced an "os version" tag between "os" and "platform", where the "os version" is a high level indicator of OS major versions, like "c6" for centos 6.xxx. Also, MacOS targets now use "macos" rather than "darwin". The one place where this creates an incompatibility is in the pre-installed prerequisites, like gtest and omniorb. If an existing opencpi installation is relying on these prerequisite installations that were done by the scripts that come with opencpi, like "install_gtest.sh" and "install_omniorb.sh", you need to rerun these scripts before doing a clean build of opencpi. Thus, after a "git pull" or "git clone" to get the latest sources, you would need to: 1. Remove gtest and omniorb by doing: rm -r -f /opt/opencpi/prerequisites/{gtest,omniorb} 2. Update your environment script based on mine (jkvm6.sh). This will mean it calls two other new scripts for default behavior at the start and end. 3. Source your environment script in a fresh shell 4. If you do not have a fresh tree (new git clone), clean out all the old target directories in the opencpi tree. find . -name "target-*" -exec rm -r "{}" ";" 5. Run "make clean" 6. Install a fresh gtest library by: ./install_gtest.sh 7. Install a fresh omniorb by ./install_omniorb.sh 8. Rebuild software make; make rcc; make examples etc. We are working toward an ARM-based cross-compilation reference platform. Cheers, Jim |
_______________________________________________ opencpi_dev mailing list [email protected] http://lists.opencpi.org/listinfo.cgi/opencpi_dev-opencpi.org
