use of AutoConfig

From: Timothy Smith (tim_smith@mit.edu)
Date: Thu Oct 18 2001 - 09:13:17 EDT


Hello Simon,

        I think I can become a autoconfig convert! It really
does look very powerful, but I need to learn a bit more, can
you help me.

        First off, from you email I understand that if I want
to change a makefile, I edit

                Makefile.in

and NOT Makefile (because configure will generate
                                 a new one of these?)

        Secondly, the present Makefiles create the libBlast.so,
nsed, blast, etc. .. in the source directories, and do not
move them to the run directory. To move them one needs to
do a
                make install (I think)

        On campus this will move libBlast.so into

                        /usr/local/lib
and nsed, s, etc.. into
                        /usr/local/bin

at Bates this fails becasue users do not have write permission
there. But if, when I configure I type

        configure --prefix=/home/blast/tps/cvs/run
then libBlast.so ends up in
                        /home/blast/tps/cvs/run/lib
and nsed in
                        /home/blast/tps/cvs/run/bin

Whereas this might really be a very good solution, it is not
what people expect - they are looking for someing in the run
directory.

        question: can I edit the config.something? file
                to change this?

Thanks for all you help.

                                        Tim Smith

____________________________________________________________________
 Timothy Paul Smith Research Scientist
 MIT Bates Lab tim_smith@mit.edu
 21 Manning Rd. tel: (617) 253-9207
 Middleton, MA 01949 fax: (617) 253-9599



This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:28 EST