Hi Isaac,
here we also have a mixture of embedded and desktop applications. We use
yocto for our embedded devices (Xilinx Zynq, Raspberry Pi, Gumstix).
The SDKs and images are very helpful for (cross platform) CI and deployment.
A first milestone definitly would be having a minimal platform support
for windows, so windows binaries can be built via mingw.
I see 2 steps there:
- cross build on a unix host
- native build on windows
A real Windows SDK support would be awesome (exspecially for deploying
library dependencies)
I think some "zip" images would be a good start for "image"-deployment.
I see the support for WiX-Installer second.
There is already some kind of "first try" with the mingw meta layer at
http://git.yoctoproject.org/cgit.cgi/meta-mingw - but I tried to use it
with our windows projects and failed, since the mingw version there is
extremly old.
Regards
Florian
Am 14.03.2018 um 05:15 schrieb Isaac Nickaein:
I know the idea is wild and possibly not a top priority (or even
priority) of the community, but extending the area of Yocto to support
Windows platform can make it the ubiquitous build system for the
enterprise, especially in embedded companies that have a mixture of
embedded and desktop applications.
In our company, we have adopted Yocto to be our build system for
embedded devices and are starting to use it for constant integration
and version management. It also solves the headache of setting up an
C++ environment by building and provding an SDK that covers a large
set of libraries.
Having a unified build system can hugely simplify the build
management, version control and integration for large organizations
where various platforms are targeted. Yocto has proven to be a great
tool for this and I believe it has potential to cover this area too.
While Yocto is mainly used to build *images* for embedded targets, for
Windows platform it would be enough to build the binaries for
applications, at the first milestone at least. One can also extend it
to build setup files with tools such as WiX installer scripts. So, it
can be break down into:
1. Supporting a bbclass that creates Windows-compatible binaries. With
the help of compilers like mingw, there is the possibility.
2. Creating an SDK that targets Windows.
3. Adapting recipes to be able to build the sources for Windows (for
the cross-platform sources, this would be straight-forward).
I am not sure how much of effort these steps would take and what are
the obstacles. I would be glad to hear from community on what they
think and why this would or not happen.
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
