2009/7/29 Sébastien Ramage <sram...@poifindus.com>

>  Hi all !
>

Hi Sébastien,


>
>
> After 7441 seconds of compiling it finally succeeded !
>

Woow, it is quite long. What is your configuration ?(processor, RAM) Which
compiler did you use (MSVC version?).


>
> After few tests pythonocc wo0.2 seems to work on python 2.6 under windows
> xp :)
>

Cool. I must now work on a set of unit tests.


>
> I can provide the windows installer if needed.
>

The best way is to use the wiki.  You can modify the Windows entry (
http://www.pythonocc.org/wiki/index.php/InstallWindows) and insert a link to
your personal webserver (it's not possible to upload .exe files to the
Wiki). Just care to mention that it is an 'unofficial' binary distro since I
did not tested it yet.


>
> Now I will try with the svn version.
>

You don't have to rebuild the SWIG files. Just use the ones that are
available from the subversion repo.


>
>
> Thank you Thomas !
>

You're welcome.

Thomas


>
> Sébastien Ramage
> Service informatiquesram...@poifindus.com
> 04 74 06 45 39
>
> Ets JANIN
> 115, rue de la république
> 69823 Belleville Cedex
> Tel : 04 74 06 45 20
> Fax : 04 74 66 11 76
>
>
>
> Thomas Paviot a écrit :
>
> Hi Sébastien,
>
> Happy that this hint helped you. When the compilation if finished:
> python setup.py build -cmsvc install
>
> And you can check if the samples run.
>
> If you want to generate a self-executable installer for Windows:
> python setup.py build -cmsvc bdist_wininst
> In the /dist directory, you'll find the .exe file.
>
> I'm not sure that it's useful to spend time on the 0.2 release. You should
> update to the latest revision of pythonOCC from the subversion repository
> (many many changes were made during the last few weeks). The 0.3 release is
> about to be available. It would be great if you could provide an installer
> for Python2.6 on Windows. I will first check that all tests successfully
> pass before making it publicly available.
>
> Thanks for your help and enjoy pythonOCC,
>
> Thomas
>
> 2009/7/28 Sébastien Ramage <sram...@poifindus.com>
>
>> oh it works ! the compilation is started, I hope it will compile fine.
>>
>> Really thank you for your help.
>> If it compile correctly can I send you the binary in order to put it on
>> the website ?
>>
>> Sébastien Ramage
>> Service informatiquesram...@poifindus.com
>> 04 74 06 45 39
>>
>> Ets JANIN
>> 115, rue de la république
>> 69823 Belleville Cedex
>> Tel : 04 74 06 45 20
>> Fax : 04 74 66 11 76
>>
>>
>>
>>
>>  Thomas Paviot a écrit :
>>
>>
>>
>> 2009/7/28 Sébastien Ramage <sram...@poifindus.com>
>>
>>> After commenting the line related to NIS in the Modules.py script, the
>>> swig generation works fine but after I get the same error during the
>>> build.
>>>
>>> I really don't know what's happen, I'm not a c++ guru...
>>
>>
>> The traceback tells that the acosh function is defined twice. Here is a
>> comment extracted from the pymath.h header file (
>> http://svn.python.org/view/python/branches/release26-maint/Include/pymath.h?view=markup
>> ):
>>
>>  /* Python provides implementations for copysign, acosh, asinh, atanh,
>> * log1p and hypot in Python/pymath.c just in case your math library doesn't
>>
>> * provide the functions.
>> *
>> *Note: PC/pyconfig.h defines copysign as _copysign
>> */**A solution is perhaps to say python to use the default acosh and asinh 
>> functions by defining the HAVE_ACOSH, HAVE_ASINH and HAVE_ATANH macros.
>>
>>
>> In order to to that, edit 'environment.py' script and look for the following 
>> lines:DEFINE_MACROS = [('WNT', None),('WIN32',None),\
>> ('_WINDOWS',None),('CSFDB',None),\('__PYTHONOCC_MAXINT__',sys.maxint)]
>>
>>
>> And replace it with the lines:DEFINE_MACROS = [('WNT', None),('WIN32',None),\
>> ('HAVE_ACOSH',None),('HAVE_ASINH',None),('HAVE_ATANH',None),\('_WINDOWS',None),('CSFDB',None),\
>> ('__PYTHONOCC_MAXINT__',sys.maxint)]
>>
>> Then restart the compilation process:
>>
>> python setup.py build -cmsvc
>>
>> Let me know about the results you get.
>>
>> Cheers,
>> Thomas
>>
>>
>>   ------------------------------
>>
>> _______________________________________________
>> Pythonocc-users mailing 
>> listpythonocc-us...@gna.orghttps://mail.gna.org/listinfo/pythonocc-users
>>
>>
>> _______________________________________________
>> Pythonocc-users mailing list
>> Pythonocc-users@gna.org
>> https://mail.gna.org/listinfo/pythonocc-users
>>
>>
> ------------------------------
>
> _______________________________________________
> Pythonocc-users mailing 
> listpythonocc-us...@gna.orghttps://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