Re: [Midnight Commander] #208: add support for building out-of-sources builds

["Ticket System" <tickets midnight-commander org>]

#208: add support for building out-of-sources builds
--------------------------+-------------------------------------------------
  Reporter:  slyfox       |       Owner:  metux                            
      Type:  enhancement  |      Status:  testing                          
  Priority:  major        |   Milestone:  4.6.3                            
 Component:  mc-core      |     Version:  4.6.1                            
Resolution:  fixed        |    Keywords:  committed-mc-4.6 committed-master
  Blocking:               |   Blockedby:                                   
--------------------------+-------------------------------------------------
Changes (by metux):

  * keywords:  vote-angel_il vote-slyfox committed-mc-4.6 committed-master
               => committed-mc-4.6 committed-master


Old description:

> 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 git://midnight-commander.org/git/mc.git
> $ ./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
> $ ../mc/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

New description:

 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 git://midnight-commander.org/git/mc.git
 $ ./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
 $ ../mc/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

 ----

 committed mc-4.6
 committed master

--

-- 
Ticket URL: <www.midnight-commander.org/ticket/208#comment:8>
Midnight Commander <www.midnight-commander.org>
Midnight Development Center