Re: [Cppqed-support] new testsuite

[Andras V. <and...@ui...>]

Hi Raimar,

Thanks for your reply, it worked. The only negative I see is that in such a
kdevelop session when the projects are imported separately, kdevelop does
not recognize them as separate git repositories. With monolithic import,
however, git does work in kdevelop. This was not like that so far when I
had only the separate repositories cloned. Can it be that kdevelop gets
confused by the git repository on a level below in the directory hierarchy?

I tried the testsuite and it ran fine both with make and ctest. I must say
I’m very impressed. The documentation is also nice, though at the moment I
do not have time to try and add new tests on the basis of it. One thing
that occured to me: how do you think we can integrate the bazaar „physical”
testsuite which relied on comparison of trajectory outputs via Sebastian’s
pycppqed?

Best regards,
András



Dr. Andras Vukics
Institute for Theoretical Physics
University of Innsbruck


On Mon, Jan 6, 2014 at 5:21 PM, Raimar Sandner <rai...@ui...>wrote:

> On Monday, January 06, 2014 09:33:54 you wrote:
> > Hi Raimar,
> > I feel that I’m close to the point where I will be able to try the
> > testsuite, just one more question beforehand. If I checkout the
> > super-repository, the different sub-repositories below it will work in
> > exactly the same way as they did, won’t they? And also, I can still use
> the
> > separate build strategy, only in one level lower in the directory
> > hierarchy, can’t I?
>
> That is correct. You can load the sub-projects as standalone-projects in
> kdevelop, you will have a separate build directory in every submodule.
> Kdevelop might ask which is the right project root because it is ambiguous,
> just choose the submodule instead of the super-repository.
>
> However, you can only run the testsuite from the super-repository project,
> obviously, and this will compile the framework again in the
> super-repository
> build directory.
>
> I will add a documentation for the testsuite soon.
>
> > I’m asking this because I wouldn’t like to keep both the separate
> projects
> > and the super-project with its subprojects on my machine, but want to
> move
> > my development to under a checked-out super-project, but work separately
> as
> > so far. This means moving all my local branches as well.
>
> Yes this will work, you could even load the super-project to kdevelop
> additionally on a as-needed basis. If you want to commit to the super-
> repository, you can just ignore the changes in the submodules (just don't
> 'git
> add' the submodules when committing). I will take care that the right
> (current) commits are registered in the super-repository on a regular
> basis.
>
> Best regards
> Raimar
>