what is the working directory for configure/compile/install tasks?

what is the working directory for configure/compile/install tasks?

[Robert P. J. Day]

  this is such a simple question, i'm kind of embarrassed to be asking
it.

  i've been handed a simple example of Makefile-based source to turn
into a recipe, and the configure/build process is absolutely
straightforward -- top-level "configure" and "Makefile" files to be
run -- to the point where i can simply define my own do_configure(),
do_compile(), etc. tasks.

  i'm aware that most tasks are defined in terms of commands that
explicitly use directory references with "S", "B", "D", WORKDIR, and
so on and so on. but if i want to define a do_configure() task that
does nothing more than invokes the top-level "configure" script, how
would i refer to it?

  i'm reading the YP dev manual, and it'a just a bit vague on this
topic, unless i managed to miss it.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is the working directory for configure/compile/install tasks?

[Alexander Kanavin]

On 01/27/2017 02:44 PM, Robert P. J. Day wrote:
>

>   i've been handed a simple example of Makefile-based source to turn
> into a recipe, and the configure/build process is absolutely
> straightforward -- top-level "configure" and "Makefile" files to be
> run -- to the point where i can simply define my own do_configure(),
> do_compile(), etc. tasks.

It's not entirely clear, but is the source GNU autotools based? Can you 
provide a link to it, so we can see what configure actually does?

Alex

Re: what is the working directory for configure/compile/install tasks?

[Burton, Ross]

[-- Attachment #1: Type: text/plain, Size: 725 bytes --]

On 27 January 2017 at 12:44, Robert P. J. Day <rpjday@crashcourse.ca> wrote:

>   i've been handed a simple example of Makefile-based source to turn
> into a recipe, and the configure/build process is absolutely
> straightforward -- top-level "configure" and "Makefile" files to be
> run -- to the point where i can simply define my own do_configure(),
> do_compile(), etc. tasks.
>

$ git grep \\[dirs\\] meta/classes/base.bbclass
meta/classes/base.bbclass:do_fetch[dirs] = "${DL_DIR}"
meta/classes/base.bbclass:do_unpack[dirs] = "${WORKDIR}"
meta/classes/base.bbclass:do_configure[dirs] = "${B}"
meta/classes/base.bbclass:do_compile[dirs] = "${B}"
meta/classes/base.bbclass:do_install[dirs] = "${B}"

Ross

[-- Attachment #2: Type: text/html, Size: 1476 bytes --]

Re: what is the working directory for configure/compile/install tasks?

[Robert P. J. Day]

[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]

On Fri, 27 Jan 2017, Burton, Ross wrote:

>
> On 27 January 2017 at 12:44, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>         i've been handed a simple example of Makefile-based source to turn
>       into a recipe, and the configure/build process is absolutely
>       straightforward -- top-level "configure" and "Makefile" files to be
>       run -- to the point where i can simply define my own do_configure(),
>       do_compile(), etc. tasks.
>
>
> $ git grep \\[dirs\\] meta/classes/base.bbclass
> meta/classes/base.bbclass:do_fetch[dirs] = "${DL_DIR}"
> meta/classes/base.bbclass:do_unpack[dirs] = "${WORKDIR}"
> meta/classes/base.bbclass:do_configure[dirs] = "${B}"
> meta/classes/base.bbclass:do_compile[dirs] = "${B}"
> meta/classes/base.bbclass:do_install[dirs] = "${B}"

  *sigh* ... i really should have known that.

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Re: what is the working directory for configure/compile/install tasks?

[Khem Raj]

On 1/27/17 4:44 AM, Robert P. J. Day wrote:
>   i'm aware that most tasks are defined in terms of commands that
> explicitly use directory references with "S", "B", "D", WORKDIR, and
> so on and so on. but if i want to define a do_configure() task that
> does nothing more than invokes the top-level "configure" script, how
> would i refer to it?
> 

do_configure () {
	${S}/configure
}