[RFC] Idea how to fix PATH (and other) problems
Ch.Ehrlicher at gmx.de
Wed Aug 8 11:24:22 CEST 2007
An: kde-windows at kde.org
> On 08.08.07 09:49:23, Christian Ehrlicher wrote:
> > Von: Andreas Pakulat
> > > On 08.08.07 06:32:51, Christian Ehrlicher wrote:
> > > > As I only want to have one executable we'Ve two options
> > > > a) 'unpack' the real executable into a temp directory and execute it
> > > > b) execute it from memory
> > > >
> > > > I'd prefer the second, but for the start the first will work too
> > >
> > > Uhm, but CreateProcess doesn't work for execut memory, or does it? I
> > > mean that solution that PutHuhn presented for executing from memory
> > > sounded extremly scary and I'd rather have the packager copy the
> > > around for the packages instead of that ugly solution.
> > >
> > But with your solution you don't solve anything - I as the user want to
> execute my program by clicking on my executable and not on another one
> somewhere else.
> Yes I do, I solve the problem of having to set PATH, which leaves the
> problems of the app icon not embedded into the executable (I actually
> couldn't care less wether the icon is in the executable or separate as
> .ico) and the problem of two incompatible abi's from compilers so you
> can't mix msvc and mingw libs/executables which can be solved in the
> installer by only providing msvc or mingw apps depending on which qt is
Didn't you just want to unzip your packages? I don't think we can restrict a user to a specific qt version - what when a program is just available for one platform?
There's no need to discuss about the app icon - it's really an easy task to fix.
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
More information about the Kde-windows