From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Compile Crypto++ package
Date: Wed, 4 Mar 2015 11:37:28 +0100 [thread overview]
Message-ID: <20150304113728.4dfd8bea@free-electrons.com> (raw)
In-Reply-To: <CAJpGAeFK15Vrznw7HLDSrACBHwRKLGi8freygbFcfPaA5BEpTw@mail.gmail.com>
Hello,
On Wed, 4 Mar 2015 11:33:59 +0800, hardik gohil wrote:
> I am using buildroot to compile packages for MIPS architecture till now.
>
> I want to compile Crypto++ which is not available in Buildroot-2013.02.
>
> I don't want to use libgcrypt which is available.
>
> Crypto++ uses GNUmakefile method but not autoconf (./configure) to compile.
>
> Is it possible to Integrate this into buildroot or i need to compile
> separately outside by setting all the paths.
Of course it is possible to integrate this package in Buildroot. You
seem to believe that only autoconf-based packages can be supported but
that's not the case: autoconf/automake based packages are supported
using the autotools-package infrastructure, but we also support CMake,
Perl, Python, Luarocks, and other types of packages.
And for packages having a custom build system such as a manual makefile
(which is the case of Crypto++), we have the generic-package
infrastructure.
> Help me?
Please read the Buildroot documentation:
http://buildroot.org/downloads/manual/manual.html#adding-packages. And
specifically the part about generic-package:
http://buildroot.org/downloads/manual/manual.html#_infrastructure_for_packages_with_specific_build_systems.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-03-04 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 3:33 [Buildroot] Compile Crypto++ package hardik gohil
2015-03-04 10:37 ` Thomas Petazzoni [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=20150304113728.4dfd8bea@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox