Hello James,

I have used the O=build_output_dir option and it builds the debian package in the curdir.
It does solve the problem, I need to test and see if the debian package bult in this way functionally works.
But, still I think your changes hold good as it creates a debian package in the specified directory than the current behavior of creating a
debian package in the parent directory.


Thanks and Regards,
Deepti.

On Thu, Sep 22, 2011 at 9:36 PM, James Westby <james.westby@linaro.org> wrote:
Hi Deepti,

It's been suggested that this could be achieved instead by using the
standard "O" variable to suggest an output dir.

Running

 make deb-pkg O=build/

would use build/ as the build directory, and then put the resulting
files in the current working directory.

I haven't tested it, but if it works would it solve your problem?

Thanks,

James


On Tue, 20 Sep 2011 17:30:46 -0400, James Westby <james.westby@linaro.org> wrote:
> Allow the caller to set the output directory for the deb packages
> using an environment variable.
> ---
>  scripts/package/builddeb |    6 +++++-
>  1 files changed, 5 insertions(+), 1 deletions(-)
>
> diff --git a/scripts/package/builddeb b/scripts/package/builddeb
> index ea33db3..dea0190 100644
> --- a/scripts/package/builddeb
> +++ b/scripts/package/builddeb
> @@ -12,6 +12,10 @@
>
>  set -e
>
> +if [ -z $DEB_OUT_DIR ]; then
> +   $DEB_OUT_DIR=".."
> +fi
> +
>  # Attempt to find the correct Debian architecture
>  forcearch=""
>  debarch=""
> @@ -64,7 +68,7 @@ create_package() {
>
>       # Create the package
>       dpkg-gencontrol -isp $forcearch -p$pname -P"$pdir"
> -     dpkg --build "$pdir" ..
> +     dpkg --build "$pdir" $DEB_OUT_DIR
>  }
>
>  # Some variables and settings used throughout the script
> --
> 1.7.5.4
>