The recent changes in OBUnitCell constantness mean that the SWIG
bindings do not compile in Visual C++ 9:
1>..\..\..\scripts\java\openbabel-java.cpp(2945) : error C2668:
'OpenBabel::OBUnitCell::WrapFractionalCoordinate' : ambiguous call to
overloaded function
and similarly for C# and python bi
On Wed, Oct 5, 2011 at 4:37 PM, Chris Morley wrote:
> The recent changes in OBUnitCell constantness mean that the SWIG
> bindings do not compile in Visual C++ 9:
>
> 1>..\..\..\scripts\java\openbabel-java.cpp(2945) : error C2668:
> 'OpenBabel::OBUnitCell::WrapFractionalCoordinate' : ambiguous call
On 5 October 2011 21:44, David Lonie wrote:
> On Wed, Oct 5, 2011 at 4:37 PM, Chris Morley wrote:
>> The recent changes in OBUnitCell constantness mean that the SWIG
>> bindings do not compile in Visual C++ 9:
>>
>> 1>..\..\..\scripts\java\openbabel-java.cpp(2945) : error C2668:
>> 'OpenBabel::OB
On 06/10/2011 09:24, Noel O'Boyle wrote:
> On 5 October 2011 21:44, David Lonie wrote:
>> On Wed, Oct 5, 2011 at 4:37 PM, Chris Morley wrote:
>>> The recent changes in OBUnitCell constantness mean that the SWIG
>>> bindings do not compile in Visual C++ 9:
>>>
>>> 1>..\..\..\scripts\java\openbabel
> Now on to how to avoid specifying the C# executable as an absolute
> address.
Is there a problem with the current setup?
> And whether to put all the OB files in a writable folder (one
> also without an absolute address), or whether to split off the /data folder.
What's the issue here? Is this
On 06/10/2011 10:03, Noel O'Boyle wrote:
>> Now on to how to avoid specifying the C# executable as an absolute
>> address.
>
> Is there a problem with the current setup?
It would be better if it used the information that was automatically
available rather than rely on the user knowing that he has
