How To Compile Everything: Difference between revisions
Content added Content deleted
imported>Geofft No edit summary |
imported>Geofft No edit summary |
||
| Line 30: | Line 30: | ||
** To set a prefix, run <code>./configure --prefix=''/home/geofft''</code>. |
** To set a prefix, run <code>./configure --prefix=''/home/geofft''</code>. |
||
** Running configure will error out if it requires something you don't have installed. But check its output, as it might be skipping something optional but useful, that you should have installed. |
** Running configure will error out if it requires something you don't have installed. But check its output, as it might be skipping something optional but useful, that you should have installed. |
||
* Is there a <code>autogen.sh</code>? |
* Is there a <code>autogen.sh</code>, but no <code>configure</code> (with no extension)? Sometimes this file is called <code>bootstrap</code> or something. |
||
** Make sure you have autoconf and automake installed. |
** Make sure you have autoconf and automake installed. |
||
** Run <code>./autogen.sh</code>, then start from the <code>configure</code> decision branch. |
** Run <code>./autogen.sh</code>, then start from the <code>configure</code> decision branch. |
||
** Rarely, <code>autogen.sh</code> will also run <code>configure</code> for you; if you want to pass options, you can either rerun <code>./configure</code> yourself, or pass them to <code>./autogen.sh</code>. |
** Rarely, <code>autogen.sh</code> will also run <code>configure</code> for you; if you want to pass options, you can either rerun <code>./configure</code> yourself, or pass them to <code>./autogen.sh</code>. |
||
* Is there a <code>configure.ac</code> or <code>configure.in</code>, but no <code>autogen.sh</code>? |
* Is there a <code>configure.ac</code> or <code>configure.in</code>, but no <code>autogen.sh</code>? (If there is one, prefer that) |
||
** Make sure you have autoconf and automake installed. |
** Make sure you have autoconf and automake installed. |
||
** Run <code>autoreconf -fvi</code>, then start from the <code>configure</code> decision branch. |
** Run <code>autoreconf -fvi</code>, then start from the <code>configure</code> decision branch. |
||
=== Java === |
|||
* Is there a <code>build.xml</code>? |
|||
** Are there files with Android-y names? |
|||
*** Install the Android utilities, then run <code>android update project</code> so that your paths to the Android SDK are set |
|||
** Run <code>ant build</code> |
|||
* Is there a <code>pom.xml</code>? |
|||
** Curse at Maven a bit, then run <code>mvn compile</code> and hope for the best |
|||
** Consider using Eclipse |
|||
* Sometimes Java programs are servlets, which you can tell by, like, <code>WEB-INF</code> directories or <code>web.xml</code> files running around |
|||
** You'll want a "servlet container" like Tomcat or Jetty, which is a fancy word for a web server that runs Java servlets |
|||
** Jetty can run standalone, with no advance setup, and there's often a Maven target for that |
|||
=== Other things === |
=== Other things === |
||