Paths to internal executables (c.f. libexec) hard-coded

2015-08-26 Thread Kevin Funk
Heya, This is problem on Windows because the *final* installation location is not known at compile-time (obviously software is installed via installers, users can pick up the installation prefix). Of course this also limits the relocateability on other platforms, so it's not just a Windows issu

Re: Paths to internal executables (c.f. libexec) hard-coded

2015-08-26 Thread Volker Krause
On Wednesday 26 August 2015 13:15:15 Kevin Funk wrote: > Heya, > > This is problem on Windows because the *final* installation location is not > known at compile-time (obviously software is installed via installers, users > can pick up the installation prefix). Of course this also limits the > rel

Re: Paths to internal executables (c.f. libexec) hard-coded

2015-08-26 Thread Kevin Funk
On Wednesday 26 August 2015 13:40:20 Volker Krause wrote: > On Wednesday 26 August 2015 13:15:15 Kevin Funk wrote: > > Heya, > > > > This is problem on Windows because the *final* installation location is > > not > > known at compile-time (obviously software is installed via installers, > > users

Re: Paths to internal executables (c.f. libexec) hard-coded

2015-08-27 Thread David Faure
On Thursday 27 August 2015 00:14:50 Kevin Funk wrote: > > If we want to support this case, then we'd need to create a > KSomething::libexecPaths() method returning the following search path (in > order): > - Windows: > - Just QCA::applicationDirPath() (we control the install layout anyway) >

Re: Paths to internal executables (c.f. libexec) hard-coded

2015-08-27 Thread Volker Krause
On Thursday 27 August 2015 00:14:50 Kevin Funk wrote: > On Wednesday 26 August 2015 13:40:20 Volker Krause wrote: > > On Wednesday 26 August 2015 13:15:15 Kevin Funk wrote: > > > Heya, > > > > > > This is problem on Windows because the *final* installation location is > > > not > > > known at comp