On 01/04/2011 08:50 AM, Michael Wild wrote:
> On 01/03/2011 06:23 PM, Todd Gamblin wrote:
>> On Jan 3, 2011, at 1:34 AM, Michael Wild wrote:
>>
>>> On 01/03/2011 09:11 AM, Todd Gamblin wrote:
Is there some standard way in CMake to get a project-local install
destination for python librar
On 01/03/2011 06:23 PM, Todd Gamblin wrote:
> On Jan 3, 2011, at 1:34 AM, Michael Wild wrote:
>
>> On 01/03/2011 09:11 AM, Todd Gamblin wrote:
>>> Is there some standard way in CMake to get a project-local install
>>> destination for python libraries, e.g.:
>>>
>>> ${CMAKE_INSTALL_PREFIX}/lib
On Jan 3, 2011, at 1:34 AM, Michael Wild wrote:
> On 01/03/2011 09:11 AM, Todd Gamblin wrote:
>> Is there some standard way in CMake to get a project-local install
>> destination for python libraries, e.g.:
>>
>> ${CMAKE_INSTALL_PREFIX}/lib/python2.6/site-packages
>>
>> Is this something f
On 01/03/2011 09:11 AM, Todd Gamblin wrote:
> Is there some standard way in CMake to get a project-local install
> destination for python libraries, e.g.:
>
> ${CMAKE_INSTALL_PREFIX}/lib/python2.6/site-packages
>
> Is this something find modules typically provide? I can construct this nam
Is there some standard way in CMake to get a project-local install destination
for python libraries, e.g.:
${CMAKE_INSTALL_PREFIX}/lib/python2.6/site-packages
Is this something find modules typically provide? I can construct this name
easily enough myself, but it involves querying the
