Installed tests

[Andreas Pakulat]

On 19.06.07 22:36:44, Alexander Neundorf wrote:
> On Tuesday 19 June 2007 19:39, Andreas Pakulat wrote:
> > On 19.06.07 19:08:20, Alexander Neundorf wrote:
> ...
> > > add_executable(foo EXCLUDE_FROM_ALL main.cpp)
> > > install(TARGETS foo DESTINATION bin)
> > >
> > > where the install failed if foo wasn't built, right ?
> >
> > Not really, the problem was that make started to build foo, but foo
> > needed a .ui file to be processed which didn't happen because foo wasn't
> > built explicitly.
> 
> "make foo" should do everything required for building foo. If it doesn't then 
> there is some problem.

make foo does work, but make install in the same dir doesn't. make
install also tries to build foo, but fails because the ui_*.h file is
not generated.

> > > > > But this file should not be installed in a non test environment
> > > > > because it add unnecessary entry in the knotify control module. So
> > > > > maybe we can just disable this test, and if one want to test, one
> > > > > need to install manually files
> > > >
> > > > Ok, so the original problem still exists: Installing certain files when
> > > > building a test (or installing them with make install only if the test
> > > > was built before), without having to specify -DKDE4_BUILD_TESTS. Any
> > > > ideas how/if this is possible with cmake
> > > >
> > > > I think there may be quite some other things that are of the same form
> > > > (a rc or desktop file that needs to be installed for the test to work).
> > >
> > > There should be no problem installing some desktop or rc files no matter
> > > whether a target is built or not.
> >
> > Right, except that this will give packagers a headache, they have to
> > explicitly deselect these file then.
> 
> Actually I think stuff needed only for testing shouldn't be installed. Would 
> be cool if we could find a solution for these test apps. Maybe setting 
> KDEDIRS ?

+1 from me.

Andreas

-- 
You will be surprised by a loud noise.