<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Thanks, folks. Jon's experience is good to know and Dan's
extension will be handy for some. And in my previous posting C-S-P
"reset editory history" should have been C-S-P "clear editor
history".</p>
<p> Here's a specific problem I'm having that somebody might be
familiar with. I have two libraries and cannot figure out how to
make a sketch build with refs to both libraries. I originally had
a library.properties for each lilbrary directory (level with their
src subdirs), but the IDE hid one of the two libraries. That is,
although there was no "not found" error for one of the #include
macros the IDE did not include it in the preprocessing for some
reason so I could put "foo" at global scope of the "hidden
library" and not get a compile error. So I thought of hoisting the
library.properties up a level (in "lib" in the pic below) but now
I get a wacky build error. What am I doing wrong? <br>
</p>
<p>One notion of what I'm doing wrong is not blowing a fuse over
there being no formal spec for project.properties and
library.properties, or at least any I've been able to find and
I've been searching for them. Maybe there are reference materials
linked to from a single place in support.particle.io?? I see lots
of examples but not spec. Is it really the case there are only two
possible fields in a project.properties file (name and dependency<br>
</p>
<p>-Pete</p>
<p>PS While preparing this I caught Code/Particle Workbench caching
one of my source files in such a way that my confidence in this
tool is shaken. I'm wishing I could use the makefiles directly.
:-( So when I exit and restart code it has it's own idea of the
state of my source files such that a mutation in between sessions
is not seen. Is this possible? What a P O S. <br>
</p>
<p>The picture of the Code IDE session showing the file/dir layout
is here: <b><a class="moz-txt-link-freetext" href="https://triembed.org/images/particle-workbench-problem1.png">https://triembed.org/images/particle-workbench-problem1.png</a></b></p>
<p><b>The project.properties looks like this</b>:</p>
<p><br>
name=alpha<br>
dependencies.SIAccMagSensor=0.0.1<br>
dependencies.SIPlatform=0.0.1<br>
</p>
<p><b>The library.properties file looks like this. </b><br>
</p>
name=SIAccMagSensor<br>
sentence=foo<br>
version=0.0.1<br>
author=foo<br>
license=foo<br>
url=<a class="moz-txt-link-freetext" href="https://github.com/foo">https://github.com/foo</a><br>
repository=<a class="moz-txt-link-freetext" href="https://github.com/foo">https://github.com/foo</a><br>
paragraph=This library is foo<br>
name=SIPlatform<br>
sentence=a library<br>
version=0.0.1<br>
author=foo<br>
license=foo<br>
url=<a class="moz-txt-link-freetext" href="https://github.com/foo">https://github.com/foo</a><br>
repository=<a class="moz-txt-link-freetext" href="https://github.com/foo">https://github.com/foo</a><br>
<p>paragraph=This library is boo and it is not included in the
compilation of alpha-accmagsensor.ino is compiled</p>
<p><br>
</p>
<p>And here are lines in alpha-accmagsensor.cpp that make this
situation weird. WIth the earlier case with per-lib
library.properties files SIPlatform.h is NOT being compiled, while
with the single library.properties file I get the funky <br>
</p>
<p><br>
#include <SIAccMagSensor.h><br>
#include <SIPlatform.h><br>
#include <stdint.h><br>
<br>
</p>
<p><br>
</p>
<br>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>