Finding APR
Andreas Pakulat
apaku at gmx.de
Wed May 9 19:28:03 UTC 2007
On 09.05.07 20:49:35, Andreas Pakulat wrote:
> On 09.05.07 10:30:41, Matthew Woehlke wrote:
> > Andreas Pakulat wrote:
> > > On 08.05.07 18:02:59, Matthew Woehlke wrote:
> > >> Did you look at the revision I pointed you at yet? That's exactly what I
> > >> did in kdesdk :-). (Actually you want to use FIND_LIBRARY to "add lib
> > >> and .so", but close enough.)
> > >
> > > Of course I did :) Well, splitting at "-" is just as bad as splitting at
> > > " ", it may be inside a path as well.
> >
> > Ok, from your "this might work" it sounded like you hadn't. :-)
> >
> > > Anyway I'm going to build apr tomorrow locally and put it into a path
> > > with spaces, lets see what apr-config tells me afterwards (I'm guessing
> > > it will give me -Lfoo bar or -Lfoo\ bar, but no quotes).
> >
> > Which means it's broken, of course ;-) but wouldn't surprise me.
>
> Couldn't you've said that apr uses autotools for building? Autotools
> don't work with directories containing spaces. While configure works and
> make obviously too, the installation doesn't because install doesn't
> seem to handle whitespace-dirs.
>
> So bottom line is: We don't have to worry about whitespace in paths on
> windows and unix. So apr-config and apu-config will be required to find
> apr/apu in our cmake macro.
Also I'd like to add that kdesdk won't build on windows this way.
subversion-1 is not existent on windows, so its either
#ifdef WIN32
#include <svn_*>
#else
#include <subversion-1/svn_*>
#endif
or have subversion-1 in the include dirs (like kdevelop does for unix
already)
Andreas
--
You will be given a post of trust and responsibility.
More information about the KDevelop-devel
mailing list