Experimental Physics and Industrial Control System

Hi Mark,

The branch is called "release/4.6.0" although your clone specifying --branch 4.6.0 should have checked out the tagged version if I had created and pushed the tag by the time you tried that (I'm not sure exactly what time this afternoon that happened though).  The tar and zip files are now available for download from the SourceForge downloads area, although we haven't sent out a notice about the release yet. I do expect to create a patch release with some known Windows build issues fixed in the exampleCPP module when I have time to work on them.

The V4 build system is not the same as the regular Base one at the top level and may never support the -j flag on its distclean target. This is related to the fact that you don't have to create your own RELEASE files for building V4, the top-level Makefile does that for you and the distclean target removes the created files again.

- Andrew

-- 
Sent from my iPad

> On Sep 18, 2016, at 3:58 PM, Mark Rivers <[email protected]> wrote:
> 
> I tried giving the branch in the git clone command:
> 
> git clone --recursive --branch 4.6.0 [email protected]:epics-base/bundleCPP.git
> 
> That did not work, I still get an older version of pvDataCPP that gives the errors on mingw about inline function.
> 
> I then did "git checkout master" in pvDataCPP.  That worked better but it eventually failed with this error:
> 
> ./../testApp/pv/testPVType.cpp:63:44: warning: too many arguments for format
> testEvent.o:testEvent.cpp:(.text+0xf): undefined reference to `__imp___ZN16MutexInitializerD1Ev'
> testEvent.o:testEvent.cpp:(.text+0x8d): undefined reference to `__imp___ZN5epics6pvData5EventC1Eb'
> testEvent.o:testEvent.cpp:(.text+0xa2): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0xce): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0xfa): undefined reference to `__imp___ZN5epics6pvData5Event6signalEv'
> testEvent.o:testEvent.cpp:(.text+0x107): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0x130): undefined reference to `__imp___ZN5epics6pvData5Event6signalEv'
> testEvent.o:testEvent.cpp:(.text+0x13d): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0x166): undefined reference to `__imp___ZN5epics6pvData5Event6signalEv'
> testEvent.o:testEvent.cpp:(.text+0x173): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0x19c): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0x1c8): undefined reference to `__imp___ZN5epics6pvData5Event6signalEv'
> testEvent.o:testEvent.cpp:(.text+0x1d5): undefined reference to `__imp___ZN5epics6pvData5Event6signalEv'
> testEvent.o:testEvent.cpp:(.text+0x1e2): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0x20b): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0x237): undefined reference to `__imp___ZN5epics6pvData5Event7tryWaitEv'
> testEvent.o:testEvent.cpp:(.text+0x26b): undefined reference to `__imp___ZN5epics6pvData5EventD1Ev'
> testEvent.o:testEvent.cpp:(.text+0x2a4): undefined reference to `__imp___ZN5epics6pvData5EventD1Ev'
> testEvent.o:testEvent.cpp:(.text+0x2cf): undefined reference to `__imp___ZN16MutexInitializerC1Ev'
> collect2: ld returned 1 exit status
> make[3]: *** [testEvent.exe] Error 1
> make[3]: *** Waiting for unfinished jobs....
> make[3]: *** wait: No child processes.  Stop.
> make[2]: *** [install.win32-x86-mingw] Error 2
> make[2]: *** Waiting for unfinished jobs....
> mkdir ../../bin/vxWorks-ppc32
> make[1]: *** [testApp.install] Error 2
> make: *** [build.pvDataCPP] Error 2
> 
> 
> There may also be a problem with distclean and parallel make:
> 
> corvette:epics/epicsV4/bundleCPP>make -sj distclean
> EPICS/Release.pm: Undefined macro $(EPICS_BASE) used
> EPICS/Release.pm: Undefined macro $(EPICS_BASE) used
> EPICS/Release.pm: Undefined macro $(EPICS_BASE) used
> EPICS/Release.pm: Undefined macro $(EPICS_BASE) used
> 
> Thanks,
> Mark
> 
> ________________________________________
> From: Mark Rivers
> Sent: Sunday, September 18, 2016 1:57 PM
> To: Johnson, Andrew N.
> Cc: EPICS core-talk
> Subject: RE: Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP
> 
> Hi Andrew,
> 
> I did the following:
> 
> git clone --recursive [email protected]:epics-base/bundleCPP.git
> cd bundleCPP/
> git checkout 4.6.0
> 
> However, "git checkout 4.6.0" did not seem to do anything in the submodules.  When I go to a submodule like pvData I see the following:
> 
> corvette:epicsV4/bundleCPP/pvDataCPP>git status
> # Not currently on any branch.
> nothing to commit (working directory clean)
> corvette:epicsV4/bundleCPP/pvDataCPP>git tag
> 1.0-BETA
> 1.0.1-BETA
> 1.1-BETA
> 1.1-SNAPSHOT
> 2.0-BETA
> 3.0-pre1
> 3.0.0
> 3.0.1
> 3.0.2
> 3.1.0
> 4.0.0
> 4.0.1
> 4.0.2
> 4.0.3
> 5.0.0
> 5.0.1
> 5.0.2
> 5.0.3
> 5.0.4
> 6.0.0
> 6.0.1
> before_merge_changesAfter3_0_2
> marchtest
> test1
> 
> How do I know that this is really version of pvData that corresponds to 4.6.0?
> 
> Thanks,
> Mark
> 
> ________________________________________
> From: Johnson, Andrew N. [[email protected]]
> Sent: Sunday, September 18, 2016 12:41 PM
> To: Mark Rivers
> Cc: EPICS core-talk
> Subject: Re: Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP
> 
> Hi Mark,
> 
>> On Sep 8, 2016, at 10:28 AM, Mark Rivers <[email protected]> wrote:
>> 
>> I get the following errors when running  "make -sj clean" on windows-x64 in top-level of pvPackageCPP
> 
> My pvPackageCPP module has been superseded by the bundleCPP module at [email protected]:epics-base/bundleCPP.git which handles parallel builds much better, but is really designed for creating the full C++ release. The release/4.6.0 branch of that module now points to the V4 modules as at the 4.6.0 release which is being made today. The master branch of that module does *not* have the latest versions of the submodules, so make sure you use the right branch.
> 
>> I would also really like to be able to do “make realclean” and “make realuninstall” in that top-level directory, but that is not supported.
> 
> The bundleCPP module does support ‘make distclean’ although I’m not too sure about doing that in parallel.
> 
> - Andrew
> 

References:

Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP Mark Rivers

Re: Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP Johnson, Andrew N.

RE: Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP Mark Rivers

RE: Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP Mark Rivers

Navigate by Date:

Prev: RE: Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP Mark Rivers

Next: Re: Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP Johnson, Andrew N.

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: Re: Errors when running "make -sj clean" on windows-x64 in top-level of pvPackageCPP Johnson, Andrew N.

Next: Build problem in pvData with VS 2015 Mark Rivers

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  <2016>  2017  2018  2019  2020  2021  2022  2023  2024