aboutsummaryrefslogtreecommitdiffstats
path: root/FAQ
blob: 298c5a8d750731c82ce2818b6ae9a499e97ebdf7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
FAQ
===

Q. How do I create a recipe to build a Mono/.NET application within Yocto/OpenEmbedded

See wiki instructions

https://wiki.yoctoproject.org/wiki/Building_and_running_embedded_Linux_.NET_applications_from_first_principles

Also see mono-hellowworld example recipes

http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/recipes-mono/mono-helloworld

- mono-helloworld is based on the Mono example, mono-skel, and provides files needed to build with autotools
- mono-helloworld-xbuild uses a Visual Studio solution and project files with Mono xbuild

Q. How do I set the version of Mono that I wish to build?

A. Modify your conf/local.conf file to include the following

For Mono 3.2.8

PREFERRED_VERSION_mono = "3.2.8"
PREFERRED_VERSION_mono-native = "3.2.8"

For Mono 3.4.0 

PREFERRED_VERSION_mono = "3.4.0"
PREFERRED_VERSION_mono-native = "3.4.0"

Q. How do I include Mono in an image?

A. Ideally you would wish to create an image recipe that inherits a base image recipe,
or .bbappends to a base image recipe, possibly in a new layer.

The core-image-mono in recipes-mono/images shows how to do this. In core-image-mono.bb
we require core-image-sato (i.e. base our mono image on the sato image) and in addition
we require core-image-mono.inc. In the include file we add Mono to the output image

IMAGE_INSTALL += "libgdiplus mono mono-helloworld"

So you can modify your own image recipe(s) in this manner. However in the simplest case 
for testing you can add the following to your conf/local.conf to add packages to every 
image built

IMAGE_INSTALL_append = " mono"

Q. How do I use Mono 3.4.0 on Windows?

A. See the article here on building the Mono sources under Windows
 
http://www.codeproject.com/Articles/769292/How-to-build-Mono-on-Windows