Ticket #208 (accepted enhancement) — at Version 2
add support for building out-of-sources builds
| Reported by: | slyfox | Owned by: | metux |
|---|---|---|---|
| Priority: | major | Milestone: | 4.6.2 |
| Component: | mc-core | Version: | 4.6.1 |
| Keywords: | committed-mc-4.6 committed-master | Cc: | |
| Blocked By: | Blocking: | ||
| Branch state: | Votes for changeset: |
Description (last modified by slyfox) (diff)
I'd like to run ./autogen.sh and(unsupported by autostuff?) and ./configure scripts from locations other, than source tree.
It is very convinient to run builds for various architectures/configurations against one actual source.
usage example:
$ cd /tmp
$ git clone path-to-mc
$ ./autogen.sh
$ chmod -R u-w mc/ # freeze sources (just for tests)
branch:208_out_of_tree_build (based on mc-4.6)
changeset:e3a3890a3a82500bf3e6b61d28a00f3a5e229f66
# let's craft 'mc-build'
# (and mc-build-{arm, x86_64, i386, ppc, mingw32}-{slang, charset, glib{1,2}} in real world)
# and build sources there:
$ mkdir mc-build
$ cd mc-build
$ ./configure --prefix=/tmp/mc-test/
$ make
$ make install
or at least to generate ./configure in /tmp/mc tree, but to be able t run it from other locations to have source tree untouched
