David George

Hi quick reply, the problems I found where missing include paths in the gfx makefile (linker includes) (I'm using Autotools in Eclipse), it will build, here my Eclipse console output... 17:35:25 **** Build of configuration Build (GNU) for project gfx_autotools_eclipse **** make all make all-recursive make[1]: Entering directory `/home/david/workspace/gfx_autotools_eclipse' Making all in src make[2]: Entering directory `/home/david/workspace/gfx_autotools_eclipse/src' . C Compiler Options.... arm-poky-linux-gnueabi-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 --sysroot=/opt/poky/2.1/sysroots/cortexa9hf-neon-poky-linux-gnueabi -c --sysroot=/opt/poky/2.1/sysroots/cortexa9hf-neon-poky-linux-gnueabi -g -O0 --sysroot=/opt/poky/2.1/sysroots/cortexa9hf-neon-poky-linux-gnueabi -ggdb -O0 -fomit-frame-pointer -Wall -Wextra -Wstrict-prototypes -fverbose-asm -MMD -MP -MF .build/dep/fakefile.o.d -I. -Igfx/ugfx -Igfx/ugfx/src -Igfx/ugfx/boards/base/Linux-Framebuffer -Igfx/ugfx/drivers/gdisp/framebuffer -Igfx/ugfx/demos/modules/gdisp/streaming -DGFX_USE_OS_LINUX=TRUE -DGFX_USE_OS_LINUX=TRUE fakefile.c -o .build/obj/fakefile.o . Linker Options........ arm-poky-linux-gnueabi-gcc -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard -mcpu=cortex-a9 --sysroot=/opt/poky/2.1/sysroots/cortexa9hf-neon-poky-linux-gnueabi --sysroot=/opt/poky/2.1/sysroots/cortexa9hf-neon-poky-linux-gnueabi -pthread -lrt .build/obj/fakefile.o -o .build/gfx_dmg . Compiling gfx/ugfx/src/gfx.c Compiling gfx/ugfx/src/gos/gos_linux.c Compiling gfx/ugfx/src/gdriver/gdriver.c Compiling gfx/ugfx/src/gqueue/gqueue.c Compiling gfx/ugfx/src/gdisp/gdisp.c ... Compiling gfx/ugfx/src/gtrans/gtrans.c Compiling gfx/ugfx/drivers/gdisp/framebuffer/gdisp_lld_framebuffer.c Compiling gfx/ugfx/demos/modules/gdisp/streaming/main.c Linking .build/gfx_dmg make[2]: Leaving directory `/home/david/workspace/gfx_autotools_eclipse/src' make[2]: Entering directory `/home/david/workspace/gfx_autotools_eclipse' make[2]: Leaving directory `/home/david/workspace/gfx_autotools_eclipse' make[1]: Leaving directory `/home/david/workspace/gfx_autotools_eclipse' 17:35:28 Build Finished (took 2s.570ms)

I have finally got a uGFX Autotools project to cross-build from the command line and also in Eclipse. I created a 'single' makefile (collating the various .mk files) to make debugging gmake easier. I will now try and work back to getting a build using the original uGFX makefiles - if I can. I will post the final neat solution hopefully next week. The only changed I made were in my single makefile, just re-arranging some paths and variable defines, probably because autoreconf/configure works slightly differently. No changes to any source code files.

Hi Victor - I'm attempting to do the same thing, your right its not easy. I will post the solution when I have one! Here's some info on including '3rd party' Makefiles into an Automake project : http://www.gnu.org/software/automake/manual/html_node/Third_002dParty-Makefiles.html

Hi I'm attempting something similar using Eclipse (not working yet), But I have cross-build a uGFX Demo from the command line, scp'd to the target and run successfully. Have you created your top level Makefile that basically builds the target ( you can't make from just a .mk file) Your top level Makefile will set GFXLIB etc.. You don't need a main.c file as this is supplied by the uGFX Demo directory.

Hi all - just wondered if anyone had any experience adding uGFX to an Eclipse Automake project? I'm using a Yocto ADT Toolchain. So its a cross-compile environment for a Yocto Linux custom BSP. I'm nearly there, I have basically "included" my top gfx Makefile in a new 'GNUMakefile.in' file the gfx directory. But with no examples its a slow process. Have tried the no-Makefile approach just adding gfx_mk.c etc but this doesn't seem right when there are perfectly good makefiles, and it created more build errors that I could list. I have successfully build and run the normal 'gmake' command line uGFX demo on my BSP Board using the framebuffer driver :-)