On 29 August 2010 23:08, Rajarshi Guha wrote:
>
> On Aug 29, 2010, at 5:25 PM, Noel O'Boyle wrote:
>
>> On 29 August 2010 21:49, Rajarshi Guha wrote:
>>>
>>> On Aug 29, 2010, at 5:31 AM, Noel O'Boyle wrote:
>>>
Hi Rajarshi
It seems that the problem was in generating the SWIG bindin
On Aug 29, 2010, at 5:25 PM, Noel O'Boyle wrote:
> On 29 August 2010 21:49, Rajarshi Guha
> wrote:
>>
>> On Aug 29, 2010, at 5:31 AM, Noel O'Boyle wrote:
>>
>>> Hi Rajarshi
>>>
>>> It seems that the problem was in generating the SWIG bindings. Is
>>> there something non-standard about your swi
On 29 August 2010 21:49, Rajarshi Guha wrote:
>
> On Aug 29, 2010, at 5:31 AM, Noel O'Boyle wrote:
>
>> Hi Rajarshi
>>
>> It seems that the problem was in generating the SWIG bindings. Is
>> there something non-standard about your swig install? It seems that
>> swig cannot find its own include fil
On Aug 29, 2010, at 5:31 AM, Noel O'Boyle wrote:
> Hi Rajarshi
>
> It seems that the problem was in generating the SWIG bindings. Is
> there something non-standard about your swig install? It seems that
> swig cannot find its own include files.
Hmm, I had installed SWIG from mac ports
>
> I've
Hi Rajarshi
It seems that the problem was in generating the SWIG bindings. Is
there something non-standard about your swig install? It seems that
swig cannot find its own include files.
I've never had to specify this but there is an additional option,
"-DSWIG_DIR" which on my Windows system point
Hi, I just updated to the latest SVN and recompiled OpenBabel which
seems towork, but then I also tried to compile the Python extensions
and I get the following:
$: cmake -DCMAKE_INSTALL_PREFIX=/usr/local/openbabel
-DPYTHON_BINDINGS=ON -DRUN_SWIG=ON
-DSWIG_EXECUTABLE=/opt/local/bin/swig ~/src/open
