On 20/05/13 14:17, Alexander Neundorf wrote:
Hmm, wrong branch ?
I checked out "stable" branch, as the wiki page recommended from May 12th to
May 20th, because "init-repository script is broken in the dev branch".
I don't want to mess up my qt clone again.
So, do I simply do "git checkout dev",
On Monday 20 May 2013 15:17:49 Alexander Neundorf wrote:
> So, do I simply do "git checkout dev", and that's it, also for all
> submodules ?
No.
git checkout dev in qt5.git
and then
git submodule update
qt5.git defines which sha1 of the submodules you should get.
"dev" everywhere isn't recomm
On Tuesday 14 May 2013, Alexander Neundorf wrote:
> On Tuesday 14 May 2013, Stephen Kelly wrote:
> > Alexander Neundorf wrote:
> > > Additionally we don't check in cmake that the Qt which has been found
> > > is good enough.
> > > We make use of the new INTERFACE_INCLUDE_DIRECTORIES target property
On Monday, May 13, 2013 22:56:57 Oswald Buddenhagen wrote:
> however, it seems unlikely that you would get a partial build without
> any error messages because of that.
I have seen then several times myself (both on my system and other people's)
and the answer is to blow away any old build dir an
David Faure wrote:
> So, if code uses qtx11extras, cmake should warn if qtx11extras is not
> found. Same for all other submodules.
It should do already. It's found with find_package(... REQUIRED).
I don't know why it's failing for Alex. Perhaps he has an old build of it
around.
Just for comp
On Tuesday 14 May 2013 17:55:42 Alexander Neundorf wrote:
> Do you say I should adjust my expectations so that I consider build
> failures ok even if cmake succeeds ? Then this means I should not consider
> a successful cmake run as a reliable signal that my system is ready to
> build the software
Alexander Neundorf wrote:
>> From reading your emails, it looks like your existing expectations are
>> the opposite of the above, though I don't know why.
>
> There shall be no build failure due to bad includes or libs if cmake says
> everything is ok.
> That's the point of the configure step of
On Tuesday 14 May 2013, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > Additionally we don't check in cmake that the Qt which has been found is
> > good enough.
> > We make use of the new INTERFACE_INCLUDE_DIRECTORIES target property, but
> > have no checks that the Qt which has been found pr
Alexander Neundorf wrote:
>
> Additionally we don't check in cmake that the Qt which has been found is
> good enough.
> We make use of the new INTERFACE_INCLUDE_DIRECTORIES target property, but
> have no checks that the Qt which has been found provides those already.
>
> The obvious way would be
On Mon, May 13, 2013 at 09:43:56PM +0200, Alexander Neundorf wrote:
> I did:
> $ git pull
> $ git submodule update
> $ rm -rf builddir (as recommended by Ossi)
> $ mkdir build
> $ cd build
> $ ../configure -prefix $KF5 -opensource...
>
with qmake, it is never a particularly good idea to put the b
On Sunday 12 May 2013, David Faure wrote:
> On Sunday 12 May 2013 17:34:12 Alexander Neundorf wrote:
> > On Sunday 12 May 2013, David Faure wrote:
> > > On Sunday 12 May 2013 11:50:44 Alexander Neundorf wrote:
> > > > : fatal error:
> > > > QX11Info: No such file or directory
> > >
> > > You didn'
On Sunday 12 May 2013 17:34:12 Alexander Neundorf wrote:
> On Sunday 12 May 2013, David Faure wrote:
> > On Sunday 12 May 2013 11:50:44 Alexander Neundorf wrote:
> > > : fatal error:
> > > QX11Info: No such file or directory
> >
> > You didn't compile the Qt module qx11extras?
> >
> > It's part o
On Sunday 12 May 2013, David Faure wrote:
> On Sunday 12 May 2013 11:50:44 Alexander Neundorf wrote:
> > : fatal error:
> > QX11Info: No such file or directory
>
> You didn't compile the Qt module qx11extras?
>
> It's part of qt5.git branch dev, which is what the wiki recommends using.
I think I
On Sunday 12 May 2013 11:50:44 Alexander Neundorf wrote:
> : fatal error:
>
> QX11Info: No such file or directory
You didn't compile the Qt module qx11extras?
It's part of qt5.git branch dev, which is what the wiki recommends using.
--
David Faure, fa...@kde.org, http://www.davidfaure.fr
Work
On Tuesday 07 May 2013, Sebastian Kügler wrote:
> On Sunday, May 05, 2013 11:25:32 Oswald Buddenhagen wrote:
> > On Sun, May 05, 2013 at 09:32:49AM +0200, Kevin Ottens wrote:
> > > On Saturday 04 May 2013 22:16:51 Alexander Neundorf wrote:
> > > > On Saturday 04 May 2013, Kevin Ottens wrote:
> > >
On Sunday, May 05, 2013 11:25:32 Oswald Buddenhagen wrote:
> On Sun, May 05, 2013 at 09:32:49AM +0200, Kevin Ottens wrote:
> > On Saturday 04 May 2013 22:16:51 Alexander Neundorf wrote:
> > > On Saturday 04 May 2013, Kevin Ottens wrote:
> > > > On Saturday 04 May 2013 20:59:32 Alexander Neundorf wr
On Sunday 05 May 2013, Oswald Buddenhagen wrote:
> On Sun, May 05, 2013 at 11:47:04AM +0200, Alexander Neundorf wrote:
> > Ok, so what is the right way to get Qt properly rebuilt ?
>
> mv $builddir/config.status $safeplace
> rm -rf $builddir/*
> mv $safeplace $builddir/config.status
> cd $builddir
On Sun, May 05, 2013 at 11:47:04AM +0200, Alexander Neundorf wrote:
> Ok, so what is the right way to get Qt properly rebuilt ?
>
mv $builddir/config.status $safeplace
rm -rf $builddir/*
mv $safeplace $builddir/config.status
cd $builddir
./config.status
make
works also for a top-level build, exce
On Sunday 05 May 2013, Oswald Buddenhagen wrote:
> On Sun, May 05, 2013 at 09:32:49AM +0200, Kevin Ottens wrote:
> > On Saturday 04 May 2013 22:16:51 Alexander Neundorf wrote:
> > > On Saturday 04 May 2013, Kevin Ottens wrote:
> > > > On Saturday 04 May 2013 20:59:32 Alexander Neundorf wrote:
> > >
On Sun, May 05, 2013 at 09:32:49AM +0200, Kevin Ottens wrote:
> On Saturday 04 May 2013 22:16:51 Alexander Neundorf wrote:
> > On Saturday 04 May 2013, Kevin Ottens wrote:
> > > On Saturday 04 May 2013 20:59:32 Alexander Neundorf wrote:
> > > > Do I have to run configure again, or is qmake in the m
On Saturday 04 May 2013 22:16:51 Alexander Neundorf wrote:
> On Saturday 04 May 2013, Kevin Ottens wrote:
> > On Saturday 04 May 2013 20:59:32 Alexander Neundorf wrote:
> > > On Monday 29 April 2013, Aaron J. Seigo wrote:
> > > > hi ...
> > > >
> > > > today i am unable to work on plasma-framework
On Saturday 04 May 2013, Kevin Ottens wrote:
> On Saturday 04 May 2013 20:59:32 Alexander Neundorf wrote:
> > On Monday 29 April 2013, Aaron J. Seigo wrote:
> > > hi ...
> > >
> > > today i am unable to work on plasma-frameworks. this is because i am
> > > currently unable to compile the framework
On Saturday 04 May 2013 20:59:32 Alexander Neundorf wrote:
> On Monday 29 April 2013, Aaron J. Seigo wrote:
> > hi ...
> >
> > today i am unable to work on plasma-frameworks. this is because i am
> > currently unable to compile the frameworks branch of kdelibs. in turn,
> > this is because i do no
On Monday 29 April 2013, Aaron J. Seigo wrote:
> hi ...
>
> today i am unable to work on plasma-frameworks. this is because i am
> currently unable to compile the frameworks branch of kdelibs. in turn,
> this is because i do not have a recent enough version of cmake.
>
> the cmake version require
On Tuesday 30 April 2013, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > cmake 2.8.11 is about to be released very soon, maybe two weeks or so.
> > If I followed Stephens work correctly currently we can't go back to
> > 2.8.10, right ?
>
> We use an advanced SCM system. We can go back, but t
On Tuesday 30 April 2013, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > There are no Qt include dirs in the compile command, I guess it has to do
> > with the include target properties.
> >
> > Stephen ?
>
> It's likely that your Qt is too old.
This is the job of cmake.
System introspect
On Tuesday 30 April 2013, Aaron J. Seigo wrote:
> On Tuesday, April 30, 2013 11:20:47 Stephen Kelly wrote:
> > I am clueless to understand why building cmake from git and installing it
> > into your kf5 prefix is a showstopper. Can you tell me?
>
> Time is limited.
>
> Every repository that I hav
On Tuesday, April 30, 2013 15:13:46 Frank Reininghaus wrote:
> but then using a released CMake rather than a recent git snapshot
> would not be enough to make building more convenient. We would have to
> ensure that the required CMake version is shipped by all major
> distros, because I think that
Hi,
2013/4/30 Aaron J. Seigo:
> On Tuesday, April 30, 2013 11:20:47 Stephen Kelly wrote:
>
>> I am clueless to understand why building cmake from git and installing it
>
>> into your kf5 prefix is a showstopper. Can you tell me?
>
> Time is limited.
>
> Every repository that I have to build (e.g.
On Tuesday, April 30, 2013 11:20:47 Stephen Kelly wrote:
> I am clueless to understand why building cmake from git and installing it
> into your kf5 prefix is a showstopper. Can you tell me?
Time is limited.
Every repository that I have to build (e.g. cmake) that is not the repository I
am tryi
Aaron J. Seigo wrote:
> hi ...
>
> today i am unable to work on plasma-frameworks. this is because i am
> currently unable to compile the frameworks branch of kdelibs. in turn,
> this is because i do not have a recent enough version of cmake.
>
> the cmake version required is 2.8.10.20130411. th
Alexander Neundorf wrote:
> cmake 2.8.11 is about to be released very soon, maybe two weeks or so.
> If I followed Stephens work correctly currently we can't go back to
> 2.8.10, right ?
We use an advanced SCM system. We can go back, but there's no justification
to do so.
Thanks,
Steve.
Alexander Neundorf wrote:
> There are no Qt include dirs in the compile command, I guess it has to do
> with the include target properties.
>
> Stephen ?
It's likely that your Qt is too old. Ensure that your qtbase is at
ec37cdbc8016042afcd3a77cebe4b3e6b8238092 or later.
Thanks,
Steve.
On Monday 29 April 2013 22:00:15 Aaron J. Seigo wrote:
> it's not enough to just have hackers writing code.
We have a lot more than that.
build.kde.org shows that kdelibs-frameworks builds and all tests are green.
That's a lot more stable than "hackers writing code [and not caring about what
h
On Monday 29 April 2013, Kevin Ottens wrote:
> On Monday 29 April 2013 21:46:14 Alexander Neundorf wrote:
> > On Monday 29 April 2013, Aaron J. Seigo wrote:
> > > hi ...
> > >
> > > today i am unable to work on plasma-frameworks. this is because i am
> > > currently unable to compile the framework
On Monday, April 29, 2013 18:22:56 Kevin Ottens wrote:
> Well it's been necessary at some point because you needed to make fast paced
> changes.
i hear that frameworks is moving slowly. (because not enough people aren't
working on it)
now i hear that "fast paced changes" are necessary. (because
On Monday 29 April 2013 21:46:14 Alexander Neundorf wrote:
> On Monday 29 April 2013, Aaron J. Seigo wrote:
> > hi ...
> >
> > today i am unable to work on plasma-frameworks. this is because i am
> > currently unable to compile the frameworks branch of kdelibs. in turn,
> > this is because i do no
On Monday 29 April 2013, Aaron J. Seigo wrote:
> hi ...
>
> today i am unable to work on plasma-frameworks. this is because i am
> currently unable to compile the frameworks branch of kdelibs. in turn,
> this is because i do not have a recent enough version of cmake.
>
> the cmake version require
On Monday 29 April 2013, Mirko Boehm wrote:
> On Apr 29, 2013, at 18:13 , Alexander Neundorf wrote:
> > I am all for requiring only released versions of cmake.
> > Or at least announcing it when an update is required.
> > But it seemed to be the majority opinion that this is not necessary in
> > k
On Monday 29 April 2013, Kevin Ottens wrote:
> On Monday 29 April 2013 18:13:59 Alexander Neundorf wrote:
> > On Monday 29 April 2013, Aaron J. Seigo wrote:
> > > hi ...
> > >
> > > today i am unable to work on plasma-frameworks. this is because i am
> > > currently unable to compile the framework
On Monday 29 April 2013 18:13:59 Alexander Neundorf wrote:
> On Monday 29 April 2013, Aaron J. Seigo wrote:
> > hi ...
> >
> > today i am unable to work on plasma-frameworks. this is because i am
> > currently unable to compile the frameworks branch of kdelibs. in turn,
> > this is because i do no
On Monday, April 29, 2013 18:15:28 Mirko Boehm wrote:
> On Apr 29, 2013, at 18:13 , Alexander Neundorf wrote:
> > I am all for requiring only released versions of cmake.
> > Or at least announcing it when an update is required.
> > But it seemed to be the majority opinion that this is not necessar
On Apr 29, 2013, at 18:13 , Alexander Neundorf wrote:
> I am all for requiring only released versions of cmake.
> Or at least announcing it when an update is required.
> But it seemed to be the majority opinion that this is not necessary in kf5.
Majority by what definition? :-)
Mirko.
--
Mirk
On Monday 29 April 2013, Aaron J. Seigo wrote:
> hi ...
>
> today i am unable to work on plasma-frameworks. this is because i am
> currently unable to compile the frameworks branch of kdelibs. in turn,
> this is because i do not have a recent enough version of cmake.
>
> the cmake version require
44 matches
Mail list logo
