Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logilink EC0003 for Rewrite-Branch #387

Open
wants to merge 7 commits into
base: rewrite
Choose a base branch
from
Open

Conversation

hernae
Copy link

@hernae hernae commented Oct 1, 2017

@CurlyMoo
Copy link
Contributor

CurlyMoo commented Oct 1, 2017

Thanks, can you also include this protocol in the unit tests?

@hernae hernae changed the title Logilink EC0005 for Rewrite-Branch Logilink EC0003 for Rewrite-Branch Oct 1, 2017
@hernae
Copy link
Author

hernae commented Oct 1, 2017

I added them but I am not sure if its 100% correct.

@CurlyMoo
Copy link
Contributor

CurlyMoo commented Oct 1, 2017

Can you add a few more? For closed states, some different unitcode and systemcode combinations.

@CurlyMoo
Copy link
Contributor

CurlyMoo commented Oct 1, 2017

@CurlyMoo
Copy link
Contributor

CurlyMoo commented Oct 1, 2017

Can you check the travis output yourself and make sure it at least compiles?

@hernae
Copy link
Author

hernae commented Oct 1, 2017

Yeah sorry, I am at it..

@CurlyMoo
Copy link
Contributor

CurlyMoo commented Oct 1, 2017

Almost there 👍

@hernae
Copy link
Author

hernae commented Oct 1, 2017

Hmm I dont know atm why the unit test fails. I have to look next week into it..

@CurlyMoo
Copy link
Contributor

CurlyMoo commented Oct 1, 2017

You can run the unit tests locally as well. Then you don't have to wait for the full travis run.

@hernae
Copy link
Author

hernae commented Oct 1, 2017

How do I do that?

@pilino1234
Copy link
Member

pilino1234 commented Oct 1, 2017

Set -DPILIGHT_UNITTEST=1 when running cmake, then run the pilight-unittest executable after compilation has finished.

Note that there are a couple of unittests infamous for failing notoriously, see this from one of my PRs (those last 4 builds always fail due to certain tests…) 😆
In case these fail, just restart the tests until those tests pass. I've considered commenting them out for a while (in tests/alltests.c), that works too 😛

@hernae
Copy link
Author

hernae commented Oct 1, 2017

This will compile solely on the rpi, right? Because I don't wanna corrupt my currently running pilight application on my rpi, I am just developing on my pc with notepad++.

Normally I just develop C# and use Visual Studio. Can I use VS for developing or is there another ide I could use? How have you setup your environment when developing for pilight?

@CurlyMoo
Copy link
Contributor

CurlyMoo commented Oct 1, 2017

This will compile solely on the rpi, right?

Or any other unix system. You can run the unit test with having to install anything.

@pilino1234
Copy link
Member

Normally I just develop C# and use Visual Studio. Can I use VS for developing or is there another ide I could use? How have you setup your environment when developing for pilight?

I'd recommend an actual IDE rather than a (advanced) text editor like notepad++. I've had good experience with Jetbrains CLion (which costs however, although it's free for students :D ). Otherwise code::blocks is quite good too.

@CurlyMoo
Copy link
Contributor

CurlyMoo commented Oct 1, 2017

notepad++

I never use differently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants