This is the second release, with more improved support for devices, Debian packaging, and Python.
If you attempt to launch a project without setting up the Pydev settings, a dialog will ask you for this.
You can launch a project by right-clicking on a project, using Run/Debug As... and select which script is the main script.
There are many fewer password prompts now. You still need to enter these for each ESbox session but you can save it.
More dialogs, like Debian package installation, accept an RSE connection instead of an IP address.
A new command, Debian Package > Create Debian Structure, will run dh_make to set up the skeleton for your project, so you can create a package more easily. Some projects, especially non-autotools ones, will need manual editing.
All the C/C++ project templates can generate Debian projects.
A VNC viewer for Eclipse from the Tools for Linux project has been included. Visit this viewer under Window > Show View > Remote Systems > VNC Viewer.
A new command, Project > Validate Installed Packages, will let you ensure that required packages for your C/C++ or Python projects are installed. You can update packages in scratchbox rootstraps and in Maemo devices at the same time.
For non-C/C++ autotools projects, the packages recommended are only broad guesses, but they list the metapackages and debug support packages you're most likely to need for the project.
This wizard comes up during the New C/C++ and Python project wizards and exposes the ability to configure your network proxy before it starts.
In an SBRSH launch configuration, you can invoke "Exchange keys" to quickly set up the passwordless login from the host to the device and vice versa. (This is an initial approach, which works only from Linux hosts, and will be further improved.)
An import wizard, File > Import > Project from Debian Repository, will let you import the sources for a package available in scratchbox into ESbox.
You can run ESbox from Windows (and OS X too, though this has not been tested throughly). This requires a virtual machine with ssh, samba, scratchbox, and maemo SDKs installed. Please see the Virtual Machines setup page for details.
The "C/C++" project type has been split into distinct C and C++ projects, which will make the C/C++ index more accurate.
We've done initial testing to verify shared library support. The gdb 6.8 debugger is now recommended and used if possible (instead of the obsolete 6.2 or 6.4 in scratchbox), enabling a much smoother debugging experience.
Also, we have a C/C++ shared library libtool-based template project available.
When a template project needs to use "libintl", the wizard will add "doctools" to the target's list of devkits.
We have updates to build and run against the RC2 build of maemo-sdk+. Note: due to a bug, only ARMEL targets will work properly.
You can now Run or Debug a clean C/C++ project; it will be built first.
ESbox can detect the platform used in scratchbox and on your device. (This is mainly internal framework, but you can see it in the Installed Targets preference page as well via the target context menu. Only when a tablet is contacted will its information be established.)
make[1]: Leaving directory `/home/maemo/.mica/.dpkg-buildpackage-tmp/maemoprojectx' dh_clean dh_clean: Sorry, but 4 is the highest compatibility level of debhelper currently supported. make: *** clean? Error 1
This happens if your scratchbox 1 targets for Chinook or Diablo contain the obsolete devkits "maemo3-debian" or "debian-sarge". The recommended devkits are:
perl debian-etch doctools cputransp (the latter for ARMEL)
Invalid scratchbox 2 target, ignoring: <...>
These are harmless.
 |
is a part of |  |
developed by |  |
in cooperation with |  |
and |  |
© Copyright 2007 - 2009, INdT, 2008 - 2009 Nokia