Hi,

It looks like you have a library in D:\Projects\Arduino\libraries\xxx that Visual Micro is finding the stepper.c file in.

Try moving D:\Projects\Arduino\libraries\xxx somewhere else then click "tools>visual micro>reload toolchain" or re-start 2013

Thanks

Hi,

Oh I see, it's a strange library name I thought it was an old backup of a lib

Okay well you are using 1.0.6 and Visual Micro attempts to cater for all Arduino releases including the 1.5.x beta versions that are soon to be fully released as 1.6.0 replacing 1.0.6

One area of the arduino beta program that has has significant changes in the past year is more flexibility surrounding libraries but at the same time library naming rules have become a little stricter. 

These changes should not affect your compile in this way when using the 1.0.6 system however it can under a few circumstances.

It's normally easily resolved but before I explain more let me ask you what the #includes in the sketch code are for this library and what it was called before it was called xxx?

Thanks

Okay well here is some info that I hope will make it easy for you to sort out and also prevent breakage when you add other libs in the future.

First of all, the problem will be that one or more of the #includes exist in more than one library folder. It is okay for libraries to contain the same named sources but consider how the correct source is identified for the compiler...

Notice that arduino does not use folder names within the #include syntax. This is the root of the problem.

The normal rules for an Arduino library say that a library will contain a .h file of the same name.

So your "grbl" library folder would contain a file called grbl.h and be #included in the sketch. In this case Visual Micro should discover the grbl library and its sources first.

If Visual Micro can not find any includes that match library folder names then the resolution of libraries becomes a little more hit and miss, in as much as Visual Micro has to look through the installed library folders in no specific order to try to discover which files belong to which library.

So, a fix for you is probably to just to add a dummy grbl.h and grbl.cpp to the grbl library folder. This will certainly make it a more "official" arduino library and allow it to be resolved After reloading the toolchain this might well fix the issue.

Hopefully you can see that working without official lib/.h combinations and without qualified library names in #includes is prone to issues. 

Visual Micro also provides and alternative solution but it probably won't allow the code to compile in the arduino Ide just yet. That is we support qualifying the #includes with the lib folder name. For example:-

#include <grbl/system.h>
#include <grbl/config.h>

As said previously, there have been many changes by arduino to how libraries work during the past year or so and whilst your combination works in 1.0.6 it doesn't mean it will work robustly in future Arduino versions. Although I think you will see why you have potential for problems, it would still be useful to see a verbose output of the problem before you rectify it. Please switch on "tools>visual micro>verbose messages", then click "Build>clean solution" then click Build and then email the output to info [at] visualmicro.com.

Thanks

Thanks very much for the great output examples. 

I see that Visual Micro is detecting the <grbl.h> include, but still going on to find the files in the Servo library (to resolve stepper.h). 

One question to save me some testing... Did you #include <grbl.h> above all other #includes?

Thanks again, that was very useful.

Great thanks

When i said servo.h earlier I meant stepper.h which I see is in both the grbl folder and the stepper library folder.

So one last question.

Visual Micro is determining that you are using these libraries:-

Include Path 'C:\arduino\libraries\EEPROM'
Include Path 'C:\arduino\libraries\Stepper'
Include Path 'D:\Projects\Arduino\libraries\grbl'

Would you agree that the stepper library should not be used because you want to use the stepper.h from the grbl lib folder?

Thanks again.

Great thanks

The bug in visual micro is that it is resolving the arduinoIDE/libraries before the sketchbook/user libraries. If it worked the other way around it would find gbrl first and would have resolved the correct files from gbrl.

We can see the problem in the verbose output you sent me:-

Include Path 'C:\arduino\libraries\EEPROM'
Include Path 'C:\arduino\libraries\Stepper'
Include Path 'D:\Projects\Arduino\libraries\grbl'

Should be:-

Include Path 'D:\Projects\Arduino\libraries\grbl'
Include Path 'C:\arduino\libraries\EEPROM'

I will also check my facts about Arduino 1.0.6 but from what I have said it should be clear that if in the future you add another user library that contains a stepper.h your sketch would easily break.

As I am sure you can imagine this is not an exact science and is a weak area of Arduino. I think it right that Visual Micro finds files based on library name and in the order specified by the #includes. This at least gives users a "known state of play"

Thanks again it has been a very useful exercise and expect the bug fixed in the next release later this week or next.

Obviously in the meantime either remove the Stepper library from c:\arduino\libraries or qualify your #includes with "libname/header.h"

#include "grbl/stepper.h"

Hi, 

I don't see how this is resolved. The error was not duplication of stepper.h ( cf Stepper.h) but a double declaration of the __vector_16 variable in wiring.c

Quote:


Apparently this is in both grbl/stepper.c and core/wiring.c


This is  all about the sucky way that Arduino copies files to different locations, inserts headers and, as already noted, gets into fishing around in a somewhat ill-defined way for library headers. 

I am also trying to build grbl in Arduino IDE and have this same double declaration bug. 

I suppose grbl is one part of the problem since they seem to reuse a variable name that is already used in core Arduino. 

It may be that this was not in core when grbl was written about 5 years ago, don't know. 

I'm a little curious how OP managed to get this to build, because I would have thought that wiring.c would always get included. It is pretty indispensable to anything on Arduino.

[ BTW, I love the way my spelling checker suggest that Arduino is misspelt and proposes "arduous". That'd be about right. ]