I don't know enough about automake/configure stuff to comment on that strategy. I apologize that I have not had more time to troubleshoot the difficulties I've been having this week. Since I was able to compile omeis standalone, but am not able to compile it as part of the OME installation, do you have any advice on the next step for me to try? I should have time on Monday or Tuesday to work on it some more. I particularly want to avoid any potential solution being deployed prematurely, or unnecessarily taking up your time.
<br><br>-Curtis<br><br><div><span class="gmail_quote">On 5/5/06, <b class="gmail_sendername">Ilya Goldberg</b> <<a href="mailto:igg@nih.gov">igg@nih.gov</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The resolution of this seems to be to include <a href="http://Makefile.in">Makefile.in</a> files in<br>the distribution+CVS. They are included when doing "make dist" and<br>are left in place when doing "make distclean".
<br>The installer logic should attempt "make", then "configure" if "make"<br>failis. This will make it faster re-running it for one thing. C<br>developers are then responsible for running autogen.sh
and updating<br>the resulting Makefile.in(s), configure, and other stuff that remains<br>after "make distclean".<br><br>Or, is this totally stupid?<br><br>-Ilya<br></blockquote></div><br>