Well, I'm right now setting up a new, fresh, build environment for KF5
and it works.
Something must be wrong with my KDE4 build environment so forget this
issue, please, I'll research it up later :-)
Thanks cheers,
--
Valentin Rusu (IRC valir, KDE vrusu)
KSecretsService (former
On 12/03/2011 09:55 PM, Alexander Neundorf wrote:
Hmm, works here for me.
Does the same work for you ?
This is what I did:
~/src/kde-git/superbuild$ cd test
~/src/kde-git/superbuild$ mkdir test
~/src/kde-git/superbuild$ cd test/
hammer:~/src/kde-git/superbuild/test$
On 12/04/2011 11:48 AM, Alexander Neundorf wrote:
On Sunday 04 December 2011, Valentin Rusu wrote:
On 12/03/2011 09:55 PM, Alexander Neundorf wrote:
Hmm, works here for me.
Does the same work for you ?
This is what I did:
~/src/kde-git/superbuild$ cd test
~/src/kde-git/superbuild$ mkdir test
On 12/04/2011 12:41 PM, Valentin Rusu wrote:
And this is with starting from scratch with clean trees, no additional
options
Yes. I did almost the same thing as you:
cd Everything
mkdir build
cd build
cmake-gui ..
make
I have cmake compiled from sources on my system. I reset it to 2.8.6
On 12/04/2011 10:20 PM, Alexander Neundorf wrote:
On Sunday 04 December 2011, Valentin Rusu wrote:
On 12/04/2011 12:41 PM, Valentin Rusu wrote:
And this is with starting from scratch with clean trees, no additional
options
Yes. I did almost the same thing as you:
cd Everything
mkdir build
cd
On 11/30/2011 08:33 AM, Andreas Pakulat wrote:
On 29.11.11 21:41:23, Alexander Neundorf wrote:
On Tuesday 29 November 2011, Valentin Rusu wrote:
On 11/29/2011 07:34 PM, Alexander Neundorf wrote:
Even so, its bad that cmake -E does not list the cmake_progress_start
command. That confuses users
On Saturday 03 December 2011, Valentin Rusu wrote:
On 11/30/2011 08:33 AM, Andreas Pakulat wrote:
On 29.11.11 21:41:23, Alexander Neundorf wrote:
On Tuesday 29 November 2011, Valentin Rusu wrote:
On 11/29/2011 07:34 PM, Alexander Neundorf wrote:
Even so, its bad that cmake -E does not
On Tuesday 29 November 2011, Valentin Rusu wrote:
Hi Alex,
On 11/28/2011 08:57 PM, Alexander Neundorf wrote:
Probably a make VERBOSE=1 already shows enough information. Can you
please post the output here ? Alex
Here is the output:
[valentin@zhost build]$ make VERBOSE=1
On 11/29/2011 07:34 PM, Alexander Neundorf wrote:
It's the --trace in the command. I don't know how you got that in
there.
Oh, sorry, my fault! I forgot I manually edited the Makefile to add
--trace to cmake command.
If you copy that command just to the command line
(/usr/local/bin/cmake
On Tuesday 29 November 2011, Valentin Rusu wrote:
On 11/29/2011 07:34 PM, Alexander Neundorf wrote:
It's the --trace in the command. I don't know how you got that in
there.
Oh, sorry, my fault! I forgot I manually edited the Makefile to add
--trace to cmake command.
If you copy that
On 29.11.11 21:41:23, Alexander Neundorf wrote:
On Tuesday 29 November 2011, Valentin Rusu wrote:
On 11/29/2011 07:34 PM, Alexander Neundorf wrote:
It's the --trace in the command. I don't know how you got that in
there.
Oh, sorry, my fault! I forgot I manually edited the Makefile to
On Sunday 27 November 2011, Andreas Pakulat wrote:
On 27.11.11 19:00:31, Valentin Rusu wrote:
Hello,
Trying to build using latest git cmake and superbuild, I get the
message I paste below. Any clues?
-- Build files have been written to:
/home/kde/src/superbuild/kdesupport/build
Hello,
Trying to build using latest git cmake and superbuild, I get the message
I paste below. Any clues?
-- Build files have been written to:
/home/kde/src/superbuild/kdesupport/build
Scanning dependencies of target AlwaysCheckDESTDIR
DESTDIR Ok. (now: , at CMake time: )
[ 0%] Built
On 27.11.11 19:00:31, Valentin Rusu wrote:
Hello,
Trying to build using latest git cmake and superbuild, I get the
message I paste below. Any clues?
-- Build files have been written to:
/home/kde/src/superbuild/kdesupport/build
Scanning dependencies of target AlwaysCheckDESTDIR
DESTDIR
14 matches
Mail list logo
