Re: [Duplicity-talk] compilec.py: _librsync Extension

[Joe Snikeris]

On Fri, Feb 18, 2011 at 7:25 AM, Kenneth Loafman <address@hidden> wrote:
> Except for very special cases, compilec.py is not used.  The normal process
> is to use 'sudo setup.py install'.

In that case, perhaps REPO-README should be changed, renamed, or
removed entirely.  I checked out the source using bzr, so naturally I
followed the instructions in REPO-README:

     "REPO README - Notes for people checking out of Launchpad (bzr)"

>
> The 'normal' place for librsync is /usr/lib.  In setup.py, you can use
> --librsync-dir to specify a different path.
>
> ...Ken
>
> On Fri, Feb 18, 2011 at 12:06 AM, Joe Snikeris <address@hidden> wrote:
>>
>> Hi all,
>> I had trouble compiling the librsync shared library using compilec.py.
>>  I had to point it to my local library and include directories:
>>
>> setup(name="CModule",
>>      version="cvs",
>>      description="duplicity's C component",
>>      ext_modules=[Extension("_librsync",
>>                             ["_librsyncmodule.c"],
>>                             libraries=["rsync"],
>>                             include_dirs=["/usr/local/include"],
>>                             library_dirs=["/usr/local/lib"])])
>>
>> Presumably, the rest of you didn't have to do this, otherwise it
>> wouldn't have been committed this way.  Out of curiosity, where is
>> librsync.so.1.0 and librsync.h located for the rest of you?
>>
>> Regards,
>> Joe Snikeris