Okay, my build from r158 has just finished - it completes fine. I'll try 
reswigging and see what happens.

I don't think you need to rebuild OCC just yet (as it takes forever!). It'll be 
useful to see if you can build without swig.

As for principle, I agree with you, but I like to get something working and 
then 
polish it :-)

Let us know how you get on,

        Arthur


M. Nawijn wrote:
> On Thu, Mar 19, 2009 at 10:10 PM, Arthur Magill <arthur.mag...@epfl.ch> wrote:
>> Hi Marco,
>>
>> Hmm, I don't really understand why I have this working and you don't. This
>> doesn't look like a 64-bit issue, and I think that's the only difference
>> between us. How did you install OCC? Is it patched, or the original?
>>
> It is (or at least should be) original.
>> When I've used the setup.py script, it hasn't rebuilt the SWIG files by
>> default. It makes the build much faster, and removes a stage of uncertainty.
>> Could you tell us exactly the step you've taken to build?  Mine have been:
>>
>> 1) Clean checkout from SVN (I currently have r158)
>> 2) Edit src/environment.py to set OCC_INC, OCC_LIB (lines 61 and 62)
>>  OCC_INC=/opt/occ/inc OCC_LIB=/opt/occ/lib in your case I think?
>> 3) python setup.py build
>> 4) su
>> 5) python setup.py install
>> 6) source /usr/local/occ63/env_DRAW.sh
>> 7) python Tools/InteractiveViewer/InteractiveViewer.py
> I do exactly the same, except for one thing. I force a rebuild of the
> SWIG files.
> For me this was just a matter of principle. PythonOCC should build from 
> scratch
> for any Windows/Linux/Unix system. Ofcourse Thomas already did a fantastic 
> job!
> 
> I will try with the pre-build swig files. See if they compile properly
> on my system.
>> You may need to su before (3) rather than (4). Did you deliberately force
>> re-swigging? Are you sure you're not building from a half-built set of
>> source files? Did you use a "svn co" or "svn update"? It may be worth
>> deleting your local set and doing a fresh checkout. Does $CASROOT point to
>> the right place?
> I did a fresh checkout this afternoon and started from scratch
> (emptied the SWIG_...linux folder).
> 
>> In case you haven't guessed, I'm stabbing in the dark now, I'm not sure
>> what's wrong. But it must be something simple.
>>
> I probably is, I just have to find it. What I will probably do is
> completely start over with OCC itself.
> Recompile and check that it works fine. Then checkout PythonOCC again
> and rebuild with existing
> SWIG files.
>> Arthur
>>
> Thanks for the feedback. I really appreciate this.
> 
>> M. Nawijn wrote:
>>> Hello Thomas,
>>>
>>> I did a fresh checkout and then used the setup.py procedure. At least
>>> one thing is re-assuring. It fails consistently
>>>
>>>
>>>
>>> swigging
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl.i
>>> to
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c
>>> swig -python -modern -fcompact -c++ -DHAVE_LIMITS_H -DHAVE_CONFIG_H
>>> -DCSFDB -DOCC_CONVERT_SIGNALS -DLIN -DLININTEL -D_GNU_SOURCE=1 -outdir
>>> /home/nawijn/scratch/pythonOCC/src/OCC -o
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl.i
>>> g++ -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -Wall
>>> -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
>>> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
>>> -fPIC -DHAVE_CONFIG_H -DHAVE_LIMITS_H -DCSFDB -DOCC_CONVERT_SIGNALS
>>> -DLIN -DLININTEL -D_GNU_SOURCE=1 -I/opt/occ/inc
>>> -I/usr/include/python2.5 -c
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c
>>> -o
>>> build/temp.linux-x86_64-2.5/home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.o
>>> -O0
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c:
>>> In constructor ‘swig::PyObject_ptr::PyObject_ptr(PyObject*, bool)’:
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c:2958:
>>> warning: suggest explicit braces to avoid ambiguous ‘else’
>>> In file included from
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c:3502:
>>> /opt/occ/inc/Interface_Check.hxx: At global scope:
>>> /opt/occ/inc/Interface_Check.hxx:184: error: expected unqualified-id
>>> before ‘)’ token
>>> In file included from
>>> /opt/occ/inc/MoniTool_DataMapNodeOfDataMapOfShapeTransient.hxx:34,
>>>                 from
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c:3576:
>>> /opt/occ/inc/TopoDS_Shape.hxx:158: error: expected unqualified-id
>>> before numeric constant
>>> /opt/occ/inc/TopoDS_Shape.hxx:161: error: expected unqualified-id
>>> before numeric constant
>>> In file included from /opt/occ/inc/TopoDS_Shape.lxx:7,
>>>                 from /opt/occ/inc/TopoDS_Shape.hxx:277,
>>>                 from
>>> /opt/occ/inc/MoniTool_DataMapNodeOfDataMapOfShapeTransient.hxx:34,
>>>                 from
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c:3576:
>>> /opt/occ/inc/TopoDS_TShape.hxx:119: error: expected unqualified-id
>>> before numeric constant
>>> /opt/occ/inc/TopoDS_TShape.hxx:122: error: expected unqualified-id
>>> before numeric constant
>>> In file included from /opt/occ/inc/TopoDS_Shape.hxx:277,
>>>                 from
>>> /opt/occ/inc/MoniTool_DataMapNodeOfDataMapOfShapeTransient.hxx:34,
>>>                 from
>>>
>>> /home/nawijn/scratch/pythonOCC/src/SWIG_src_modular_linux_darwin/STEPControl_wrap.c:3576:
>>> /opt/occ/inc/TopoDS_Shape.lxx:239: error: expected unqualified-id
>>> before numeric constant
>>> /opt/occ/inc/TopoDS_Shape.lxx:249: error: expected unqualified-id
>>> before numeric constant
>>> /opt/occ/inc/InterfaceGraphic_XWD.hxx:30: warning:
>>> ‘InterfaceGraphic_swaptest’ defined but not used
>>> error: command 'g++' failed with exit status 1
>>>
>>>
>>>
>>> Any suggestions?
>>>
>>> Marco
>>


_______________________________________________
Pythonocc-users mailing list
Pythonocc-users@gna.org
https://mail.gna.org/listinfo/pythonocc-users

Reply via email to