On Apr 22, 6:48 pm, Cactus <rieman...@googlemail.com> wrote:
> On Apr 22, 6:29 pm, Jeff Gilchrist <jeff.gilchr...@gmail.com> wrote:
>
>
>
> > On Wed, Apr 22, 2009 at 1:22 PM, Cactus <rieman...@googlemail.com> wrote:
> > > To overcoem this problem I hence had to drop all the test project
> > > dependencies and this means that it is no longer possible to build
> > > them all at once.
>
> > Ah ok.
>
> > > The way I now do this is to build the test library first and then
> > > select all the rest and issue a build command. This is not ideal but
> > > it is hopeless debugging when all the test projects all rebuild even
> > > when only one is needed :-(
>
> > Is there a way to select all the rest without having to individually
> > select build for each of the 146 project files? The IDE won't let me
> > select more than 1 project int he Solution Explorer so I had to go
> > into the Configuration manager and click on the "Build" box beside
> > each one. If there is an easier way please let me know.
>
> That very odd.
>
> All I do after building the test library is to select the 'constants'
> project, scroll down to the subc project and do SHIFT select on it.
> This selects all the projects after which I can then right click and
> select build or rebuild (I do have to ensure that none of the projects
> are expanded to avoid selecting C files at the same time).
>
> > > It might be possible to have two configurations - one that builds all
> > > of them and one that builds each one alone - I'll look into this.
>
> > That would be useful too for people who are building MPIR then want to
> > run the tests to ensure everything is ok. Maybe have a new project
> > called "build-all-tests" and have it depend on all the other projects
> > in the library so it builds everything?
>
> Yes. Or setting the debug configuration to build one and the releae
> configuration to build all of them.
I have added the missing test in the trunk and the 1.1 branch in
SVN.
I have also changed the build configuration for the Windows tests to
build all the tests when in release mode.
I have done these changes in trunk and in 1.1 since they don't
directly impact on the integrity of the MPIR build itself.
Brian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"mpir-devel" group.
To post to this group, send email to mpir-devel@googlegroups.com
To unsubscribe from this group, send email to
mpir-devel+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/mpir-devel?hl=en
-~----------~----~----~----~------~----~------~--~---
