All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Davies <busybox_mail@rovoreed.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] package: add opencv
Date: Sat, 22 Oct 2011 14:01:34 +0000	[thread overview]
Message-ID: <1319292094.2998.6.camel@ceri> (raw)
In-Reply-To: <1319130558-16555-1-git-send-email-s.martin49@gmail.com>

Hi,

I have tried your previous version (V3) and have a comment.

It seems to put over 32Mb into the target, that I think doesn't need to
be there, i.e.

[mike at ceri buildroot-2011.08]$ du -ch output/target/usr/share/opencv
56K	output/target/usr/share/opencv/lbpcascades
19M	output/target/usr/share/opencv/haarcascades
504K	output/target/usr/share/opencv/doc/vidsurv
14M	output/target/usr/share/opencv/doc
32M	output/target/usr/share/opencv
32M	total
[mike at ceri buildroot-2011.08]$ 

Certainly I don't want any documentation on my target system, and
there's 14Mb of that.

I built the system with just opencv selected, and nothing in the opencv
sub-menu selected.

Mike

      reply	other threads:[~2011-10-22 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 17:09 [Buildroot] [PATCH v4] package: add opencv Samuel Martin
2011-10-22 14:01 ` Mike Davies [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=1319292094.2998.6.camel@ceri \
    --to=busybox_mail@rovoreed.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.