[RFC] Idea how to fix PATH (and other) problems

[Andreas Pakulat]

On 08.08.07 11:24:22, Christian Ehrlicher wrote:
> 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
> > .dll's
> > > > 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
> > chosen.
> Didn't you just want to unzip your packages?

Well, somebody who downloads the .zip's from an ftp server an be
expected to be intelligent enough to choose only matching zips.

> I don't think we can restrict a user to a specific qt version - what when a program is just available for one platform?

Then he has to switch to the other, but IMHO we shouldn't force 2 Qt
versions on the user either. Also: Do you have any example for that
case? I can only imagine a Qt only program that a user wants to use
which use something that mingw doesn't support. However I also think
that in windows packages for apps you often get Qt bundled so that
wouldn't be a problem either. Until we find a use-case we shouldn't care
too much about that (i.e. if its easily doable, sure, if it gets
complicated let it be until need arises).

Andreas

-- 
You will have domestic happiness and faithful friends.