#19 Support for project scope paths

[Anonymous]

Hello,

I'm using the latest Avr Eclipse plugin version 2.1.1 with Eclipse version 3.3, CDT 4.0. I just started using it, but I'm very enthusiastic right now...!

I got the following question: I'm not very "happy" with the fact that I'll have to add the WinAvr toolchain to my windows path. This because I have multiple versions of the WinAvr toolchain installed on my PC. Older projects keep working on the old toolchain, newer projects use the latest toolchain.

It would help me if I could change the path for each project. I tried the Project Properties --> C/C++ Build --> Environment setting, but this doesn't seem to work. Because when I try to change "AVR target hardware" I get an error message & an empty list.

So I guess the toolchain needs the path before the project environment settings are applied (are they in fact applied when I open the project, or are they only applied when I build my project...?)

Maybe you have a suggestion for me, on how I can store the path settings in my Eclipse project?

Grtz,
Ivo Sieben

[Thomas Holland]

Logged In: YES
user_id=1542541
Originator: NO

Well, you don't have to add winAVR to your windows path for the Plugin. Actually the plugin does not use the windows path at all.

By default the Plugin will determine the path from the Windows Registry, but this path can be modified in the Preferences (Window -> Preferences... -> AVR)

But this is currently a global setting for all projects.

While I have thought about per Project Path settings and there is already some - untested - code in the plugin to support this, I didn't get around to writing the necessary GUI code.

However following the discussions about the advantages and drawbacks of the latest winAVR releases I will be implementing per Project paths in one of the next releases (probably not the next one, as this is reserved for AVRDude support which I really want to get released).

But for a Workaround you have two options:
1. Change the global path setting anytime you switch projects.

1. Set the Plugin path to the AVR-GCC to some custom value pointing to the bin directory of one of your winAVR installations. This is needed because the plugin needs to know the path to one avr-gcc, which is called internally to get a list of all MCUs to avr-gcc supports.

Then change the PATH envvar for each build configuration as needed via "Project Properties -> C/C++ Build -> Environment Settings -> PATH -> Edit". This edited PATH is what the build will use when calling make with the generated makefiles. If you don't change the value manually, the plugin will prepend the path from the preferences (actually two paths, one to the avr-gcc bin directory and one for the make bin directory), but any edited changes seem to be override the settings of the plugin.

I just tried number 2 and it did seem to work. Please report if it works for you.

brgds

Thomas

P.S. I changed the title of your request and moved it to "Feature Requests", so I have a reminder to implement the project scope path settings.