mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] extract tarballs with no toplevel directory
Date: Mon, 4 Mar 2013 14:35:45 +0100	[thread overview]
Message-ID: <20130304133545.GR5360@pengutronix.de> (raw)
In-Reply-To: <CAMwGMjy=uKXqbqPRy2Jmf5Ku+YkNg1sWn0PeT8Y6Czziq3bWrQ@mail.gmail.com>

On Thu, Feb 28, 2013 at 05:52:39PM -0500, Jon Ringle wrote:
> Most source tarballs have a top level directory in the form of
> package-version, but I've run into one that doesn't conform to this
> standard practice.
> I'm trying to build a .make file for pugixml-1.2 (
> http://pugixml.googlecode.com/files/pugixml-1.2.tar.gz), but there is no
> directory pugixml-1.2/ as the toplevel directory. Instead everything is in
> the ./ directory that you would expect to be in a pugixml-1.2/ directory.
> When ptxdist extracts it, it seems to find all the subdirectories that are
> at the top level, and puts them all together in a pugixml-1.2/ directory
> that it has created, which changes the file/directory structure that was
> originally in the tar ball to begin with, and the source does not build.
> 
> How can I solve this?

Take a look at rules/ckermit.make. This package has the same problem. You
just need to set:
<PKG>_STRIP_LEVEL	:= 0

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2013-03-04 13:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-28 22:52 Jon Ringle
2013-03-04 13:35 ` Michael Olbrich [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130304133545.GR5360@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox