Subject: |
Re: Still can not successful compile/run epicsV4CPP from github |
From: |
Marty Kraimer <[email protected]> |
To: |
[email protected] |
Date: |
Wed, 23 Aug 2017 13:23:28 -0400 |
On 08/23/2017 12:09 PM, Heinz P. Junkes wrote:
There are still some issues to compile/run the V4 stuff. Even on linux
only
Attached you can find my used script.
There seems to be introduced a new directory structure (.../pv/...)
but this leads to issues like this:
../../include/compiler/gcc -I../../include/os/Linux
-I../../include -I/home/etest/EPICS/pvDataCPP/include
-I/home/etest/EPICS/pvCommonCPP/include
-I/home/etest/EPICS/epics-base/include/compiler/gcc
-I/home/etest/EPICS/epics-base/include/os/Linux
-I/home/etest/EPICS/epics-base/include -c
../../testApp/utils/testAtomicBoolean.cpp
In file included from ../../testApp/utils/testAtomicBoolean.cpp:4:0:
../../src/remote/pv/remote.h:32:29: fatal error: pv/pvaConstants.h: No
such file or directory
#include <pv/pvaConstants.h>
^
compilation terminated.
make[2]: *** [testAtomicBoolean.o] Error
Heinz
#!/bin/bash
# Dependencies between modules, also used for RELEASE files
# pvDataCPP_DEPENDS_ON = pvCommonCPP
#normativeTypesCPP_DEPENDS_ON = pvDataCPP
# pvAccessCPP_DEPENDS_ON = pvDataCPP
# pvaClientCPP_DEPENDS_ON = pvAccessCPP normativeTypesCPP
# pvaSrv_DEPENDS_ON = pvAccessCPP
# pvDatabaseCPP_DEPENDS_ON = pvAccessCPP
# exampleCPP_DEPENDS_ON = pvDatabaseCPP pvaSrv pvaClientCPP
cat << EOF > RELEASE.local
PVACCESS=$PWD/pvAccessCPP
NORMATIVETYPES=$PWD/normativeTypesCPP
PVDATA=$PWD/pvDataCPP
PVDATABASE=$PWD/pvDatabaseCPP
PVCOMMON=$PWD/pvCommonCPP
PVACLIENT=$PWD/pvaClientCPP
PVASRV=$PWD/pvaSrv
EPICS_BASE=$PWD/epics-base
TEMPLATE_TOP=$PWD/epics-base/templates/makeBaseApp/top
EOF
My RELEASE.local is:
mrk> cat RELEASE.local
EPICS4_DIR=/home/epicsv4/masterCPP
EXAMPLE=${EPICS4_DIR}/exampleCPP
PVDATABASE=${EPICS4_DIR}/pvDatabaseCPP
PVACLIENT=${EPICS4_DIR}/pvaClientCPP
PVASRV=${EPICS4_DIR}/pvaSrv
PVACCESS=${EPICS4_DIR}/pvAccessCPP
NORMATIVETYPES=${EPICS4_DIR}/normativeTypesCPP
PVDATA=${EPICS4_DIR}/pvDataCPP
#PVCOMMON=${EPICS4_DIR}/pvCommonCPP
#EPICS_BASE=/home/install/epics/base-3.14.12.5
#EPICS_BASE=/home/install/epics/base-3.15.5
EPICS_BASE=/home/install/epics/base-3.16.1
#EPICS_BASE=/home/install/epics/base
Thus all in reverse of dependencies.
My build is successful.
I am not sure what this means.
Marty
repos=(
"https://github.com/epics-base/epics-base.git"
"https://github.com/epics-base/pvCommonCPP.git"
"https://github.com/epics-base/pvDataCPP.git"
"https://github.com/epics-base/normativeTypesCPP.git"
"https://github.com/epics-base/pvAccessCPP.git"
"https://github.com/epics-base/pvaClientCPP.git"
"https://github.com/epics-base/pvaSrv.git"
"https://github.com/epics-base/pvDatabaseCPP.git"
"https://github.com/epics-base/exampleCPP.git"
)
echo "Cloning " ${#repos[@]} "repositories"
for repo in "${repos[@]}"
do
localRepoDir=$(echo ${repo}| cut -d'/' -f5 | cut -d'.' -f1)
if [ -d $localRepoDir ]; then
echo "Directory " $localRepoDir " already exists"
cd $localRepoDir
echo "will pull"
git pull
make runtests
cd ..
else
echo "clone" ${repo}
git clone ${repo}
cd $localRepoDir
make runtests
cd ..
fi
done
- Replies:
- Re: Still can not successful compile/run epicsV4CPP from github Michael Davidsaver
- References:
- Still can not successful compile/run epicsV4CPP from github Heinz P. Junkes
- Navigate by Date:
- Prev:
Still can not successful compile/run epicsV4CPP from github Heinz P. Junkes
- Next:
Re: Still can not successful compile/run epicsV4CPP from github Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Still can not successful compile/run epicsV4CPP from github Heinz P. Junkes
- Next:
Re: Still can not successful compile/run epicsV4CPP from github Michael Davidsaver
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
<2017>
2018
2019
2020
2021
2022
2023
2024
|