Tricky opensource legal issue in embedded development
There is a host processor (H) and a separate auxiliary processor (A). The host processor runs a C library (that is GPLv2) which is responsible for pushing some initialization code to the auxiliary processor (A). This initialization code is the compiled binary of proprietary software (with a commercial license, but which we have been granted rights to use); we store this initialization code in a C array in a header file (summary: we store the compiled binary of proprietary software in a C array in a header)

Question: Is the proprietary source code used to build the binary initialization code tainted by the GPLv2 ?

In other words, since the binary of the original proprietary software is now included in a `.h` file (which is under the GPL), is there now a kind of 'retrospective effect' on the source code, also bringing it under the GPL, and thus requiring its release ?

 
Tricky opensource legal issue in embedded development
===

There is a host processor (H) and a separate auxiliary processor (A). The host processor runs a C library (that is GPLv2) which is responsible for pushing some initialization code to the auxiliary processor (A). This initialization code is the compiled binary of proprietary software (with a commercial license, but which we have been granted rights to use); we store this initialization code in a C array in a header file (summary: we store the compiled binary of proprietary software in a C array in a header)

Question: Is the proprietary source code used to build the binary initialization code tainted by the GPLv2 ?

In other words, since the binary of the original proprietary software is now included in a `.h` file (which is under the GPL), is there now a kind of 'retrospective effect' on the source code, also bringing it under the GPL, and thus requiring its release ?

 