87 2010-04-01 12:37:02 +0000 toolchain triplet should be project specific 2011-01-11 11:26:43 +0000 1 1 6 Yocto Project Subprojects Anjuta Plugin anjuta-plugin 0.9 All Multiple RESOLVED WONTFIX Low enhancement 1.0 M1 1 gary liping.ke jessica.zhang josh liping.ke sgw yp.ap.watcher yp.watcher --- --- --- oldest_to_newest 8350 0 gary 2010-04-01 12:37:02 +0000 As is, the toolchain triplet is a global setting. This makes it difficult to work on more than one project where the target machine architecture changes, e.g. ARM & PowerPC 8454 1 josh 2010-04-16 15:39:20 +0000 The suggestion ehere would be to store the Anjuta plugin configuration, particularly the toolchain triplet, in the specific project file. An even better solution would be to enable on the fly toolchain changing, by some highly visible UI such as a toolbar item. 8698 2 liping.ke 2010-05-21 04:23:49 +0000 Hi, Josh This is a good point. Since I often feels uncomfortable with anjuta compares with eclipse experiences. In Eclipse, general configuration and project configuration is easy to identify. For compile/debug/connect/deploy/device scripts, it is regarded as the run/debug dynamic target configuration. Even for the same application, I can safely add different run/debug target, so that my same project could easily run on arm device/qemu/x86, etc. I can just have three different run/debug targets. That's fine. And eclipse could open many projects in the same view. But seems anjuta did not have this concept well...Rather it's quite discrete in different menus ( in run, there're something like debug remote target...). What's most important is that anjuta must open one project in one process. It can't multiply open several projects. It's a big limitation. I will also log this as an improvement in our task list to see if we can do anything better in spite of the limited framework. How do you think? Thanks& Regards, criping (In reply to comment #1) > The suggestion ehere would be to store the Anjuta plugin configuration, > particularly the toolchain triplet, in the specific project file. > > An even better solution would be to enable on the fly toolchain changing, by > some highly visible UI such as a toolbar item. > 9665 3 liping.ke 2010-09-08 05:46:55 +0000 This bug is caused by current anjuta framework limitation. We won't fix this bug currently. I will first put off this bug to M4 and collect some anjuta community feedbacks firstly. 9788 4 liping.ke 2010-09-13 23:56:58 +0000 I have filed a bug in anjuta bugzilla, hoping that we can get some answers about the problem. If anjuta has some support for this, it would be easier. Otherwise, we can't support the features right away. https://bugzilla.gnome.org/show_bug.cgi?id=629615 One thing is sure, we might still wait anjuta itself enable this session-wide preference settings, please see below response I got from anjuta: " Johannes Schmid [anjuta developer] 2010-09-14 06:30:13 UTC There is the AnjutaSession interface that allows you to save values to the project (project = session). But that requires you to listen to the "save-session" and "load-session". In theorie, there is a flag in the preferences definition that makes preferences project-wide but it isn't used until now. I plan to add support for this with the GSettings migration in the next cycle." Regards, criping 11446 5 jessica.zhang 2011-01-11 11:26:43 +0000 Please note, Yocto project for Anjuta plug-in support will leave things in the current state and open to community pick up futher enhancement and bug fixes