On Sun, Mar 22, 2009 at 2:03 PM, Arthur Magill <arthur.mag...@epfl.ch> wrote:
> Hi Jelle,
>
> That's an interesting question. You're right, many libraries on a 64-bit 
> system
> are actually 32-bit, and it is common to have both versions of some libraries
> installed. The 'standard' way to do things is to put 64 bit libraries in
> /usr/lib64 and 32 bit versions in /usr/lib, but of course OCC isn't following
> this convention!
>
> I guess pyOCC should follow how OCC has been compiled. OCC uses autoconf to
> detect a 64 bit system and adds appropriate flags. I don't know how we can 
> check
> the build flags used for OCC, but I think it is safe(ish) to assume OCC is
> compiled as 64-bit on a 64-bit system.
All compilation settings for OCC are stored in the config.log file
that will be created in the
$CASROOT ("ros") directory. For example, for my system it shows the
following for the
CXX* variables:

CXX='g++'
CXXCPP='g++ -E'
CXXCPPFLAGS=' -D_OCC64 -m64 -DNDEBUG  -DNo_Exception'
CXXDEPMODE='depmode=gcc3'
CXXFLAGS=' -DCSFDB -DOCC_CONVERT_SIGNALS -DLIN -DLININTEL -D_GNU_SOURCE=1 -O2'



We could then provide an override in the
> SCons file. Anyone who has managed to compile OCC as 32 bit on a 64 bit 
> machine
> has done that deliberately, so should be savvy enough to do the same with 
> pyOCC.
>
> What do you think?
>
>   Arthur
>
> Jelle Feringa wrote:
>>>> This effectively means that the -D_OCC64 and possible -m64
>>>> compilation
>>>> options should be enabled
>>>> on 64 bit platforms.
>>> I'll add this to the SConstruct file. I have to detect, from Python,
>>> that your processor is 64 bits.
>>
>> Ai, that would be a bad heuristic; most processors are 64 bit, but run
>> 32 bits processes mostly!
>> So, the default case should be 32 bits, if you want 64 bits, you
>> probably know how to.
>> Supporting 64 bits is a nice feature in the future, but something to
>> be done when 32 bit support is really well polished.
>>
>> -jelle
>>
>>
>> _______________________________________________
>> Pythonocc-users mailing list
>> Pythonocc-users@gna.org
>> https://mail.gna.org/listinfo/pythonocc-users
>
>
> _______________________________________________
> Pythonocc-users mailing list
> Pythonocc-users@gna.org
> https://mail.gna.org/listinfo/pythonocc-users
>

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

Reply via email to