po-util/Lobby

Particle Offline Utility: The Ultimate Local Particle Experience for Linux and macOS

Jeremy Ellis

@hpssjellis

Looks like particle doesn't totally hate me. They want to see my openthread methods https://community.particle.io/t/using-particle-mesh-devices-with-the-openthread-border-router/46189/68

Nathan Robinson

@nrobinson2000

I saw your post earlier today. I'm pretty sure Brandon is going to try replicating your setup in Workbench.

Jeremy Ellis

@hpssjellis

My cloud attempt at po-util is coming along. I am still making some changes. any idea what might be causing this issue.

mbedtls/library/oid.c:295:39: error: 'oid_ext_key_usage' defined but not used [-Werror=unused-const-variable=]
static const mbedtls_oid_descriptor_t oid_ext_key_usage[] =
^~~~~
mbedtls/library/oid.c:167:30: error: 'oid_x520_attr_type' defined but not used [-Werror=unused-const-variable=]
static const oid_x520_attr_t oid_x520_attr_type[] =
^~~~~~
cc1: all warnings being treated as errors
make[2]: [../../build/module.mk:272: ../../build/target/mbedtls/platform-12/./mbedtls/library/oid.o] Error 1
make[1]: [../build/recurse.mk:12: third_party/mbedtls] Error 2
make: * [../build/recurse.mk:12: crypto] Error 2

They are only warning, any idea how to suppress warnings as errors?

Jeremy Ellis

@hpssjellis

Not really sure which make file needs this but it might suprress the warning

-Wno-unused-const-variable

Jeremy Ellis

@hpssjellis

I think I know what is happening, not sure where po-util stores the gcc make files that are used. any suggestions?

Jeremy Ellis

@hpssjellis

I think I asked this before but can't find your reply, where are the src and make files stored that po compiles? Strangely hard to find. Can't even find the particle version of openthread.

Nathan Robinson

@nrobinson2000

Are you referring to ~/.po-util/src/particle/firmware ?

@hpssjellis

I saw your video today, very nice.

Jeremy Ellis

@hpssjellis

Thanks. Better news. I got cloud po-util working!

Jeremy Ellis

@hpssjellis

Best thing is it works on my Particle build. I am probably going to change the github a fair bit but it is here https://github.com/hpssjellis/gitpod-po-util

emdash

@emdash

I am pulling my hair out with Particle and external libraries. I would really like is some minimal Makefile that builds exactly the sources I specify against the Particle toolchain, but without all the dependency management. I would prefer to manage dependencies via git submodules, and not be endlessly copying files around or having libraries silently "upgraded" behind my back.

Is this even possible?

I am not having much luck with workbench, and from what I can tell, po-util works in a similar way. But I figure @nrobinson2000 probably knows more about the particle toolchain than anyone else at this point

Jeremy Ellis

@hpssjellis

Not sure if this is helpful but I just found out about platformio.org and with the particle debugger board $20 it seems to work with the xenon, possibly the Argon.

emdash

@emdash

@hpssjellis I'll take a look

Nathan Robinson

@nrobinson2000

@emdash Long before Particle created the updated library structure that is used by Workbench and particle-cli, I had developed my own system for managing a centralized directory of installed libraries that would get symbolically linked into each project directory. When Particle announced the new structure for libraries I decided to add compatibility for the structure to po-util by integrating workbench's makefile. My old (legacy) system still exists within po-util.

I agree that it would be better for Workbench/particle-cli to utilize a local centralized directory of libraries instead of requiring users to make a copy of a library in each project.

I have been dreaming of creating new utility similar to po-util that would make use of more of the new tools that Particle is developing, but I'm not sure if it would be necessary if Particle added the features to the tools themselves.

@emdash Could you describe your situation a little bit more? I just made a repository to test using a library as a git submodule and it works pretty well. https://github.com/nrobinson2000/submodule-test

Blake Bourque

@TechplexEngineer

I just installed the SparkIntervalTimer library "po lib add SparkIntervalTimer", I see the new directory with the library but when I build I get a mesage "SparkIntervalTimer.h no such file or directory" However that file is clearly in the SparkIntervalTimer folder. What am I missing?

Nathan Robinson

@nrobinson2000

I'm getting the same issue. It's probably something to do with the symbolic links. Personally I've switched to using the official Particle structure for all of my projects because of its interoperability with Workbench and particle-cli. I would like to make a system that uses git submodules in the future.

If I use SparkIntervalTimer in an officially structured project it works fine:

particle project create --name interval-test .
cd interval-test
particle library copy SparkIntervalTimer
mv src/interval-test.ino src/interval-test.cpp
vim src/interval-test.cpp # Load in demo
po photon build-beta

Nathan Robinson

@nrobinson2000

To anyone who still uses this gitter, I am proud to release neopo, a replacement for po:

https://community.particle.io/t/neopo-a-lightweight-solution-for-local-particle-development/56378

Where communities thrive

People

Repo info

Activity