Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The <code>configure</code> file is generated through autoconf from a <code>configure.ac</code> file. Here's my minimal template for <code>configure.ac</code> with C++:</p> <pre><code>dnl Minimal autoconf version supported. 2.60 is quite a good bias. AC_PREREQ([2.60]) dnl Set program name and version. It will be used in output, dnl and then passed to program as #define PACKAGE_NAME and PACKAGE_VERSION. AC_INIT([program-name], [program-version]) dnl Keep helpers in build-aux/ subdirectory to not leave too much junk. AC_CONFIG_AUX_DIR([build-aux]) dnl Enable generation of Makefile.in by automake. dnl Minimal automake version: 1.6 (another good bias IMO). dnl foreign = disable GNU rules requiring files like NEWS, README etc. dnl dist-bzip2 = generate .tar.bz2 archives by default (make dist). dnl subdir-objects = keep .o files in subdirectories with source files. AM_INIT_AUTOMAKE([1.6 foreign dist-bzip2 subdir-objects]) dnl Enable silent rules if supported (i.e. CC something.o instead of gcc call) m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES]) dnl Find a good C++ compiler. AC_PROG_CXX dnl Write #defines to config.h file. dnl You need to generate config.h.in, for example using autoheader. AC_CONFIG_HEADERS([config.h]) dnl Generate Makefile from Makefile.in. AC_CONFIG_FILES([Makefile]) dnl This generates fore-mentioned files. AC_OUTPUT </code></pre> <p>The <code>dnl</code> lines are comments (explanations) for you, you can remove them from your file.</p> <p>It assumes you are using automake to generate the <code>Makefile</code> as well. If you don't want that, you need to prepare a <code>Makefile.in</code> by hand (and remove the <code>AM_INIT_AUTOMAKE</code> line).</p> <p>The configuration results will be written to <code>config.h</code>. You usually include it like:</p> <pre><code>#ifdef HAVE_CONFIG_H # include "config.h" #endif </code></pre> <p>And my template for <code>Makefile.am</code> (which is used by automake):</p> <pre><code># Programs which will be compiled and installed to /usr/bin (or similar). bin_PROGRAMS = myprogram # Source files for program 'myprogram'. myprogram_SOURCES = src/f1.cxx src/f2.cxx # Linked libraries for program 'myprogram'. myprogram_LDADD = -llib1 -llib2 </code></pre> <p>After creating those two templates, you usually run <code>autoreconf -vi</code> rather than random tools yourself. This is going to guess what you need and run it.</p> <p>Feel free to let you know if you need something more, I'll be happy to explain.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload