[BioLib-dev] GSL

[Xin Shuai]

Oh, when I pull from your libsequence branch, the file mode change from
644->755 happened again! And it seems far more files than ever changed:
mode change 100644 => 100755 .gitignore
 mode change 100644 => 100755 CMakeLists.txt
 mode change 100644 => 100755 INSTALL
 mode change 100644 => 100755 LICENSE
 mode change 100644 => 100755 PROJECTNAME
 mode change 100644 => 100755 README
 mode change 100644 => 100755 Rakefile
 mode change 100644 => 100755 TODO
 mode change 100644 => 100755 VERSION
 mode change 100644 => 100755 contrib/README.txt
 mode change 100644 => 100755 doc/APIDOCUMENTATION.txt
 mode change 100644 => 100755 doc/BUILD.txt
 mode change 100644 => 100755 doc/DEPENDENCIES.txt
 mode change 100644 => 100755 doc/DEVELOPMENT.txt
 mode change 100644 => 100755 doc/EXAMPLE.txt
 mode change 100644 => 100755 doc/GSL.txt
 mode change 100644 => 100755 doc/LAYOUT.txt
 mode change 100644 => 100755 doc/NIX.txt
 mode change 100644 => 100755 doc/OSX.txt
 mode change 100644 => 100755 doc/PACKAGING.txt
 mode change 100644 => 100755 doc/PERL.txt
 mode change 100644 => 100755 doc/PYTHON.txt
 mode change 100644 => 100755 doc/RELEASE_NOTES.txt
 mode change 100644 => 100755 doc/REPORTING_BUGS.txt
 mode change 100644 => 100755 doc/ROADMAP.txt
 mode change 100644 => 100755 doc/RUBY.txt
 mode change 100644 => 100755 doc/TESTING.txt
 mode change 100644 => 100755 doc/TROUBLESHOOTING.txt
 mode change 100644 => 100755 doc/WINDOWS.txt
 mode change 100644 => 100755 doc/doxygen/Doxyfile
 mode change 100644 => 100755 doc/doxygen/mainpage.txt
 mode change 100644 => 100755 doc/examples/c/CMakeLists.txt
...
...

...

To my surprise, the same problem occurred again and again. If I try to
modify them one by one like cmake-support, too much should be done this
time.

On Mon, Aug 10, 2009 at 5:01 AM, Pjotr Prins <pjotr.public14 at thebird.nl>wrote:

> Hi Xin,
>
> On Fri, Aug 07, 2009 at 04:14:29PM -0400, Xin Shuai wrote:
> > I have already modified related .cmake files and tested it. It looked
> fine.If
> > only the problem of my last email is solved, I think I can update the
> > cmake-support submodule.
>
> Good job :-). I can build libsequence and compile Python bindings
> now. Cool stuff. Now the final step before merging into
> release_candidate. After updating from my tree:
>
>  git pull pjotr libsequence
>  git submodule update
>
> add a working 'integration' test to the Python module. When you do:
>
>  cd src/mappings/swig/python/libsequence
>  cmake .
>  make
>  make test
>
> you'll see   1/  1 Testing TestPythonlibsequence         ***Failed
>
> the output is in Testing/Temporary/LastTest.log.
>
> Currently ../test/test_libsequence.py consists of your doctests. They
> are bound to be elaborate. A biolib integration test merely makes sure
> the build system did not fail - so it usually has a few simple tests.
>
> Rename your current doctest to ../test/doctest_libsequence.py
>
> and create a new short test (see test_example.py) that confirms the
> libraries are linked together and the mapping just works. Same for
> the Perl module.
>
> Once that test passes I'll merge into release_candidate so Mark (and
> perhaps others) can start testing.
>
> Pj.
>
> P.S. I had to revert some changes in cmake-support. Not sure why you
> changed those, but I think this is correct.
>
>


-- 
Xin Shuai (David)
PhD of Complex System in School of Informatics
Indiana University Bloomington
812-606-8019