Hi,

In the last release there was a fix for the ArduinoJson library which compiled with the Arduino Ide but not with Visual Micro. This is probably resolved by following one of the two guidelines below.

Firstly, The error you getting is strange and it would be helpful if you zipped and emailed your library when it is in a state that produced the error. It might also be an idea to click "Build>Clean Solution" to clear the compiler cache after all the changes you have made to the layout of the library.

In earlier versions of visual micro, if a library contained an /src sub folder it was considered to be the new arduino 1.5.x library format otherwise it was considered to be an Arduino 1.0.x format library.

In the latest release, if any source code exists directly in the library folder then the library is considered an Arduino 1.0.x format library. This is how the Arduino Ide works.

1.0.x - Version 1 libraries

The source code of the library must reside in the main library folder, an optional \utility sub-folder is supported for "private" includes. The headers in the library folder (not the utility folder) are #included when adding the library to a sketch

1.5.x - Version 2 libraries

The root of the library must not contain any source code or header files. The source code of the library will be located in the \src sub folder. The \src sub folder may contain an unlimited number of additional "private" sub folders with as many levels of folder below \src as is required. When importing a library to a sketch the header files in the \src folder are #included.

General Library Best Practices

A library will ideally contain one .h header file with the same name as the library folder and that header file is #included in the sketch project main sketch [sketch_name].ino code. This makes it easier for Arduino and Visual Micro to resolve the correct library.

It is recommended that the Visual Micro menu "project>add/import sketch library" command be used to import libraries because this ensures the correct Arduino compatible #include syntax is used in the sketch code. 

For libraries that have conflicting header names or to use specific versions of libraries Visual Micro optionally supports qualifying the library name in the #include <LibName\LibName.h> or #include <LibName\Lib1.h>. Qualifying library names in #includes is not recommended because the code is not compatible with the Arduino Ide. The facility exists purely for experienced users to circumvent a weakness in the Arduino library design that is a result of the simplicity of the design (a benefit to most).

Multiple header files in libraries are supported

Summary

I hope this information helps but would still like a zip of the library sent to info [at] visualmicro.com

Thanks

I don't understand.

Create  library called myLibrary

Put a myLibrary.h in the folder it can be empty if that's easier for you.

Add more .h and cpp fiels to meet your needs.

Then use the "project>add/import library" to include the library in your sketch. Do not add #includes manually because then you will never learn the correct #include syntax.

If you want to move to two different libraries then create separate folders but import both libraries into the sketch.

You own lib code can use other libraries as long as you import them both into the sketch. This is how dependencies are resolved.

Hope that makes sense, to be clear here are the rules

1) Make sure your library is located in sketch\libraries
2) use Visual Micro to import your library into the sketch code. Do not manually add #includes until you know what you are doing.

I'm sorry I don't understand probably because my mind is on other things

1st I need to understand if you have decided to use v1 or v2 library format?

Then please explain why point 3) does not work providing a compiler output of any error?

3. Make LibPack subfolder (or smth like this) in user libraries folder, put there all .h and .cpp files for Lib1, Lib2 and other auxiliary libraries. This is how I tried to do before.
Advatages: 
- only 1 copy of each auxiliary library
- all working files are located in one folder, so it's easy to find them and redistribute
- need to #include only LibX.h file (via #include <LibPack\LibX.h>), but not all the auxiliary libraries, that are used in LibX
- every auxiliary library can be used in main sketch code

Thanks

Thanks for the report.

I have tested this and can confirm that if a v1 library is included in a project but there is not one #include with the name of the library then we get a compiler error.

Short term workaround is to simply create an empty.h of the same name and include it in the sketch above the other header files from the same library.

We will fix it but you should know that without a header file of the same name your library will always be prone to failing after new libraries are installed on your computer. 

#Includes from matching header/folder names get resolved first in a more accurate manner. Then it's pot luck as to which library folder is found containing matching header names.

Ok, that's great! Thank you a lot!