-
-
Notifications
You must be signed in to change notification settings - Fork 795
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
Unit testing running on the development machine #258
Comments
I got you, you need cross compiler for desktop platforms. I'm working on it for @smartanthill project. However, only Mac OS X will be the first host OS for desktop cross-compiling. Which type of your OS? |
You are right. The need behind this unit testing thing is desktop cross compiling. Unit testing would be just a library in desktop compilation. |
Thanks! Could you help us with tool chains which would be used for cross-compiling from Linux 32/64 to Mac/Win/LinuxARM? If they are native packages from Linux package manager, this is good. We will show additional information which packages should be installed to make cross-compiling. For example, "from host Linux 64 to target Windows 32". From the other side will be good to have independent pre-built tool chains (like mingw, or using it) and automatically install it like PlatformIO package. |
Looks like this issue was resolved in PlatformIO 2.3 where is support for desktop development platforms. See docs http://docs.platformio.org/en/latest/platforms/index.html#desktop Please reopen the issue if you still need help. |
Hello,
Is there any feature supporting unit testing running on the development machine?
Ideally, when I build, part of my source code (the one with the logic, not the interaction with hardware) is compiled and unit tested on the development machine.
This implies no upload to a physical platform and no use of emulator/simulator.
I went through the docs and did not find anything in this area.
An idea would be to create a "unit testing" platform using a native compiler for the development machine. Only the relevant tests and related source code would be compiled and immediately run.
This would add just another target platform for a project.
I might give it a try (I started to read the doc about the platform manifest and build script) but prefer to ask if this makes sense or if it would be better to use some other approach.
Olivier
The text was updated successfully, but these errors were encountered: