I remember coming accross something like this before (mangled cmake
files). Are you using the latest Scripts and Compile? These were patched
to avoid this problem. (Actually, it might just have been Scripts that
was patched)
Frank
Guilherme Bedin wrote:
> Hi,
>
> Tips for compiling KDE 4.2.0
Lucas C. Villa Real wrote:
> BTW, have you tried to compile KDE within ChrootCompile? It's
> interesting to make sure KDE still compiles under that environment, as
> that's how we compile the so called official packages.
>
Ah thanks, I'll try that. I was wondering whether there was such a tool
in
Yep KDE 4.2 is still in beta and what's more, I just reinstalled KDE
from scratch and the
oxygen theme has vanished :-S . So they are still a little way from
full readiness
anyhow. I just attached them to save you guys some hassle. :)
Frank
On 9 Jan 2009, at 10:12, Lucas C. Villa Real wrote
Frank Wilson wrote:
>> Would you mind checking out an updated snapshot of Scripts and
>> verifying if it works better now?
>
> Sure, I'll test it out.
>
> Thanks,
>
> Frank
> ___
> gobolinux-devel mailing l
> Would you mind checking out an updated snapshot of Scripts and
> verifying if it works better now?
Sure, I'll test it out.
Thanks,
Frank
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo
Hi. I've been mucking about with the kde 4.2 betas and I've got a
with problems how cmake recipes interact with kde 4.2 beta 2.
Basically whenever I compile kdepimlibs, Compile seems
significantly change KdepimLibsConfig.cmake (which gets installed in
/System/Links/Libraries/KdepimLibs/cmake/). T
or_Sunset/contents/screenshot.png"
does not exist
I have two questions about this. Firstly, is there some cmake option
that would allow this check to pass? Secondly, what is the purpose of
this check?
Thanks,
Frank Wilson
___
gobolinux-devel mailing list
gobolinux-devel@lists.gobolinux.org
http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
sys...@kde.org
> Cc: Allen Winter , Frank Wilson >
> Subject: Re: Fwd: Kde 4.2 beta1 feedback: Notes on cmake scripts
> Reply-To: neund...@kde.org
>
> On Friday 19 December 2008, Allen Winter wrote:
>&g
would eliminate the need to set this for many cmake recipes.
I will try this later after I have tested a few more KDE4 recipes.
Frank
On 17 Dec 2008, at 12:36, Frank Wilson wrote:
> Hmm... using LIB_INSTALL_DIR was a bad idea (for me at least).
> Using that variable means the KDE will try
ement point to the unique path of each library?
I suppose
the latter is closer to the gobo way, but harder to realize.
Frank
On 17 Dec 2008, at 12:07, Frank Wilson wrote:
> Right I am going to just assume that WIN32 stuff was just accidentally
> changed with sed and is just a
-FindKdepimLibs.patch
Description: Binary data
On 17 Dec 2008, at 10:51, Frank Wilson wrote:
By the way I should have made it clear that the patch applies to KDE-
Libs 4.1.3.
Frank
On 17 Dec 2008, at 10:31, Frank Wilson wrote:
I am working on recipes for KDE 4.1.80 (the KDE 4.2 beta 1 release
[1]).
For
By the way I should have made it clear that the patch applies to KDE-
Libs 4.1.3.
Frank
On 17 Dec 2008, at 10:31, Frank Wilson wrote:
> I am working on recipes for KDE 4.1.80 (the KDE 4.2 beta 1 release
> [1]).
> For some reason I found that I could not apply the patch [2] for 4.1.3
I am working on recipes for KDE 4.1.80 (the KDE 4.2 beta 1 release [1]).
For some reason I found that I could not apply the patch [2] for 4.1.3
to the new release. However I still think the new release needs to
be patched in a similar way. I would like to have a better understanding
of the current
13 matches
Mail list logo
