Hi Andreas, On Mittwoch, 18. Mai 2016 15:40:26 CEST Andreas Färber wrote:
I don't think so... While MIT is redistributable and does not require them or us to redistribute source code, the only exception to providing source code on our openSUSE OBS that I'm aware of is "SUSE-Firmware", which I doubt applies in this cross-compilation case. MIT is not really a non-free license, so openSUSE:Factory:NonFree seems a misfit, too.
However the only official Wiki page I could come up with is:
https://en.opensuse.org/openSUSE:Build_Service_application_blacklist
This is also the wiki page I've found. In addition the first bullet-point of [1] might fit, it is related to cross- compilation where one might need some previous toolchain to build other packages. There is written that I should contact the openSUSE Packaging Committee, but this is the only place this committee is mentioned therefore I don't know if it really exists ;-)
For those of us not so familiar with Espressif, could you provide some more details on what library we are talking about here? (name, purpose)
In particular I am wondering whether it might be possible to build a non-Espressif based xtensa toolchain with my pending newlib package and our binutils and gcc5/gcc6. In a quick experiment binutils succeeds to build [1] but I don't spot xtensa support in newlib - is libc one of those binary libraries?
The toolchain (gcc, libc, ...) is already built from source with a patched version of crosstool-ng, see [2]. What's missing are libraries for interfacing timers, rtc, watchdog, flash or wifi, as well as some highlevel libraries as SNTP, DNS, TCP, UDP, JSON, ... Some of these are based on open source projects under BSD licence as lwIP, wpa_supplicant, net80211, axTLS extended by some wrappers. The first library they've released there modified sources for is lwIP. This is also what I would like to build from source instead of using the binary library [3]. Unfortunately due to the wrappers it is not possible to build this library without some parts of their binary SDK and without the wrappers it won't be compatible to the API documentation... One solution might be that I just package the header files, and fetch the libraries with the script on the user PC, linking is anyway done by the user. But then I would still upload the original zip file with the binary libraries and just do not copy them to the rpm. But it would be nicer to have the headers and libraries in the rpm. Regards, Thomas [1] https://en.opensuse.org/openSUSE:Packaging_guidelines#Exceptions [2] https://build.opensuse.org/package/show/CrossToolchain:xtensa/xtensa-lx106-g... [3] https://build.opensuse.org/package/show/CrossToolchain:xtensa/esp-open-lwip -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org