Michael Stahl wrote: > > What more curl(ing) stuff do I need? > > uhm, there really is a very simple rule for this: if configure complains > that it cannot find the "foo" library, and you see that you have a > "libfooN" package installed, then you should install a package that (on > debian or derived distros) is either named "libfoo-dev" or "libfooN-dev". > that rule should apply at least 95% of the time. > Heh. I wonder why people with virtually no build-stuff-on-linux experience actually choose OOo as their very first project, likely one of the hardest picks one could make.
Maybe a disclaimer like: "if you've never built stuff on Linux, please start with easy project <Foo>, build instructions at <Bah>" should be added to the build guide? > but of course there is also a simpler way: for a lot (but not all) of > external libraries, the OOo repository already contains a copy. > you can enable those by passing --without-system-libs to configure. > I wouldn't call it simpler, if the general concept of a -dev package is not grokked beforehand. Cheers, -- Thorsten "Java isn't platform independent; it is a platform." -- Stroustrup
pgpFDTWDQyqlt.pgp
Description: PGP signature
