To compile it on your platform you must first compile the extensions
by running this script:
http://code.google.com/p/pywafo/source/browse/trunk/pywafo/build_all.py
That script walks through the subfolders of wafo/source and build the
extensions by running these build scripts:
http://code.google.com/p/pywafo/source/browse/trunk/pywafo/src/wafo/source/c_codes/build_all.py
http://code.google.com/p/pywafo/source/browse/trunk/pywafo/src/wafo/source/rind2007/build_all.py
http://code.google.com/p/pywafo/source/browse/trunk/pywafo/src/wafo/source/mvnprd/build_all.py
http://code.google.com/p/pywafo/source/browse/trunk/pywafo/src/wafo/source/mvn/build_all.py
and then move the compiled extensions to .../src/wafo.
Now you are ready to install pywafo using
http://code.google.com/p/pywafo/source/browse/trunk/pywafo/setup.py
by running:
python setup.py install
Then you may test the tutorialscripts found here:
http://code.google.com/p/pywafo/source/browse/trunk/pywafo/src/wafo/doc/tutorial_scripts/chapter1.py
I have not considered integrating WAFO with sagemath. The plan is to
make a stable standalone toolbox that covers most of the functionality
found in WAFO for matlab.
Then who knows what the future will bring.
Best regards Per A.
> --
> Du mottar denne meldingen fordi du abonnerer på Google-gruppen «wafo».
> Hvis du vil legge inn en melding i denne gruppen, kan du sende e-post til wa...@googlegroups.com.
> Hvis du vil avslutte abonnementet på denne gruppen, sender du en e-post til wafo+uns...@googlegroups.com.
> Hvis du vil ha flere alternativer, kan du besøke gruppen på http://groups.google.com/group/wafo?hl=no.
>
>
I just made a commit on the google code page (r77) with some very modest changes
so the necessary source files can also be compiled on Linux (included
.so files are
compiled on Ubuntu 10.04 64bit system).
Building these source files is not yet included in the general
build_all.py script.
Currently, on linux the f2py is called via f2py2.6, which is not a very robust
approach, since on different systems it might called differently.
Any suggestions on making this approach more generic on Linux is welcome.
Regards,
David
On 2 February 2011 11:39, Per Andreas Brodtkorb
correction: building these source files is not included in the
setup.py build (previously mistaken with build_all.py), which was also
noted by Per in the previous mails.
On 2 February 2011 18:11, Per Andreas Brodtkorb
<per.andrea...@gmail.com> wrote:
> This is great. Thank you.
>
> Per A.
On 2 February 2011 19:11, Per Andreas Brodtkorb