If anyone is interessted, I think I found a solution:
git submodule update --init --recursive
Instead of both lines
Best Regards
Am 27.06.2011 um 19:56 schrieb NoRulez :
> Hi,
>
>
>
> currently I use the following to update git submodules during the ctest:
>
>
>
> if (EXISTS "${CTE
Hi,
currently I use the following to update git submodules during the ctest:
if (EXISTS "${CTEST_SOURCE_DIRECTORY}/.gitmodules")
execute_process (COMMAND ${GIT_EXECUTABLE} submodule init
WORKING_DIRECTORY ${CTEST_SOURCE_DIRECTORY})
# Update
Hi David,
with 2.8.3 the submodule update works. Thx.
On Wednesday 12 January 2011 18:43:41 you wrote:
> Are you using CMake 2.8.3? If not, you should upgrade. There were some
> improvements made w.r.t. ctest_update and git repos in that release. I
> think the submodule update was one of them...
On 1/12/2011 12:43 PM, David Cole wrote:
> Are you using CMake 2.8.3? If not, you should upgrade. There were some
> improvements made w.r.t. ctest_update and git repos in that release. I
> think the submodule update was one of them...
Among the improvements was the submodule update command:
htt
On Wed, Jan 12, 2011 at 12:16 PM, Gerhard Gappmeier
wrote:
> Hi,
>
> my project is stored in a git repo with submodules.
>
> I'm wondering if ctest is updating also the submodules when running
>
> ctest Nightly|Continuous etc.
>
> or just the main repo.
>
> I believe not, unless I have some other
Are you using CMake 2.8.3? If not, you should upgrade. There were some
improvements made w.r.t. ctest_update and git repos in that release. I think
the submodule update was one of them...
HTH,
David
On Wed, Jan 12, 2011 at 12:16 PM, Gerhard Gappmeier <
gerhard.gappme...@ascolab.com> wrote:
>
Are you using CMake 2.8.3? If not, you should upgrade. There were some
improvements made w.r.t. ctest_update and git repos in that release. I think
the submodule update was one of them...
HTH,
David
On Wed, Jan 12, 2011 at 12:16 PM, Gerhard Gappmeier <
gerhard.gappme...@ascolab.com> wrote:
>
Hi,
my project is stored in a git repo with submodules.
I'm wondering if ctest is updating also the submodules when running
ctest Nightly|Continuous etc.
or just the main repo.
I believe not, unless I have some other problems with my test script.
I could do a manual "git pull && git submodule in
Sorry for the lame suggestion, then... I have not yet used git personally,
so I'm not up to speed on git command lines.
On 3/5/08, Brad King <[EMAIL PROTECTED]> wrote:
>
> David Cole wrote:
> > With this declarative style script, the inner ctest run via
> > CTEST_COMMAND will use the CVSCOMMAND c
Brad King wrote:
David Cole wrote:
With this declarative style script, the inner ctest run via
CTEST_COMMAND will use the CVSCOMMAND cache entry... CTEST_CVS_COMMAND
is used when you use the CTEST_UPDATE() command within a command-based
script (as opposed to a declarative script). Try adding:
C
David Cole wrote:
> With this declarative style script, the inner ctest run via
> CTEST_COMMAND will use the CVSCOMMAND cache entry... CTEST_CVS_COMMAND
> is used when you use the CTEST_UPDATE() command within a command-based
> script (as opposed to a declarative script). Try adding:
>
> CVSCOMMAN
With this declarative style script, the inner ctest run via CTEST_COMMAND
will use the CVSCOMMAND cache entry... CTEST_CVS_COMMAND is used when you
use the CTEST_UPDATE() command within a command-based script (as opposed to
a declarative script). Try adding:
CVSCOMMAND:STRING=/usr/bin/git-clone
t
Hi,
has someone CTest running with git? I can clone the repository, but it always
tries to use cvs to update. See attached config file.
-- andreas
--
http://www.cynapses.org/ - cybernetic synapses
set(CTEST_SOURCE_DIRECTORY "/tmp/testing/csync/nightly/source/")
set(CTEST_BINARY_DIRE
13 matches
Mail list logo
