maemo.org wiki - User contributions [en]

MADDE/FAQ

2010-01-29T14:01:02Z

194.197.118.140: added question about mounting

=== What is MADDE? ===

MADDE stands for Maemo Application Development and Debugging Environment. It
is SDK for cross compile, debug and package new application for Maemo.
It is not meant to use to build debian packages that use Autotools or
anything that aids compilation by figuring out native system information.

=== What platforms are supported? ===

MADDE supports Windows (XP, Vista, 7), Linux variants, Mac OS X (Snow Leopard). It probably works on other Unix variants too but it is not tested there.

=== Where can I get MADDE? ===

You can download the installer from [http://tablets-dev.nokia.com/MADDE.php MADDE downloads]

=== How do I install MADDE? ===

Installation instructions can be found from main page [[MADDE]]

=== How do I setup cross compilation environment? ===

Cross compilation environment is created by using 'mad-admin create target'
command. You can list supported targets by using 'mad list targets' command.

=== How do I use created cross compilation target? ===

Usually you compile your program by using Makefile and make command.
Now you can give command 'mad -t <target> make' and compilation is
done by using cross compilation environment named <target>.

=== Why doesn't the installer come with the toolchains and sysroots for all available targets? ===

Not every developer needs every target. Installation is faster when
no unneeded components come with the installer. Furthermore, this approach
makes it easier to provide more targets in the future.

=== Can I use several targets simultaneously? ===

Yes you can. When you have created several targets use
'mad -t <target>' to cross compile for <target>.

=== How well does MADDE work for GTK+ development (in C)? ===

MADDE works well for GTK+ development (in C).
At minimum the lines 'pkg-config --cflags gtk+-2.0' (for source to object
file compiling) and 'pkg-config --libs gtk+-2.0' (for linking) is needed
in your Makefile

Use 'mad pkg-config --list-all' to see some other (gtk) modules you may
need.

(Note that if you try to run gcc compilation from command line
outside mad environment the line must be like

mad gcc -o foo foo.c `mad pkg-config --cflags --libs gtk+-2.0'

to get both gcc and pkg-config be run inside mad environment --
When inside Makefile this is not a problem as whole make is run
inside mad environment...).

=== How about Hildon development (in C)? ===

Like the above; just replace 'gtk+-2.0' with 'hildon-1 libosso'

=== Is there an emulator for testing? ===

Not yet. Be patient, its coming soon.

=== Where can I get source code? ===

It is not available yet but it will be. Unfortunately I don't know when.
By the way, most of code are perl and bourne shell scripts. Look inside directories
{MADDE}/version/bin/
{MADDE}/version/madlib/
{MADDE}/version/madbin/

=== How does MADDE work? ===

MADDE is basically a cross-compiler. Cross-compilation are done via 'target'.
Without 'target' one cannot compile. 'Target' hides from the end user
the fact that she/he is actually cross-compiling. The end user can use same
Makefile as in native compilation. Usually no modifications are needed.

Traditionally cross-toolchain contains sysroot. MADDE separates toolchain and sysroot into different components, because libraries and header files are updated more often than compilation tools. MADDE supports GNU GCC and binutils
as a toolchain. No others are currently supported. Support for other toolchains is quite easy to add if they offer similar feature than GCC's --sysroot option.

Compilation is done through 'target' specific wrappers. GCC wrappers work so that they add --sysroot=$SYSROOT_DIR option (SYSROOT_DIR is absolute path into target specific sysroot) and mangle all absolute paths from arguments to be relative to the $SYSROOT_DIR. After that wrappers call a real GCC binary. Path mangling is done by changing first '/' character with '='.
If path prefix already contains SYSROOT_DIR it is not mangled.

In practice SYSROOT_DIR is patched inside wrapper when target is created.

'mad' command finds out the used 'target'. The it adds 'target' specific bin/ (wrappers are there) into PATH environment variable. Now when GCC family is called OS finds out first our wrappers.
Process is simple, isn't it?

=== Where is IDE? ===

Under the work. Qt Creator + madde integration is coming soon.

=== How do I mount local directory to N900 with MADDE? ===

See instructions from there [[MADDE/Mounting| Mounting]]

MADDE/FAQ

2010-01-27T14:08:56Z

194.197.118.140: IDE question added

=== What is MADDE? ===

MADDE stands for Maemo Application Development and Debugging Environment. It
is SDK for cross compile, debug and package new application for Maemo.
It is not meant to use to build debian packages that use Autotools or
anything that aids compilation by figuring out native system information.

=== What platforms are supported? ===

MADDE supports Windows (XP, Vista, 7), Linux variants, Mac OS X (Snow Leopard). It probably works on other Unix variants too but it is not tested there.

=== Where can I get MADDE? ===

You can download the installer from [http://tablets-dev.nokia.com/MADDE.php MADDE downloads]

=== How do I install MADDE? ===

Installation instructions can be found from main page [[MADDE]]

=== How do I setup cross compilation environment? ===

Cross compilation environment is created by using 'mad-admin create target'
command. You can list supported targets by using 'mad list targets' command.

=== How do I use created cross compilation target? ===

Usually you compile your program by using Makefile and make command.
Now you can give command 'mad -t <target> make' and compilation is
done by using cross compilation environment named <target>.

=== Why all toolchains and sysroots for available targets do not come with installer? ===

All developer do not need all targets. Installation is faster when
unneeded components do not come with installer and this approach
makes easier to provide more targets in future.

=== Can I use several targets simultaneously? ===

Yes you can. When you have created several targets use
'mad -t <target>' to cross compile for <target>.

=== How well does MADDE work for GTK+ development (in C)? ===
MADDE works well for GTK+ development (in C).
At minimum the lines 'pkg-config --cflags gtk+-2.0' (for sourrce to object
file compiling) and 'pkg-config --libs gtk+-2.0' (for linking) is needed
in your Makefile

Use 'mad pkg-config --list-all' to see some other (gtk) modules you may
need.

(Note that if you try to run gcc compilation from command line
outside mad environment the line must be like

mad gcc -o foo foo.c `mad pkg-config --cflags --libs gtk+-2.0'

to get both gcc and pkg-config be run inside mad environment --
When inside Makefile this is not a problem as whole make is run
inside mad environment...).

=== Is there an emulator for testing? ===

Not yet. Be patient, its coming soon.

=== Where can I get source code? ===

It is not available yet but it will be. Unfortunately I don't know when.
By the way, most of code are perl and bourne shell scripts. Look inside directories
{MADDE}/version/bin/
{MADDE}/version/madlib/
{MADDE}/version/madbin/

=== How does MADDE work? ===

MADDE is basically a cross-compiler. Cross-compilation are done via 'target'.
Without 'target' one cannot compile. 'Target' hides from the end user
the fact that she/he is actually cross-compiling. The end user can use same
Makefile as in native compilation. Usually no modifications are needed.

Traditionally cross-toolchain contains sysroot. MADDE separates toolchain and sysroot into different components, because libraries and header files are updated more often than compilation tools. MADDE supports GNU GCC and binutils
as a toolchain. No others are currently supported. Support for other toolchains is quite easy to add if they offer similar feature than GCC's --sysroot option.

Compilation is done through 'target' specific wrappers. GCC wrappers work so that they add --sysroot=$SYSROOT_DIR option (SYSROOT_DIR is absolute path into target specific sysroot) and mangle all absolute paths from arguments to be relative to the $SYSROOT_DIR. After that wrappers call a real GCC binary. Path mangling is done by changing first '/' character with '='.
If path prefix already contains SYSROOT_DIR it is not mangled.

In practice SYSROOT_DIR is patched inside wrapper when target is created.

'mad' command finds out the used 'target'. The it adds 'target' specific bin/ (wrappers are there) into PATH environment variable. Now when GCC family is called OS finds out first our wrappers.
Process is simple, isn't it?

=== Where is IDE? ===

Under the work. Qt Creator + madde integration is coming soon.

MADDE/FAQ

2010-01-27T13:56:45Z

194.197.118.140: removed chapter 1 faq

=== What is MADDE? ===

MADDE stands for Maemo Application Development and Debugging Environment. It
is SDK for cross compile, debug and package new application for Maemo.
It is not meant to use to build debian packages that use Autotools or
anything that aids compilation by figuring out native system information.

=== What platforms are supported? ===

MADDE supports Windows (XP, Vista, 7), Linux variants, Mac OS X (Snow Leopard). It probably works on other Unix variants too but it is not tested there.

=== Where can I get MADDE? ===

You can download the installer from [http://tablets-dev.nokia.com/MADDE.php MADDE downloads]

=== How do I install MADDE? ===

Installation instructions can be found from main page [[MADDE]]

=== How do I setup cross compilation environment? ===

Cross compilation environment is created by using 'mad-admin create target'
command. You can list supported targets by using 'mad list targets' command.

=== How do I use created cross compilation target? ===

Usually you compile your program by using Makefile and make command.
Now you can give command 'mad -t <target> make' and compilation is
done by using cross compilation environment named <target>.

=== Why all toolchains and sysroots for available targets do not come with installer? ===

All developer do not need all targets. Installation is faster when
unneeded components do not come with installer and this approach
makes easier to provide more targets in future.

=== Can I use several targets simultaneously? ===

Yes you can. When you have created several targets use
'mad -t <target>' to cross compile for <target>.

=== How well does MADDE work for GTK+ development (in C)? ===
MADDE works well for GTK+ development (in C).
At minimum the lines 'pkg-config --cflags gtk+-2.0' (for sourrce to object
file compiling) and 'pkg-config --libs gtk+-2.0' (for linking) is needed
in your Makefile

Use 'mad pkg-config --list-all' to see some other (gtk) modules you may
need.

(Note that if you try to run gcc compilation from command line
outside mad environment the line must be like

mad gcc -o foo foo.c `mad pkg-config --cflags --libs gtk+-2.0'

to get both gcc and pkg-config be run inside mad environment --
When inside Makefile this is not a problem as whole make is run
inside mad environment...).

=== Is there an emulator for testing? ===

Not yet. Be patient, its coming soon.

=== Where can I get source code? ===

It is not available yet but it will be. Unfortunately I don't know when.
By the way, most of code are perl and bourne shell scripts. Look inside directories
{MADDE}/version/bin/
{MADDE}/version/madlib/
{MADDE}/version/madbin/

=== How does MADDE work? ===

MADDE is basically a cross-compiler. Cross-compilation are done via 'target'.
Without 'target' one cannot compile. 'Target' hides from the end user
the fact that she/he is actually cross-compiling. The end user can use same
Makefile as in native compilation. Usually no modifications are needed.

Traditionally cross-toolchain contains sysroot. MADDE separates toolchain and sysroot into different components, because libraries and header files are updated more often than compilation tools. MADDE supports GNU GCC and binutils
as a toolchain. No others are currently supported. Support for other toolchains is quite easy to add if they offer similar feature than GCC's --sysroot option.

Compilation is done through 'target' specific wrappers. GCC wrappers work so that they add --sysroot=$SYSROOT_DIR option (SYSROOT_DIR is absolute path into target specific sysroot) and mangle all absolute paths from arguments to be relative to the $SYSROOT_DIR. After that wrappers call a real GCC binary. Path mangling is done by changing first '/' character with '='.
If path prefix already contains SYSROOT_DIR it is not mangled.

In practice SYSROOT_DIR is patched inside wrapper when target is created.

'mad' command finds out the used 'target'. The it adds 'target' specific bin/ (wrappers are there) into PATH environment variable. Now when GCC family is called OS finds out first our wrappers.

Process is simple, isn't it?

MADDE

2010-01-27T12:06:59Z

194.197.118.140: /* Guides */

<div style="border: 1px solid red; background-color: #faa; padding: 20px;"><div style="text-align:center;">'''TECHNOLOGY PREVIEW'''</div></div>

== Introduction ==

This is a '''TECHNICAL PREVIEW''' of a new development tool for Maemo. MADDE stands for '''M'''aemo '''A'''pplication '''D'''evelopment and '''D'''ebugging '''E'''nvironment and offers the following features:

* Command-line cross-compiling
* Multi-platform support (Linux (32-bit/64-bit), Windows, Mac OS X)
* Configurable for different targets & toolchains
* Client for the device to simplify the development process
* Simplicity

You are welcome to test the tool in your development process. But keep in mind that this is a technical preview. We highly appreciate your feedback in talk, the developer list and especially in bugzilla (Developer Platform -> MADDE).

Find the talk-thread around MADDE [http://talk.maemo.org/showthread.php?t=38075 here].

== Installation ==

'''1. Download the file for your operating system from:'''
:[http://tablets-dev.nokia.com/MADDE.php MADDE downloads]

'''2. Depending on your operating system:'''

* '''Windows:'''
:Execute the downloaded file and follow the instructions

* '''Linux, Mac OS X '''
:Open the terminal and run:
sh <MADDE installer>

'''3. Start the environment'''

* '''Windows'''
:Find the MADDE terminal in:
:Start -> Programs -> MADDE -> MADDE terminal

:A general information for Windows users: Projects, which are created in MADDE are stored in:
:C:\MADDE\0.5\home\<username>

* '''Linux, Mac OS X'''
:Use the terminal to run the MADDE commands as described in the guides.

== Guides ==

* [[{{PAGENAME}}/Configuration | Guide: Configuration of the development environment]]
* [[{{PAGENAME}}/Qt Example | Guide: Using the template for a small Qt example]]
* [[{{PAGENAME}}/Device runtime | Guide: Connecting MADDE with your device]]
* [[{{PAGENAME}}/Packaging | Guide: Packaging and Deploying to Device with Icon]]
* [[{{PAGENAME}}/FAQ | FAQ: Frequently asked questions]]

[[Category:Development]]
[[Category:Qt]]

MADDE/FAQ

2010-01-27T12:05:55Z

194.197.118.140: how does madde work

=== FAQ ===
This page is for MADDE FAQ

=== What is MADDE? ===

MADDE stands for Maemo Application Development and Debugging Environment. It
is SDK for cross compile, debug and package new application for Maemo.
It is not meant to use to build debian packages that use Autotools or
anything that aids compilation by figuring out native system information.

=== What platforms are supported? ===

MADDE supports Windows (XP, Vista, 7), Linux variants, Mac OS X (Snow Leopard). It probably works on other Unix variants too but it is not tested there.

=== Where can I get MADDE? ===

You can download the installer from [http://tablets-dev.nokia.com/MADDE.php MADDE downloads]

=== How do I install MADDE? ===

Installation instructions can be found from main page [[MADDE]]

=== How do I setup cross compilation environment? ===

Cross compilation environment is created by using 'mad-admin create target'
command. You can list supported targets by using 'mad list targets' command.

=== How do I use created cross compilation target? ===

Usually you compile your program by using Makefile and make command.
Now you can give command 'mad -t <target> make' and compilation is
done by using cross compilation environment named <target>.

=== Why all toolchains and sysroots for available targets do not come with installer? ===

All developer do not need all targets. Installation is faster when
unneeded components do not come with installer and this approach
makes easier to provide more targets in future.

=== Can I use several targets simultaneously? ===

Yes you can. When you have created several targets use
'mad -t <target>' to cross compile for <target>.

=== How well does MADDE work for GTK+ development (in C)? ===
MADDE works well for GTK+ development (in C).
At minimum the lines 'pkg-config --cflags gtk+-2.0' (for sourrce to object
file compiling) and 'pkg-config --libs gtk+-2.0' (for linking) is needed
in your Makefile

Use 'mad pkg-config --list-all' to see some other (gtk) modules you may
need.

(Note that if you try to run gcc compilation from command line
outside mad environment the line must be like

mad gcc -o foo foo.c `mad pkg-config --cflags --libs gtk+-2.0'

to get both gcc and pkg-config be run inside mad environment --
When inside Makefile this is not a problem as whole make is run
inside mad environment...).

=== Is there an emulator for testing? ===

Not yet. Be patient, its coming soon.

=== Where can I get source code? ===

It is not available yet but it will be. Unfortunately I don't know when.
By the way, most of code are perl and bourne shell scripts. Look inside directories
{MADDE}/version/bin/
{MADDE}/version/madlib/
{MADDE}/version/madbin/

=== How does MADDE work? ===

MADDE is basically a cross-compiler. Cross-compilation are done via 'target'.
Without 'target' one cannot compile. 'Target' hides from the end user
the fact that she/he is actually cross-compiling. The end user can use same
Makefile as in native compilation. Usually no modifications are needed.

Traditionally cross-toolchain contains sysroot. MADDE separates toolchain and sysroot into different components, because libraries and header files are updated more often than compilation tools. MADDE supports GNU GCC and binutils
as a toolchain. No others are currently supported. Support for other toolchains is quite easy to add if they offer similar feature than GCC's --sysroot option.

Compilation is done through 'target' specific wrappers. GCC wrappers work so that they add --sysroot=$SYSROOT_DIR option (SYSROOT_DIR is absolute path into target specific sysroot) and mangle all absolute paths from arguments to be relative to the $SYSROOT_DIR. After that wrappers call a real GCC binary. Path mangling is done by changing first '/' character with '='.
If path prefix already contains SYSROOT_DIR it is not mangled.

In practice SYSROOT_DIR is patched inside wrapper when target is created.

'mad' command finds out the used 'target'. The it adds 'target' specific bin/ (wrappers are there) into PATH environment variable. Now when GCC family is called OS finds out first our wrappers.

Process is simple, isn't it?

MADDE/FAQ

2010-01-27T11:37:41Z

194.197.118.140: Emulator and source code questions added

MADDE/FAQ

2010-01-26T13:10:55Z

194.197.118.140: added GTK note

MADDE/FAQ

2010-01-26T12:56:51Z

194.197.118.140: New page: === FAQ === This page is for MADDE FAQ === What is MADDE? === MADDE stands for Maemo Application Development and Debugging Environment. It is SDK for cross compile, debug and package new...