| |||||||||||||
|
| |||||||||||||
Repositioning the KDE Brand (KDE.News)Repositioning the KDE Brand (KDE.News)Posted Nov 27, 2009 2:50 UTC (Fri) by dlang (✭ supporter ✭, #313)In reply to: Repositioning the KDE Brand (KDE.News) by lysse Parent article: Repositioning the KDE Brand (KDE.News)
please name a single program which has it's build system setup to fetch the source code for all libraries that it depends on, configure them, and build them when you try to build the program
nothing does this, and there are good reasons why this is so.
do you want the developers tracking the details of all the libraries that they use, where to get them, how to configure them appropriately (for all different platforms no less), how to install them without conflicts on every distro out there, etc.
or do you want them working on improving their application and documenting that they need library X (version > y, tested up through version z) and let the users or distro maintainers pull, configure, and install the appropriate libraries?
personally, I want the developers to work on their own app.
(Log in to post comments)
kdesvn-build Posted Nov 27, 2009 3:44 UTC (Fri) by sbishop (guest, #33061) [Link] please name a single program which has it's build system setup to fetch the source code for all libraries that it depends on, configure them, and build them when you try to build the program KDE, funny enough: http://kdesvn- build.kde.org/. I've used it on old RHEL systems to build a decent, up- to-date KDE. It was nice to have everything taken care of for me.
kdesvn-build Posted Nov 27, 2009 4:50 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
WOW, you mean that it will fetch the code for glibc and compile it if the development packages are not already installed on the system? what about PAM libraries?
I suspect that the most it did was to grab other KDE specific libraries.
kdesvn-build Posted Nov 29, 2009 18:17 UTC (Sun) by sbishop (guest, #33061) [Link]
glibc and PAM, huh? Well, you need to be careful. If you have the script handle the user-space component of your operating system, it must, of course, handle the kernel-space component as well. You will, if I remember right, end up running FreeBSD. (It's pretty popular with the KDE devs.)
Typically, however, kdesvn-build will only build and install Qt, taglib, CMake, and QCA, among others.
|
|
||||||||||||