Thanks for the Google results
Is it possible to build KDrive in a pure SDL / OpenGL environment?
The package pointed at has too many dependencies…
Let’s examine that further:
x11-server-common = 1.6.5-1.2mdv2010.0
The above are all pretty self-contained libs and should build
anywhere. They’re used internally in popular open source X
This is a dependency you get when you compile with -pthread. MSWindows
used to have a POSIX compatibility layer. If it doesn’t have pthread
API support now, there are other options like cygwin.
I’m not sure what the parts in parenthesis are supposed to mean
exactly, but this is all just the standard C library.
This is dlopen(3) et al. It lets programs take a more hands-on
approach to dynamic linkage. I have the same thing to say about this
as I did about pthreads.
This is the standard math library. It should also be available
anywhere like the standard C library. You shouldn’t have to compile
this yourself, it will come with your software building tools like gcc
or whatever you use.
This is well contained, ultra-portable code.
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadIsLzma) <= 4.4.6-1
I’m not exactly sure what this means, but rpmlib has also been built
on a wide variety of platforms. I’m going to guess the parts in
parenthesis here reflect configuration options your rpmlib needs to be
built with. They seem to relate only to compressed file archives.
I don’t know what this is, but I recognize “rtld” as being the prefix
to macros used with the dlopen(3) et al APIs mentioned earlier with
respect to libdl.
This is another lib providing POSIX APIs. Again, Linux or Cygwin are
probably the right answer.
This is DBUS, an inter-process message passing API. The only
dependency this one has is an XML parser, according to its website.
This one may break you. I’m pretty sure HAL is very low-level and
there may not exist an implementation for a platform like MSWindows.On Tue, Jun 15, 2010 at 12:15 PM, Philippe Laporte wrote: