To build a lib sample in Dev (which is the usual reference for the Atom based IDE), you need to have a project for that sample that features a project.properties file.
What I did when updating this library to the 2.0 format was open the example .ino files (examples/combo/combo.ino) from the library checkout and hit “Compile in Cloud” in Dev.
I’m trying to add support for additional hardware to the library, but hit this problem before getting very far.
I can try to get the CLI working again, but it’s always been problematic for me on Linux since it wants me to update the system node.js, which affects unrelated packages.
Just as a note, building the examples in Dev works fine, except for including the library my library depends on. And this used to work, since that’s what I did when doing development for my library.
But I’ll try to get the CLI going again and see if that solves my problem.
This is what I was refering to. It’s not uncommon that library samples or a lib itself would depend on secondary libs, but for that Dev would need to apply the library.properties and/or project.properties files of the lib and/or the sample.