installing libs on Windows

Andreas Pakulat apaku at gmx.de
Tue Jul 24 11:28:53 BST 2007


On 24.07.07 11:29:46, Ralf Habacker wrote:
> Andreas Pakulat schrieb:
> > On 22.07.07 20:13:37, Alexander Neundorf wrote:
> >> On Sunday 22 July 2007 11:33, Alex Merry wrote:
> >>> On Saturday 21 Jul 2007, Alexander Neundorf wrote:
> >> Can something be done using the registry ?
> >> Does this help us ?
> >> http://www.codeguru.com/Cpp/W-P/dll/article.php/c99#more
> >>     
> >
> > Ralf, how hard is it to change the registry inside kdewin-installer?
> >   
> setting the registry would be possible, but there are drawbacks. It is
> then required for every installed application and it bounds installation
> to the kdewin installer. Currently it is possible to unpack the zip
> files by hand, set the environment and start running kde apps. This
> would not be possible anymore. Additional moving the installation dir to
> another place would also not possible.

Well, for me this is the same, wether you have to change a path in the
registry or some environment variable makes not much difference, _if_ we
communicate clearly how to do it. So the only real drawback is that
you'd have to fix 2 places as changes in the environment have to be done
anyway.

> >> If a user downloads and installs KDE4/ a KDE4 application on Windows (e.g. 
> >> kdevelop), will this have the development stuff, i.e. the .lib files and the 
> >> headers ?
> >>     
> >
> > No, lib (i.e. headers and import lib) are separated from bin in the
> > packages.
> >
> >   
> >> If not, then for developing it could be a requirement to adjust the PATH, when 
> >> building a package, LIB_INSTALL_DIR can be set to bin/, so that it will just 
> >> work for users. That's possible right now without any modifications.
> >>     
> >
> > As Ralf already said, taking your example above without modifications
> > except that LIB_INSTALL_DIR will be set to bin/ on win32 it would
> > pollute the bin/ dir with the import and static libraries and also make
> > it harder to package those development parts because the current
> > packaging tool just zips up a list of files from a certain directory
> > without changing their position under that directory (i.e. moving from
> > one subdir to another). 
> >
> > So I think we should rather leave cmake-stuff as it is and see that we
> > go with the registry-thing. (Unless of course thats a problem)
> >
> >   
> For me the best solutions is if cmake would install the runtime into
> bin/ by default or would have a changeable default setting for RUNTIME
> DESTINATION, which could be set in KDE4Internals for all projects once.

Snipped the rest as I completely agree with you here. 

Andreas

-- 
You have an unusual understanding of the problems of human relationships.




More information about the kde-core-devel mailing list