On 10.07.07 07:46:35, Ralf Habacker wrote:
> Alexander Neundorf schrieb:
> > On Monday 09 July 2007 17:18, Ralf Habacker wrote:
> >
> >> Andreas Pakulat schrieb:
> >>
> >>> On 09.07.07 06:49:23, Thiago Macieira wrote:
> >>>
> Andreas Pakulat wrote:
>
> > As I t
On 09.07.07 22:35:49, Alexander Neundorf wrote:
> On Sunday 08 July 2007 14:53, Andreas Pakulat wrote:
> > On 08.07.07 20:49:23, Ralf Habacker wrote:
> > > Andreas Pakulat schrieb:
> > > > On 08.07.07 19:31:49, Andreas Pakulat wrote:
> > > >> On 08.07.07 11:06:32, Matt Rogers wrote:
> > > >>> On Ju
Alexander Neundorf schrieb:
> On Monday 09 July 2007 17:18, Ralf Habacker wrote:
>
>> Andreas Pakulat schrieb:
>>
>>> On 09.07.07 06:49:23, Thiago Macieira wrote:
>>>
Andreas Pakulat wrote:
> As I tried to explain at the start: this is specifically about
>
Hi,
On Sunday 08 July 2007 14:53, Andreas Pakulat wrote:
> On 08.07.07 20:49:23, Ralf Habacker wrote:
> > Andreas Pakulat schrieb:
> > > On 08.07.07 19:31:49, Andreas Pakulat wrote:
> > >> On 08.07.07 11:06:32, Matt Rogers wrote:
> > >>> On Jul 8, 2007, at 9:35 AM, Andreas Pakulat wrote:
> >
On Monday 09 July 2007 17:18, Ralf Habacker wrote:
> Andreas Pakulat schrieb:
> > On 09.07.07 06:49:23, Thiago Macieira wrote:
> >> Andreas Pakulat wrote:
> >>> As I tried to explain at the start: this is specifically about
> >>> installing module's in different locations.
> >>
> >> I think KDEDIRS
Andreas Pakulat schrieb:
> On 09.07.07 06:49:23, Thiago Macieira wrote:
>
>> Andreas Pakulat wrote:
>>
>>> As I tried to explain at the start: this is specifically about
>>> installing module's in different locations.
>>>
>> I think KDEDIRS is the best way.
>>
>
> Ok, tried and
On 09.07.07 06:49:23, Thiago Macieira wrote:
> Andreas Pakulat wrote:
> >As I tried to explain at the start: this is specifically about
> >installing module's in different locations.
>
> I think KDEDIRS is the best way.
Ok, tried and it works quite well. now the question is: where to put
this:
e
Andreas Pakulat wrote:
>On 08.07.07 23:42:24, Thiago Macieira wrote:
>> Andreas Pakulat wrote:
>> >So using kde4-config --path data as destination for
>> >FindKDevPlatform.cmake is not an option and neither is installing
>> >KDevPlatformConfig.cmake into /lib/kdevplatform.
>>
>> Why not?
>>
>> $ kd
On 08.07.07 23:42:24, Thiago Macieira wrote:
> Andreas Pakulat wrote:
> >So using kde4-config --path data as destination for
> >FindKDevPlatform.cmake is not an option and neither is installing
> >KDevPlatformConfig.cmake into /lib/kdevplatform.
>
> Why not?
>
> $ kde4-config --path data
> /home/
On 08.07.07 20:26:34, Andreas Pakulat wrote:
> On 08.07.07 19:31:49, Andreas Pakulat wrote:
> > On 08.07.07 11:06:32, Matt Rogers wrote:
> > > On Jul 8, 2007, at 9:35 AM, Andreas Pakulat wrote:
> > > > due to a problem (I'd call it a bug actually) in cmake its not
> > > > possible
> > > > to inst
Andreas Pakulat wrote:
>So using kde4-config --path data as destination for
>FindKDevPlatform.cmake is not an option and neither is installing
>KDevPlatformConfig.cmake into /lib/kdevplatform.
Why not?
$ kde4-config --path data
/home/thiago/.kde4/share/apps/:/home/thiago/KDE4/share/apps/
$ mkdir
On 08.07.07 21:55:17, Ralf Habacker wrote:
> Andreas Pakulat schrieb:
> > On 08.07.07 21:26:42, Ralf Habacker wrote:
> >> In the meantime I found a simpler way by appending all pathes from KDEDIRS
> >> (+
> >> 'share/apps/cmake/module') added to the CMAKE_MODULE_PATH in
> >> FindKDE4Internal.cm
Andreas Pakulat schrieb:
> On 08.07.07 21:26:42, Ralf Habacker wrote:
>
>> Andreas Pakulat schrieb:
>>
>>> On 08.07.07 20:49:23, Ralf Habacker wrote:
>>>
I have added the following stuff to a new file in
/lib/kdevplatform/KDevPlatformConfig.cmake
if(WIN32)
On 08.07.07 21:26:42, Ralf Habacker wrote:
> Andreas Pakulat schrieb:
> >On 08.07.07 20:49:23, Ralf Habacker wrote:
> >>I have added the following stuff to a new file in
> >>/lib/kdevplatform/KDevPlatformConfig.cmake
> >>
> >>if(WIN32)
> >>file(TO_CMAKE_PATH "$ENV{ProgramFiles}" ProgramFiles)
Andreas Pakulat schrieb:
On 08.07.07 20:49:23, Ralf Habacker wrote:
Andreas Pakulat schrieb:
On 08.07.07 19:31:49, Andreas Pakulat wrote:
On 08.07.07 11:06:32, Matt Rogers wrote:
On Jul 8, 2007, at 9:35 AM, Andreas Pakulat wrote:
due to a prob
On 08.07.07 20:49:23, Ralf Habacker wrote:
> Andreas Pakulat schrieb:
> > On 08.07.07 19:31:49, Andreas Pakulat wrote:
> >
> >> On 08.07.07 11:06:32, Matt Rogers wrote:
> >>
> >>> On Jul 8, 2007, at 9:35 AM, Andreas Pakulat wrote:
> >>>
> due to a problem (I'd call it a bug actu
Andreas Pakulat schrieb:
> On 08.07.07 19:31:49, Andreas Pakulat wrote:
>
>> On 08.07.07 11:06:32, Matt Rogers wrote:
>>
>>> On Jul 8, 2007, at 9:35 AM, Andreas Pakulat wrote:
>>>
due to a problem (I'd call it a bug actually) in cmake its not
possible
to install 2 kd
On 08.07.07 19:31:49, Andreas Pakulat wrote:
> On 08.07.07 11:06:32, Matt Rogers wrote:
> > On Jul 8, 2007, at 9:35 AM, Andreas Pakulat wrote:
> > > due to a problem (I'd call it a bug actually) in cmake its not
> > > possible
> > > to install 2 kde modules where one depends on the other into sep
On 08.07.07 11:06:32, Matt Rogers wrote:
> On Jul 8, 2007, at 9:35 AM, Andreas Pakulat wrote:
> > due to a problem (I'd call it a bug actually) in cmake its not
> > possible
> > to install 2 kde modules where one depends on the other into separate
> > directories (and separate directories from kd
On Jul 8, 2007, at 9:35 AM, Andreas Pakulat wrote:
> Hi,
>
> due to a problem (I'd call it a bug actually) in cmake its not
> possible
> to install 2 kde modules where one depends on the other into separate
> directories (and separate directories from kdelibs). For packaging KDE
> module's howe
Hi,
due to a problem (I'd call it a bug actually) in cmake its not possible
to install 2 kde modules where one depends on the other into separate
directories (and separate directories from kdelibs). For packaging KDE
module's however its needed that each module is installed into its own
prefix.
W
21 matches
Mail list logo
