Greeaintgs All,
I am attempting to cross-compile DirectFB 1.1.1 for an ARM target
environment. I am using the following "build" script:
----------
export
AR=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_uclibc
-ar
export
AS=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_uclibc
-as
export
CPP=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_uclib
c-cpp
export
CC=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_uclibc
-gcc
export
GCOV=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_ucli
bc-gcov
export
GPROF=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_ucl
ibc-gprof
export
LD=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_uclibc
-ld
export
NM=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_uclibc
-nm
export
OBJCOPY=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_u
clibc-objcopy
export
OBJDUMP=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_u
clibc-objdump
export
RANLIB=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_uc
libc-ranlib
export
READELF=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_u
clibc-readelf
export
SIZE=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_ucli
bc-size
export
STRINGS=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_u
clibc-strings
export
STRIP=/vob/ccm_firmware/ip_g4/infra/tools/v6_le_uclibc/bin/arm_v6_le_ucl
ibc-strip
./configure --build=i686-linux --target=arm-linux --host=arm-linux \
--prefix=/tmp/rhilding/target_root \
--disable-x11 --disable-voodoo \
--disable-mmx --disable-sse --disable-sdl \
--disable-gif --disable-video4linux --disable-video4linux2 \
--enable-fbdev --disable-freetype --with-tests \
--with-gfxdrivers=none --with-inputdrivers=linuxinput
have_linux=yes
----------
This will configure the makefiles correctly and will make without
errors. The problem comes during the runtime phase on the actual target.
If I execute the "dfbinfo" command I get the following output:
=======================| DirectFB 1.1.1 |=======================
(c) 2001-2007 The DirectFB Organization (directfb.org)
(c) 2000-2004 Convergence (integrated media) GmbH
------------------------------------------------------------
(*) DirectFB/Core: Single Application Core. (2008-01-29 17:35)
(!) Direct/Modules: Could not open module directory
`//tmp/rhilding/target_root/lib/directfb-1.1-0/systems'!
--> No such file or directory
(!) DirectFB/core/system: No system found!
(#) DirectFBError [DirectFBCreate() failed]: No (suitable)
implementation found!
In essence, it appears that during the "make install" phase of
cross-compiling DirectFB, the libraries are being hard-coded to look in
the install path for the modules directory. However, since I'm
cross-compiling, the install path is not the actual target path, so I
need a way to force the libraries to look for the modules directory in a
different path from the install path...
Any help with this issue would be greatly appreciated!
Thanks,
-Robert Hildinger
_______________________________________________
directfb-dev mailing list
directfb-dev@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
