SVN commit 577387 by coolo:
I was unable to specify inter directory dependencies in a sane
way ;(
CCMAIL: kde-buildsystem@kde.org
M +5 -0 CMakeLists.txt
--- trunk/KDE/kdepim/kontact/plugins/kmail/CMakeLists.txt #577386:577387
@@ -26,6 +26,11 @@
install(TARGETS kontact_kmailplugin
On Saturday, 26. August 2006 16:16, Stephan Kulow wrote:
> I was unable to specify inter directory dependencies in a sane
> way ;(
> CCMAIL: kde-buildsystem@kde.org
This causes a new failure for me:
make[2]: *** No rule to make target `kontact/plugins/kmail/kmail_plugin.moc',
needed by
`konta
Am Samstag, 26. August 2006 23:24 schrieb Dirk Mueller:
> On Saturday, 26. August 2006 16:16, Stephan Kulow wrote:
> > I was unable to specify inter directory dependencies in a sane
> > way ;(
> > CCMAIL: kde-buildsystem@kde.org
>
> This causes a new failure for me:
>
> make[2]: *** No rule to make
Am Samstag, 26. August 2006 16:16 schrieb Stephan Kulow:
> SVN commit 577387 by coolo:
>
> I was unable to specify inter directory dependencies in a sane
> way ;(
> CCMAIL: kde-buildsystem@kde.org
>
>
> M +5 -0 CMakeLists.txt
>
>
> --- trunk/KDE/kdepim/kon
tem@kde.org
> >
> >
> > M +5 -0 CMakeLists.txt
> >
> >
> > --- trunk/KDE/kdepim/kontact/plugins/kmail/CMakeLists.txt #577386:577387
> > @@ -26,6 +26,11 @@
> >
> > install(TARGETS kontact_kmailplugin DESTINATION ${PLUGIN_INSTALL_DIR})
> >
&g
ory dependencies in a sane
> > > way ;(
> > > CCMAIL: kde-buildsystem@kde.org
> > >
> > >
> > > M +5 -0 CMakeLists.txt
> > >
> > >
> > > --- trunk/KDE/kdepim/kontact/plugins/kmail/CMakeLists.txt
> > > #5773
Hi,
On Tuesday 29 August 2006 19:37, you wrote:
> Am Dienstag, 29. August 2006 18:48 schrieb Alexander Neundorf:
...
> The same happens if you start from toplevel with -j5 - so your suggestion
> fixes _nothing_ ;(
Does it help to add a dependency from the plugin to kmailprivate ?
add_dependencie
Am Dienstag, 29. August 2006 19:48 schrieb Alexander Neundorf:
> Hi,
>
> On Tuesday 29 August 2006 19:37, you wrote:
> > Am Dienstag, 29. August 2006 18:48 schrieb Alexander Neundorf:
>
> ...
>
> > The same happens if you start from toplevel with -j5 - so your suggestion
> > fixes _nothing_ ;(
>
>
On Tuesday 29 August 2006 20:11, you wrote:
> Am Dienstag, 29. August 2006 19:48 schrieb Alexander Neundorf:
> > Hi,
> >
> > On Tuesday 29 August 2006 19:37, you wrote:
> > > Am Dienstag, 29. August 2006 18:48 schrieb Alexander Neundorf:
> >
> > ...
> >
> > > The same happens if you start from topl
On Tuesday 29 August 2006 20:11, Stephan Kulow wrote:
> Am Dienstag, 29. August 2006 19:48 schrieb Alexander Neundorf:
> > Hi,
> >
> > On Tuesday 29 August 2006 19:37, you wrote:
> > > Am Dienstag, 29. August 2006 18:48 schrieb Alexander Neundorf:
> >
> > ...
> >
> > > The same happens if you start
Am Dienstag, 29. August 2006 20:41 schrieb Alexander Neundorf:
>
> Now that you have the dep to kmailprivate added explicitely, you can remove
> the header again from the list of sources.
So just to summarize: the only solution for "source file A needs generated
header file B" is "compile and lin
On Wednesday 30 August 2006 10:14, Stephan Kulow wrote:
> other target that come close to A"? That is pretty much not what you expect
> to happen - anyway I can't test atm, I'll commit if it works.
Since my compile dashboard stumbles over it all the time (it builds from clean
sources with -j12),
On Wednesday 30 August 2006 10:14, Stephan Kulow wrote:
> Am Dienstag, 29. August 2006 20:41 schrieb Alexander Neundorf:
> > Now that you have the dep to kmailprivate added explicitely, you can
> > remove the header again from the list of sources.
>
> So just to summarize: the only solution for "so
Am Mittwoch, 30. August 2006 18:37 schrieb Alexander Neundorf:
> Then the plugin should really only depend on the generated header(s).
That sounds more useful indeed.
Greetings, Stephan
___
Kde-buildsystem mailing list
Kde-buildsystem@kde.org
https://m
14 matches
Mail list logo
