From: Willy <willy@willygroup.org>
To: buildroot@busybox.net
Subject: [Buildroot] gtkmm in buildroot toolchain
Date: Fri, 27 Jan 2012 14:11:13 +0000 (UTC) [thread overview]
Message-ID: <loom.20120127T145617-861@post.gmane.org> (raw)
In-Reply-To: 20120127111928.3e881f03@skate
Thomas Petazzoni <thomas.petazzoni@...> writes:
> All options are possible of course, but option 1) is the one that will
> allow you to re-use your software as-is. We already have gtk+ support
> in Buildroot, and I don't think that gtkmm has many more dependencies
> outside of gtk+, so it should be relatively easy to integrate into
> Buildroot.
I've added gtkmm with the following .mk file (with no errors):
#####################################################
LIBGTKMM_VERSION = 2.24.0
LIBGTKMM_SOURCE = glibmm-$(LIBGTKMM_VERSION).tar.bz2
LIBGTKMM_INSTALL_STAGING = YES
LIBGTKMM_CONF_OPT = --enable-shared
LIBGTKMM_DEPENDENCIES = libglib2 host-pkg-config
$(eval $(call AUTOTARGETS))
#####################################################
the when I try to compile a gtkmm helloworld example I get this error:
#####################################################
>>> helloworldgtkmm 1.0 Building
/usr/bin/make -j4
CXX=/buildroot_folder/output/host/
usr/bin/i586-unknown-linux-uclibc-g++
LD=/buildroot_folder/output/host/usr/bin/
i586-unknown-linux-uclibc-ld -C
/buildroot_folder/output/build/helloworldgtkmm-1.0 all
make[1]: ingresso nella directory
"/buildroot_folder/output/build/helloworldgtkmm-1.0"
/buildroot_folder/output/host/usr/bin/i586-unknown-linux-uclibc-g++
helloworld.o
main.o -o helloworldgtkmm `pkg-config gtkmm-2.4 --cflags --libs`
/buildroot_folder/output/host/usr/lib/gcc/i586-unknown-linux-uclibc
/4.3.6/../../../../i586-unknown-linux-uclibc/bin/ld:
cannot find -lgtkmm-2.4
/buildroot_folder/output/host/usr/lib/gcc/i586-unknown-linux-uclibc
/4.3.6/../../../../i586-unknown-linux-uclibc/bin/ld:
cannot find -latkmm-1.6
/buildroot_folder/output/host/usr/lib/gcc/i586-unknown-linux-uclibc
/4.3.6/../../../../i586-unknown-linux-uclibc/bin/ld:
cannot find -lgdkmm-2.4
/buildroot_folder/output/host/usr/lib/gcc/i586-unknown-linux-uclibc
/4.3.6/../../../../i586-unknown-linux-uclibc/bin/ld:
cannot find -lpangomm-1.4
/buildroot_folder/output/host/usr/lib/gcc/i586-unknown-linux-uclibc
/4.3.6/../../../../i586-unknown-linux-uclibc/bin/ld:
cannot find -lcairomm-1.0
/buildroot_folder/output/host/usr/i586-unknown-linux-uclibc/
sysroot/usr/lib/libglib-2.0.so:
warning: the use of OBSOLESCENT `utime' is discouraged, use `utimes'
collect2: ld returned 1 exit status
make[1]: *** [helloworldgtkmm] Errore 1
#####################################################
Perhaps do I install those *mm library manually one by one?
> There is some documentation in the Buildroot sources, run 'make manual'
> to generate the documentation.
Thanks,
Willy
next prev parent reply other threads:[~2012-01-27 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 8:56 [Buildroot] gtkmm in buildroot toolchain Willy
2012-01-27 10:19 ` Thomas Petazzoni
2012-01-27 12:49 ` Michael S. Zick
2012-01-27 14:11 ` Willy [this message]
2012-01-27 14:27 ` Michael S. Zick
2012-01-27 14:38 ` Willy
2012-01-27 15:14 ` Thomas Petazzoni
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=loom.20120127T145617-861@post.gmane.org \
--to=willy@willygroup.org \
--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