On Donnerstag, 6. Februar 2025 09:33:08 Mitteleuropäische Normalzeit David
Redondo wrote:
> Am Donnerstag, 6. Februar 2025, 06:47 schrieb Alexander Neundorf:
> > Hi,
> >
> > on Ubuntu 24.04 using gcc 14, building frameworks fails:
> > kde-builder --set-project-option-value frameworks,tag,v6.8.0
>
Am Donnerstag, 6. Februar 2025, 06:47 schrieb Alexander Neundorf:
> Hi,
>
> on Ubuntu 24.04 using gcc 14, building frameworks fails:
> kde-builder --set-project-option-value frameworks,tag,v6.8.0
> --set-project-option-value
> oxygen-icons,tag,v6.0.0 frameworks
>
> [snip compiler output]
Look
Hi,
on Ubuntu 24.04 using gcc 14, building frameworks fails:
kde-builder --set-project-option-value frameworks,tag,v6.8.0
--set-project-option-value
oxygen-icons,tag,v6.0.0 frameworks
[4/304] Compiling C object
tests/test-build-pedantic-stable_xdg_shell_xdg_shell_xml.p/
meson-generated_.._tes
pplication based largely on okular that I would like
to be able to deploy as simply as possible for users with no technical
expertise. For this purpose, and despite its well-known down-sides I thought
that a static build would be helpful.
So I started building KDE frameworks and other okular de
On Fri, Feb 22, 2019 at 11:57:42AM +0800, Jonathan Schultz wrote:
> Hello KDE developers,
>
> If anyone is interested, here is a brief report on something I have been
> working on in my spare time.
>
> TLDR: Here are some scripts to build KDE frameworks and okular statically
> using gcc/musl an
down-sides I thought
> that a static build would be helpful.
>
> So I started building KDE frameworks and other okular dependencies using
> kdesrc-build and working out what would need to change to make a static
> build. It turned out to be more painstaking but less complicate
build would be helpful.
So I started building KDE frameworks and other okular dependencies using
kdesrc-build and working out what would need to change to make a static build.
It turned out to be more painstaking but less complicated than I had imagined.
It all happens inside Docker containers
On Monday, December 10, 2018 12:34:22 PM CET Harald Sitter wrote:
> On Mon, Dec 10, 2018 at 11:26 AM Frederik Schwarzer
wrote:
> > After installing it, phonon-vlc built fine.
>
> this should be easier to diagnose in the future
> https://commits.kde.org/phonon-vlc/e441972892fe61e361ee9b2c39ce0b31
On Mon, Dec 10, 2018 at 11:26 AM Frederik Schwarzer wrote:
> After installing it, phonon-vlc built fine.
this should be easier to diagnose in the future
https://commits.kde.org/phonon-vlc/e441972892fe61e361ee9b2c39ce0b319f6d1c9e
HS
On Monday, December 10, 2018 12:29:54 AM CET Michael Pyne wrote:
> On Sun, Dec 09, 2018 at 10:18:42AM +0100, Frederik Schwarzer wrote:
> > Hi,
> >
> > please forgive my ignorance. It has been ages since I last built KDE from
> > sources.
> >
> > Using kdesrc-build, the phonon-vlc package fails on
On Sun, Dec 09, 2018 at 10:18:42AM +0100, Frederik Schwarzer wrote:
> Hi,
>
> please forgive my ignorance. It has been ages since I last built KDE from
> sources.
>
> Using kdesrc-build, the phonon-vlc package fails on cmake with the following
> error:
> -- Checking for module 'libvlc'
>
Hi,
please forgive my ignorance. It has been ages since I last built KDE from
sources.
Using kdesrc-build, the phonon-vlc package fails on cmake with the following
error:
-- Checking for module 'libvlc'
-- Found libvlc, version 3.0.4
CMake Error at cmake/FindLIBVLC.cmake:106 (mess
On Sat, Jun 09, 2018 at 10:49:26AM +0530, Bhavesh Patidar wrote:
> Hello Everyone.
> For building Elisa from kdesrc-build, I am building the dependencies from
> here:
> https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Install_the_dependencies
>
>
> But this is installing version
Hello Everyone.
For building Elisa from kdesrc-build, I am building the dependencies from
here:
https://community.kde.org/Guidelines_and_HOWTOs/Build_from_source/Install_the_dependencies
But this is installing version 5.9.5 for Qt and version 5.44 for all kde
frameworks. Elisa requires versions 5
Yes it worked. Thank You!
On Fri, Aug 4, 2017 at 4:44 PM, chinmoy ranjan
wrote:
> I think it requires bison development files. Maybe search on synaptic for
> bison-dev. This should fix your problem.
> On Aug 4, 2017 16:39, "Aman Gupta" wrote:
>
>> I am trying to build KDE LabPlot but it shows a
I think it requires bison development files. Maybe search on synaptic for
bison-dev. This should fix your problem.
On Aug 4, 2017 16:39, "Aman Gupta" wrote:
> I am trying to build KDE LabPlot but it shows an error:
>
>
>
>
>
> *CMake Error at
> /usr/share/cmake-3.5/Modules/FindPackageHandleStanda
I am trying to build KDE LabPlot but it shows an error:
*CMake Error at
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148
(message): Could NOT find BISON (missing: BISON_EXECUTABLE) Call Stack
(most recent call first):
/usr/share/cmake-3.5/Modules/FindPackageHandleStandardAr
Hi !
I am new to kde, and have been trying to build it in ubuntu 14.04.
Yesterday the building was working fine and managed to download,
install 130/226 odd files.
But today, I get these two runtime errors stating "time out". And
mostly, the 2nd error.
http://pastebin.com/d5nCtPUR
I tried us
On Sun, Apr 29, 2012 at 8:25 PM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> On Sun, 29 Apr 2012 08:07:10 PM Rohan Garg wrote:
> > Unless you're targeting developers who are going to contribute to core
> KDE
> > SC components like kdelibs, I fail to see why you would want to build KD
On Sun, 29 Apr 2012 08:07:10 PM Rohan Garg wrote:
> Unless you're targeting developers who are going to contribute to core KDE
> SC components like kdelibs, I fail to see why you would want to build KDE
> from ground up.
That's exactly who I'm targeting. Getting the KDE dev environment for casual
Hi
On Sat, Apr 28, 2012 at 9:54 AM, Анонимный Аноним wrote:
> Hmm... Is Project Neon still active? If yes, maybe somebody will edit the
> techbase page which recommends to use «maverick» repository? Or, is the
> latest repository really marked as «maverick»?
>
> http://techbase.kde.org/Getting_St
VM so people can easily build trunk
> themselves, not looking for pre build repos
>
I'm still going to advise you to use prebuilt binaries primarily because
building KDE in a VM on commodity hardware is going to be *slow* . Unless
you're targeting developers who are going to contrib
On 28/04/12 01:03, Lindsay Mathieson wrote:
2. Its a VM. I don't think 64bit VM's run very well if at all on 32 bit
installs. I'm wondering if I should cater to that with just a 32 bit VM.
That should be no problem with relatively recent CPUs.
Visit http://mail.kde.org/mailman/listinfo/kde-d
On Sat, 28 Apr 2012 02:07:03 PM Thom Castermans wrote:
> Hi Lindsay,
>
> Although I cannot answer your question, I would be interested in your
> VM if you have finished it. Is there a page where you post your
> project, or will you send an email via this list if you're done? Maybe
> it is an idea
Hi Lindsay,
Although I cannot answer your question, I would be interested in your
VM if you have finished it. Is there a page where you post your
project, or will you send an email via this list if you're done? Maybe
it is an idea to create a 32- and a 64-bit version?
Thom
2012/4/28 Lindsay Mat
, "Rohan Garg" :
> Hi Lindsay
>
> On Fri, Apr 27, 2012 at 6:57 PM, Lindsay Mathieson
> wrote: > On Fri, 27 Apr 2012 10:00:50 PM you
> wrote:
>>> Been out of the loop for a while ...
>>>
>>> Is Building KDE using kdesrc-build (http://kdesr
On Sat, 28 Apr 2012 12:18:26 AM Rohan Garg wrote:
Hi Rohan, while I appreciate the answer did you even read beyond my subject
line?
1. I'm setting up a preconfigured VM so people can easily build trunk
themselves, not looking for pre build repos
2. Its a VM. I don't think 64bit VM's run very w
Hi Lindsay
On Fri, Apr 27, 2012 at 6:57 PM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> On Fri, 27 Apr 2012 10:00:50 PM you wrote:
> > Been out of the loop for a while ...
> >
> > Is Building KDE using kdesrc-build (http://kdesrc-build.kde.org/) sti
On Fri, 27 Apr 2012 10:00:50 PM you wrote:
> Been out of the loop for a while ...
>
> Is Building KDE using kdesrc-build (http://kdesrc-build.kde.org/) still the
> best option on Kubuntu?
>
> Looking at finishing a project I started a while back - setting up a
> VirtualBo
Been out of the loop for a while ...
Is Building KDE using kdesrc-build (http://kdesrc-build.kde.org/) still the
best option on Kubuntu?
Looking at finishing a project I started a while back - setting up a
VirtualBox image preconfigured for downlaoding and building trunk. Thought I'd
On 02/17/2012 09:00 AM, Simon Kaczor wrote:
Luiz Romário Santana Rios gmail.com> writes:
Got that same problem and a simple ln -s /usr/bin/python2
$KDE_INST_DIR/bin/python solved it for me. Kind of a workaround, but I
don't see any problem, as I don't think any of KDE uses python3 yet.
I
Luiz Romário Santana Rios gmail.com> writes:
>
> Got that same problem and a simple ln -s /usr/bin/python2
> $KDE_INST_DIR/bin/python solved it for me. Kind of a workaround, but I
> don't see any problem, as I don't think any of KDE uses python3 yet.
>
> 2011/10/17 Tomaz Canabrava kde.org>:
>
On 17.10.11 16:26:42, Scott Kitterman wrote:
> > On 17.10.11 16:06:01, Tomaz Canabrava wrote:
> >> probably has something to do with my python version, but ...
> >>
> >> Generating singleview.moc
> >> File
> >> "/kde/kde-workspace/plasma/generic/scriptengines/python//plasma_importer.py",
> >> lin
There is a draft PEP that's been circulated for consideration, but
/usr/bin/python2 is also (at least for now) a distro specific change from
Python upstream.
Scott K
> Got that same problem and a simple ln -s /usr/bin/python2
> $KDE_INST_DIR/bin/python solved it for me. Kind of a workaround, but
Got that same problem and a simple ln -s /usr/bin/python2
$KDE_INST_DIR/bin/python solved it for me. Kind of a workaround, but I
don't see any problem, as I don't think any of KDE uses python3 yet.
2011/10/17 Tomaz Canabrava :
> probably has something to do with my python version, but ...
>
> Gene
> On 17.10.11 16:06:01, Tomaz Canabrava wrote:
>> probably has something to do with my python version, but ...
>>
>> Generating singleview.moc
>> File
>> "/kde/kde-workspace/plasma/generic/scriptengines/python//plasma_importer.py",
>> line 107
>> exec code in mod.__dict__
>> ^
>>
On 17.10.11 16:06:01, Tomaz Canabrava wrote:
> probably has something to do with my python version, but ...
>
> Generating singleview.moc
> File
> "/kde/kde-workspace/plasma/generic/scriptengines/python//plasma_importer.py",
> line 107
> exec code in mod.__dict__
> ^
> SyntaxErr
probably has something to do with my python version, but ...
Generating singleview.moc
File
"/kde/kde-workspace/plasma/generic/scriptengines/python//plasma_importer.py",
line 107
exec code in mod.__dict__
^
SyntaxError: invalid syntax
make[2]: *** [compile_python_files] Error 1
Hi,
I just cloned kde-libs,kde-workspace,kde-baseapps with this steps:
mkdir $BRANCH
cd $BRANCH
git init
git remote add -t $BRANCH -f origin $REMOTE_REPO
git checkout $BRANCH
Then compile everything without problem.
On 9/22/11, Gorosito Gonzalo wrote:
> I have this one here:
>
> commit 6ef2c709
Compiling...
Build succeeded after 5 minutes, and 48 seconds.
Installing kdelibs.
Overall time for kdelibs was 6 minutes, and 6 seconds.
Building kde-workspace (2/2)
Waiting for source code update.
Source update complete for kde-workspace:
I have this one here:
commit 6ef2c70949c0188f72789b924d9d88b8fb72459e
Author: Aaron Seigo
Date: Mon Sep 19 16:18:52 2011 +0200
only allow valid values for the resize method, and add missing getters
I also rebuilt kdelibs after I pulled from this branch.
##
On Wednesday, September 21, 2011 11:56:59 Gorosito Gonzalo wrote:
> My kdelibs its already on KDE/4.7:
it was part of commit 6ef2c70949c0188f72789b924d9d88b8fb72459e
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer s
Aaron,
My kdelibs its already on KDE/4.7:
ggorosito@glaptop:~/kde/kdesrc/kde/kdelibs$ git pull origin KDE/4.7
>From git://anongit.kde.org/kdelibs
* branchKDE/4.7-> FETCH_HEAD
Already up-to-date.
Do I need to do something else?
Thanks
###
#
On Wednesday, September 21, 2011 12:07:36 Hugo Pereira Da Costa wrote:
> Adding kde-core-devel, which is better suited for these kind of emails.
>
> Seems to me that trunk is actually not up to date for kdelibs, and that
> accessor to
master is dead. do not use it. use the KDE/4.7 branch for buil
Adding kde-core-devel, which is better suited for these kind of emails.
Seems to me that trunk is actually not up to date for kdelibs, and that
accessor to
resizeMethodHint is missing from plasma/wallpaper.h / .cpp
See patch attached. (can someone fix/commit this ?)
At least it made things
Le Monday 6 June 2011 19:35:53, Zé a écrit :
> Error building kde/kanagram from master, the output:
>
> [ 22%] Building CXX object
> kanagram/src/CMakeFiles/kanagram.dir/kanagram.o
> /home/mmodem/rpm/BUILD/kdeedu/kanagram/src/kanagram.cpp:49:30: fatal
> error: sharedkvtmlfiles.
Error building kde/kanagram from master, the output:
[ 22%] Building CXX object
kanagram/src/CMakeFiles/kanagram.dir/kanagram.o
/home/mmodem/rpm/BUILD/kdeedu/kanagram/src/kanagram.cpp:49:30: fatal
error: sharedkvtmlfiles.h: No such file or directory
compilation terminated.
make[2]: *** [kanagram
47 matches
Mail list logo
