Category:How to - Build helloworld - Revision history

Ashcharles at 21:37, 1 April 2016

2016-04-01T21:37:59Z

Sellis: Fixed some whitespace

2010-08-14T14:08:00Z

Fixed some whitespace

Sellis: Update for latest OE toolchain changes

2010-08-14T14:01:13Z

Update for latest OE toolchain changes

Sellis: linux-libc-headers already gets built with gcc-cross. Bad example.

2010-07-21T12:32:42Z

linux-libc-headers already gets built with gcc-cross. Bad example.

Sellis: wording

2010-06-14T09:45:08Z

wording

Sellis: Be explicit that the Hello World recipe link is an alternative to this page.

2010-06-14T09:22:10Z

Be explicit that the Hello World recipe link is an alternative to this page.

Sellis: Seems this was confusing people combining lib path with libs. Just show lib path now.

2010-04-03T16:35:05Z

Seems this was confusing people combining lib path with libs. Just show lib path now.

Ashcharles at 22:40, 3 March 2010

2010-03-03T22:40:58Z

Sellis: Added a network boot link

2010-01-14T18:39:21Z

Added a network boot link

Sellis: Added gcc-cross instructions

2010-01-04T23:09:56Z

Added gcc-cross instructions

@@ Line 1: / Line 1: @@
 ==Overview==
-What follows is a description for building C programs on a workstation using the cross-build tools of [http://wiki.openembedded.net/index.php/Main_Page OpenEmbedded], but NOT USING the bitbake/recipe framework.
+What follows is a description for building C programs on a workstation using the cross-build tools of Yocto, but NOT USING the bitbake/recipe framework.
 For an alternative method USING the bitbake/recipe framework, a series of sample recipes can be found [[HelloWorld Examples | here]].
@@ Line 7: / Line 7: @@
 ==Setup==
-Follow the instructions for [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html setting up a build environment] to get the cross-build tools correctly installed.
+Follow the instructions for [https://github.com/gumstix/yocto-manifest/wiki setting up a build environment] to get the cross-build tools correctly installed.
 The tools are built under the TMPDIR directory declared in ${OVEROTOP}/build/conf/site.conf.
@@ Line 71: / Line 71: @@
 . If you have a network connection to the overo, use scp.
 ==Only the Tools==

@@ Line 30: / Line 30: @@
   OETMP = ${OVEROTOP}/tmp
   # OE prior to around 30July2010
   # TOOLDIR = ${OETMP}/cross/armv7a/bin
   # STAGEDIR = ${OETMP}/staging/armv7a-angstrom-linux-gnueabi/usr
-−
-  # OE after 30July2010, the multi-machine safe toolchain patches
+  # OE after 30July2010
   TOOLDIR = ${OETMP}/sysroots/`uname -m`-linux/usr/armv7a/bin
   STAGEDIR = ${OETMP}/sysroots/armv7a-angstrom-linux-gnueabi/usr

@@ Line 30: / Line 30: @@
   OETMP = ${OVEROTOP}/tmp
-  TOOLDIR = ${OETMP}/cross/armv7a/bin
+  # OE prior to around 30July2010
+ # TOOLDIR = ${OETMP}/cross/armv7a/bin
-  STAGEDIR = ${OETMP}/staging/armv7a-angstrom-linux-gnueabi/usr
+  # STAGEDIR = ${OETMP}/staging/armv7a-angstrom-linux-gnueabi/usr
   CC = ${TOOLDIR}/arm-angstrom-linux-gnueabi-gcc

← Older revision		Revision as of 12:32, 21 July 2010
Line 77:		Line 77:

	You can use OE to selectively build additional cross-compiled libraries as needed. Look around in the OE recipes folder.		You can use OE to selectively build additional cross-compiled libraries as needed. Look around in the OE recipes folder.
−
−	~~For example, if you needed the kernel headers too...~~
−
−	~~bitbake linux-libc-headers~~

	If you build a complete image, then most of the cross-build tools and libraries will get installed as as side-effect. That is probably the easiest way to setup your workstation the first time.		If you build a complete image, then most of the cross-build tools and libraries will get installed as as side-effect. That is probably the easiest way to setup your workstation the first time.

@@ Line 58: / Line 58: @@
 ==Distribute==
-Copy the resulting target executable to the overo.
+After building with make, copy the resulting target executable to the overo.
 . If you are using [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Creating-a-bootable-microSD-card/111.html a microSD card], copy your executable to the rootfs before you unmount it in the final step.

@@ Line 1: / Line 1: @@
 ==Overview==
-What follows is a description for building C programs on a workstation using the cross-build tools of [http://wiki.openembedded.net/index.php/Main_Page OpenEmbedded], but not using the bitbake/recipe framework.
+What follows is a description for building C programs on a workstation using the cross-build tools of [http://wiki.openembedded.net/index.php/Main_Page OpenEmbedded], but NOT USING the bitbake/recipe framework.
-A series of sample recipes can be found [[HelloWorld Examples | here]].
+For an alternative method USING the bitbake/recipe framework, a series of sample recipes can be found [[HelloWorld Examples | here]].
 ==Setup==
 Follow the instructions for [http://www.gumstix.net/Setup-and-Programming/view/Overo-Setup-and-Programming/Setting-up-a-build-environment/111.html setting up a build environment] to get the cross-build tools correctly installed.
 The tools are built under the TMPDIR directory declared in ${OVEROTOP}/build/conf/site.conf.
@@ Line 26: / Line 13: @@
 TMPDIR defaults to ${OVEROTOP}/tmp, but you can point it somewhere else.
 ==Makefile==
-Create a makefile for your project pointing to the cross-build toolchain.
+After you have built an image, the cross-tools will be installed on your workstation.
-Here is a simple one for helloworld.
+You can now create a standard makefile for your project pointing to this cross-build toolchain.
   # Makefile for building with the OE cross tools
@@ Line 77: / Line 64: @@
 . If you have a network connection to the overo, use scp.
-. If you have a kermit console session, use the kermit SEND command.
+. If you are doing a [http://www.gumstix.net/wiki/index.php?title=Category:How_to_-_Network_Boot network boot] then copy the executable directly to the nfs exported root filesystem the gumstix is using on the workstation.
-. If you are doing a [http://www.gumstix.net/wiki/index.php?title=Category:How_to_-_Network_Boot network boot] then copy the executable directly to the nfs exported root filesystem the gumstix is using on the workstation.
+If you build a complete image, then most of the cross-build tools and libraries will get installed as as side-effect. That is probably the easiest way to setup your workstation the first time.

@@ Line 54: / Line 54: @@
   INCDIR = ${STAGEDIR}/include
-−
- LIBS = -L ${LIBDIR}
-−
   TARGET = helloworld
@@ Line 63: / Line 61: @@
   ${TARGET} : $(OBJS)
-          ${CC} ${CFLAGS} ${OBJS} ${LIBS} -o ${TARGET}
+          ${CC} ${CFLAGS} ${OBJS} -L ${LIBDIR} -o ${TARGET}
   helloworld.o: helloworld.c

← Older revision		Revision as of 22:40, 3 March 2010
Line 2:		Line 2:

	What follows is a description for building C programs on a workstation using the cross-build tools of [http://wiki.openembedded.net/index.php/Main_Page OpenEmbedded], but not using the bitbake/recipe framework.		What follows is a description for building C programs on a workstation using the cross-build tools of [http://wiki.openembedded.net/index.php/Main_Page OpenEmbedded], but not using the bitbake/recipe framework.
		+
		+	A series of sample recipes can be found [[HelloWorld Examples \| here]].

	==Setup==		==Setup==

← Older revision		Revision as of 18:39, 14 January 2010
Line 78:		Line 78:

	3. If you have a kermit console session, use the kermit SEND command.		3. If you have a kermit console session, use the kermit SEND command.
		+
		+	4. If you are doing a [http://www.gumstix.net/wiki/index.php?title=Category:How_to_-_Network_Boot network boot] then copy the executable directly to the nfs exported root filesystem the gumstix is using on the workstation.

← Older revision		Revision as of 23:09, 4 January 2010
Line 8:		Line 8:

	While you don't necessarily need to build a complete image to get the cross-tools for a C program, as a practical matter, successfully building an image is a good test that the cross-tools are correctly installed.		While you don't necessarily need to build a complete image to get the cross-tools for a C program, as a practical matter, successfully building an image is a good test that the cross-tools are correctly installed.
		+
		+	If you only want to cross compile a C program without third-party dependencies, then you can build just the gcc-cross recipe.
		+
		+	bitbake gcc-cross
		+
		+	And if you need the kernel headers too...
		+
		+	bitbake linux-libc-headers
		+
		+	There is no time lost building only these recipes, since both are dependencies of a full image.
		+

	The tools are built under the TMPDIR directory declared in ${OVEROTOP}/build/conf/site.conf.		The tools are built under the TMPDIR directory declared in ${OVEROTOP}/build/conf/site.conf.