Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread David Faure
On Thursday 10 May 2012 23:44:31 Stephen Kelly wrote: > Stephen Kelly wrote: > > David Faure wrote: > >> On Thursday 10 May 2012 23:21:55 Stephen Kelly wrote: > >>> We have RPATH for that. Is that enough? > >> > >> Doesn't seem to work currently. > >> > >> Apply attached patch in kcoreaddons, mak

Re: kdelibs (tier1) splitting package/repository granularity

2012-05-10 Thread Kevin Ottens
On Thursday 10 May 2012 23:00:16 Alexander Neundorf wrote: > On Thursday 10 May 2012, Kevin Ottens wrote: > > On Wednesday 9 May 2012 21:38:55 Alexander Neundorf wrote: > > > I understand correctly that tier1 libs do not have any dependencies > > > between each other, right ? > > > > Correct. > > >

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Patrick Spendrin
Am 10.05.2012 23:22, schrieb David Faure: > On Thursday 10 May 2012 12:09:59 Patrick Spendrin wrote: >> Am 10.05.2012 11:52, schrieb David Faure: >>> Even on Windows I like to have everything in one place, but yes, it >>> requires setting PATH. No big deal, though... We're talking about >>> program

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Stephen Kelly
Stephen Kelly wrote: > David Faure wrote: > >> On Thursday 10 May 2012 23:21:55 Stephen Kelly wrote: >>> David Faure wrote: >>> >> Now we don't do that anymore. >>> >> So for Windows the dlls and the exes have to go into the same >>> >> directory. >>> > >>> > And how will the libs be found on Un

Re: kdelibs (tier1) splitting package/repository granularity

2012-05-10 Thread Patrick Spendrin
Am 10.05.2012 23:00, schrieb Alexander Neundorf: > The situation with the tier1 libs is very different than with KDE4 > kdelibs: no dependencies between each other, no runtime dependencies. > > Why not put all tier1 libraries into one repository and release them as > one package ? > > Keep t

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Stephen Kelly
David Faure wrote: > On Thursday 10 May 2012 23:21:55 Stephen Kelly wrote: >> David Faure wrote: >> >> Now we don't do that anymore. >> >> So for Windows the dlls and the exes have to go into the same >> >> directory. >> > >> > And how will the libs be found on Unix, given that they are under lib

KAction and KShortcut in frameworks

2012-05-10 Thread Mark
Hi, Making this quite detailed and long mail as per request from David Faure (twice) ;) So, I've been patching KShortcut up to support multiple shortcuts: https://git.reviewboard.kde.org/r/104801/ and it's working just fine with that patch. However, there seems to be some duplication between: KAc

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread David Faure
On Thursday 10 May 2012 23:21:55 Stephen Kelly wrote: > David Faure wrote: > >> Now we don't do that anymore. > >> So for Windows the dlls and the exes have to go into the same directory. > > > > And how will the libs be found on Unix, given that they are under lib/ and > > not bin/? > > > > Putt

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Stephen Kelly
David Faure wrote: >> Now we don't do that anymore. >> So for Windows the dlls and the exes have to go into the same directory. > > And how will the libs be found on Unix, given that they are under lib/ and > not bin/? > > Putting all executables in bin doesn't remove the need for wrapper > scri

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread David Faure
On Thursday 10 May 2012 12:09:59 Patrick Spendrin wrote: > Am 10.05.2012 11:52, schrieb David Faure: > > Even on Windows I like to have everything in one place, but yes, it > > requires setting PATH. No big deal, though... We're talking about > > programs run by developers, who have to set PATH any

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread David Faure
On Thursday 10 May 2012 22:53:01 Alexander Neundorf wrote: > On Thursday 10 May 2012, David Faure wrote: > > On Thursday 10 May 2012 10:36:20 Patrick Spendrin wrote: > > > > set(EXECUTABLE_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}) > > > > > > Yes, the EXECUTABLE_OUTPUT_PATH should be set per projec

Re: kdelibs (tier1) splitting package/repository granularity

2012-05-10 Thread Alexander Neundorf
On Thursday 10 May 2012, Kevin Ottens wrote: > On Wednesday 9 May 2012 21:38:55 Alexander Neundorf wrote: > > I understand correctly that tier1 libs do not have any dependencies > > between each other, right ? > > Correct. > > > Do we plan to put each of those into a separate repository and relea

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Alexander Neundorf
On Thursday 10 May 2012, David Faure wrote: > On Thursday 10 May 2012 10:36:20 Patrick Spendrin wrote: > > > set(EXECUTABLE_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}) > > > > Yes, the EXECUTABLE_OUTPUT_PATH should be set per project into the > > project binary_dir\bin > > As a linux developer, I do

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Alexander Neundorf
On Thursday 10 May 2012, Patrick Spendrin wrote: > Am 10.05.2012 11:52, schrieb David Faure: > > On Thursday 10 May 2012 11:15:57 Patrick Spendrin wrote: > >> Am 10.05.2012 10:45, schrieb David Faure: > >>> On Thursday 10 May 2012 10:36:20 Patrick Spendrin wrote: > > set(EXECUTABLE_OUTPUT_PATH

Re: Removing WinCE support

2012-05-10 Thread Alexander Neundorf
On Thursday 10 May 2012, Volker Krause wrote: > On Wednesday 09 May 2012 16:47:17 Stephen Kelly wrote: > > Alexander Neundorf wrote: > > > Hi, > > > > > > KDAB made kdelibs in some way work with Win CE. > > > > > > Now Win CE is a very different OS, and IMO we should not even strive to > > > port

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Patrick Spendrin
Am 10.05.2012 11:52, schrieb David Faure: > On Thursday 10 May 2012 11:15:57 Patrick Spendrin wrote: >> Am 10.05.2012 10:45, schrieb David Faure: >>> On Thursday 10 May 2012 10:36:20 Patrick Spendrin wrote: > set(EXECUTABLE_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}) Yes, the EXECUTABLE_

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread David Faure
On Thursday 10 May 2012 11:15:57 Patrick Spendrin wrote: > Am 10.05.2012 10:45, schrieb David Faure: > > On Thursday 10 May 2012 10:36:20 Patrick Spendrin wrote: > >>> set(EXECUTABLE_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}) > >> > >> Yes, the EXECUTABLE_OUTPUT_PATH should be set per project into t

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Patrick Spendrin
Am 10.05.2012 10:45, schrieb David Faure: > On Thursday 10 May 2012 10:36:20 Patrick Spendrin wrote: >>> set(EXECUTABLE_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}) >> >> Yes, the EXECUTABLE_OUTPUT_PATH should be set per project into the >> project binary_dir\bin > > As a linux developer, I don't like

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread David Faure
On Thursday 10 May 2012 10:36:20 Patrick Spendrin wrote: > > set(EXECUTABLE_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}) > > Yes, the EXECUTABLE_OUTPUT_PATH should be set per project into the > project binary_dir\bin As a linux developer, I don't like this. I want to be able to do make && ./kurltest

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Patrick Spendrin
[resending since I am now subscribed ;-)] Am 09.05.2012 22:18, schrieb Alexander Neundorf: > Hi, > > in several autotests/ directories in tier1/ EXECUTABLE_OUTPUT_PATH is > set like this: > > set(EXECUTABLE_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}) Yes, the EXECUTABLE_OUTPUT_PATH should be set pe

Re: setting EXECUTABLE_OUTPUT_PATH in tier1/ tests ?

2012-05-10 Thread Patrick Spendrin
Am 09.05.2012 22:18, schrieb Alexander Neundorf: > Hi, > > in several autotests/ directories in tier1/ EXECUTABLE_OUTPUT_PATH is > set like this: > > set(EXECUTABLE_OUTPUT_PATH ${CMAKE_CURRENT_BINARY_DIR}) Yes, the EXECUTABLE_OUTPUT_PATH should be set per project into the project binary_dir\bin