How to install M2M Studio 1.1.0 under Linux


Here is a quick guide to install M2M Studio plugins over a Linux Eclipse platform.

  • Download and install an Eclipse 3.4.2 platform for Linux, from It is recommended to use the Eclipse IDE for C/C++ Developers one.
  • Launch this Eclipse platform
  • Add M2M Studio update site: go to Help > Software Updates > Available Software, and add the URL
  • Click the checkbox in order to install everything from this update site, click Install and follow the steps.
  • Restart your Eclipse platform when asked: now M2M Studio plug-ins are installed.
  • To get started, display the Packages Manager or Open AT perspectives. If the Open AT perspective does not appear in the default list, click the Show all checkbox to display it.


when I import an m2m studio (1.0.2 win) project into 1.1.0 linux , I get a couple of errors:
at org.eclipse.cdt.managedbuilder.internal.dataprovider.ProfileInfoProvider.getEntryValues(
at org.eclipse.cdt.managedbuilder.internal.dataprovider.BuildEntryStorage.getDiscoveredEntries(
at org.eclipse.cdt.managedbuilder.internal.dataprovider.BuildEntryStorage.putEntriesToLevel(
at org.eclipse.cdt.core.settings.model.util.AbstractEntryStorage.initCache(
at org.eclipse.cdt.core.settings.model.util.AbstractEntryStorage.getEntries(
at org.eclipse.cdt.managedbuilder.internal.dataprovider.BuildLanguageData.getEntries(
at org.eclipse.cdt.core.settings.model.extension.impl.CDefaultLanguageData.getEntriesToCopy(
at org.eclipse.cdt.core.settings.model.extension.impl.CDefaultLanguageData.createStore(
at org.eclipse.cdt.core.settings.model.extension.impl.CDefaultLanguageData.copySettingsFrom(
at org.eclipse.cdt.internal.core.settings.model.CLanguageSettingCache.copySettingsFrom(
at org.eclipse.cdt.internal.core.settings.model.CLanguageSettingCache.(
at org.eclipse.cdt.internal.core.settings.model.CFolderDescriptionCache.copyLanguageData(
at org.eclipse.cdt.core.settings.model.extension.impl.CDefaultFolderData.copyDataFrom(
at org.eclipse.cdt.internal.core.settings.model.CFolderDescriptionCache.(
at org.eclipse.cdt.internal.core.settings.model.CConfigurationDescriptionCache.copyFolderData(
at org.eclipse.cdt.core.settings.model.extension.impl.CDefaultConfigurationData.copySettingsFrom(
at org.eclipse.cdt.internal.core.settings.model.CConfigurationDescriptionCache.loadData(
at org.eclipse.cdt.internal.core.settings.model.CProjectDescription.loadDatas(
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.loadProjectDescription(
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(
at org.eclipse.cdt.internal.core.settings.model.CProjectDescriptionManager.getProjectDescription(
at org.eclipse.cdt.internal.core.model.CProject.computeSourceRoots(
at org.eclipse.cdt.internal.core.model.CProject.computeChildren(
at org.eclipse.cdt.internal.core.model.CProject.buildStructure(
at org.eclipse.cdt.internal.core.model.Openable.generateInfos(
at org.eclipse.cdt.internal.core.model.CElement.openWhenClosed(
at org.eclipse.cdt.internal.core.model.CElement.getElementInfo(
at org.eclipse.cdt.internal.core.model.CElement.getElementInfo(
at org.eclipse.cdt.internal.core.model.Parent.getChildren(
at org.eclipse.cdt.internal.core.model.CModelManager.create(
at org.eclipse.cdt.internal.core.model.CModelManager.create(
at org.eclipse.cdt.core.model.CoreModel.create(
at org.eclipse.cdt.internal.ui.navigator.CNavigatorContentProvider.convertToCElements(
at org.eclipse.cdt.internal.ui.navigator.CNavigatorContentProvider.interceptUpdate(
at org.eclipse.ui.internal.navigator.NavigatorPipelineService.pipelineInterceptUpdate(
at org.eclipse.ui.internal.navigator.NavigatorPipelineService.interceptUpdate(
at org.eclipse.ui.navigator.CommonViewer.update(
at org.eclipse.jface.viewers.StructuredViewer.update(
at org.eclipse.jface.viewers.StructuredViewer.handleLabelProviderChanged(
at org.eclipse.ui.navigator.CommonViewer.handleLabelProviderChanged(
at org.eclipse.jface.viewers.ContentViewer$1.labelProviderChanged(
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider$
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.fireLabelProviderChanged(
at org.eclipse.ui.internal.navigator.NavigatorContentServiceLabelProvider.labelProviderChanged(
at org.eclipse.jdt.ui.ProblemsLabelDecorator.fireProblemsChanged(
at org.eclipse.jdt.ui.ProblemsLabelDecorator.access$0(
at org.eclipse.jdt.ui.ProblemsLabelDecorator$1.problemsChanged(
at org.eclipse.jdt.internal.ui.viewsupport.ProblemMarkerManager.runPendingUpdates(
at org.eclipse.jdt.internal.ui.viewsupport.ProblemMarkerManager.access$0(
at org.eclipse.jdt.internal.ui.viewsupport.ProblemMarkerManager$1.runInUIThread(
at org.eclipse.ui.progress.UIJob$
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(
at org.eclipse.swt.widgets.Display.runAsyncMessages(
at org.eclipse.swt.widgets.Display.readAndDispatch(
at org.eclipse.ui.internal.Workbench.runEventLoop(
at org.eclipse.ui.internal.Workbench.runUI(
at org.eclipse.ui.internal.Workbench.access$4(
at org.eclipse.ui.internal.Workbench$
at org.eclipse.core.databinding.observable.Realm.runWithDefault(
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(
at org.eclipse.ui.internal.ide.application.IDEApplication.start(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at org.eclipse.equinox.launcher.Main.invokeFramework(
at org.eclipse.equinox.launcher.Main.basicRun(

and some warnings:
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US
Command-line arguments: -os linux -ws gtk -arch x86

This is a continuation of log file /home/luca/Work/development/wavecom/workspace/.metadata/.bak_0.log
Created Time: 2009-08-18 10:38:13.785

Tue Aug 18 10:38:22 CEST 2009
Unable to locate $os$/dd path in com.wavecom.openat.ide.ebs.armelfgcc bundle




if can help
importing the same project in m2m studio 1.1 for win it works


I found the problem:
old projects contains the mingw build configuration that on linux version not exists :slight_smile:
I tried the import ‘existing openat studio projects’ but the imported project have the same issue
now the problem is that projects are incompatible between linux and windows.
is possible to implement a workaround like a dummy mingw configuration on linux?


Thanks for your investigation.
Did you make the try of importing a project which does not contain a MinGW build configuration? Is it working?


For who will try to use the new m2m I write down some mandatory steps:
open packages manager perspective
click on add new repository
select folder (i copied the openat installation from windows to linux)
then select the new repository and with right click select install packages
now a restart of eclipse is needed


I tried the following:
created a new project with name ‘test’ and with the needed plugins, then copied the .cproject from test to old project and replaced all occurrence of ‘test’ with the name of the old project
it works on linux.


This is a bug specific to M2M Studio plug-ins when they are installed over an existing Eclipse platform (whatever is the OS, win32 or linux).
As a workaround, please download the following file ( and replace the one existing in the plugins directory of your Eclipse installation.
This will fix the need for restart bug.

Please advise if this fixes also the project import bug or not.


thanks I will try it asap,

a think… the m2m 1.1 on linux is several time faster in comparison to m2m 1.0.2 on win.
My opinion is that the m2m 1.1 is better: good job guys :slight_smile:


Thanks for your feedback, and don’t hesitate to continue testing this Linux version and posting every (constructive :wink: ) remark you have :exclamation:


I installed the plugin (got from the other updatesite) and restarted eclipse , but the import still fails.

another think: on windows when I run the application (non rte) the connection is done automagically (cool) the download starts, but the application is not started. is correct?



What is the “other update site”?
I made the try this morning, and the fix just works…

[ 08:59 AM ] dpo@frilmlnxcpl02 ~/eclipse/eclipse $ ls plugins/*org.eclipse.equinox.p2.ui*
-rw-r--r-- 1 dpo nfsgroup 375575 2009-02-23 19:18 plugins/__org.eclipse.equinox.p2.ui_1.0.4.R34x_v20090123.jar__
-rw-r--r-- 1 dpo nfsgroup 357539 2009-08-24 09:18 plugins/org.eclipse.equinox.p2.ui_1.0.4.R34x_v20090123.jar

Please note the file size above (the xx version is the “old” buggy one, the other is the “new” functional one).

Seems to be a regression since 1.1.0; point logged for correction in next release.
(By the way, even if it is a typo, I like the “automagically” word :wink: )

I suppose is the windows update site

is not a typo :laughing: , I like this word too, some kind of automations are better explained with this word.


#14 is the update site for the full Windows application (including all Eclipse plug-ins requirements) is the update site containing only the M2M Studio plug-ins, to be installed over an existing Eclipse platform (whatever is the OS).
The plug-in we are talking about is the same on both update sites. Did you make the size check?


I installed from scratch but the when I import the repository from folder, the behavior is the same: eclipse must restart for to see installed adl plugins
here my output of ls
ll plugins/org.eclipse.equinox.p2.ui
-rw-r–r-- 1 luca luca 375575 2009-02-23 20:18 plugins/org.eclipse.equinox.p2.ui_1.0.4.R34x_v20090123.jar
-rw-r–r-- 1 luca luca 128927 2009-02-23 20:18 plugins/org.eclipse.equinox.p2.ui.sdk_1.0.1.R34x_v20081029.jar


Please note the date: you still use the old plug-in version. The fixed one has been generated on 2009-08-12 (cf my own ls result above; obviously it shows “download date” and not the file creation date…)


I agree but that means that the installation procedure will require to install this plugin manually because it will not taken from update site


Well, this is exactly the problem, as I wrote in a previous post:


ok thanks