Hi! On Sun, 23 Jun 2019 15:41:33 +0200 Hannah von Reth <vonr...@kde.org> wrote: > The main question is, how are backend and froentend supposed to > communicate? > > A server client application using sockets?
Yes. The good thing is: This part is solved, already. We really do have separate processes for frontend and backend. > Also be aware that if both frontend and backend depend on Qt, you'd > need to ship Qt two times. True. Fortunately, the backend is a console application, only, and will only need a few of the Qt dlls. > > Cheers, > > Hannah > > On 23/06/2019 12:40, Thomas Friedrichsmeier wrote: > > Hi! > > > > I'll try to break my earlier question about building rkward > > frontend / backend with different compilers into (hopefully) more > > managable chunks. The basic idea is still that we might build our > > frontend process using MSVC (and will be able to use QWebEngine), > > and the backend process using MinGW (in order to solve compatibility > > nightmares). Questions: > > > > 1. I assume it is still correct that craft does not support multiple > > compilers in one installation, and there are no plans to add > > anything the like. > > > > My plan then would have to be along the lines to build the backend, > > alone, on a MinGW craft, and the frontend, on an MSVC craft. Then on > > the MSVC craft, I would additionally fetch the MinGW-built backend > > binary, somehow. So questions: > > > > 2. Can a single craft recipe produce two separate artifacts > > (frontend / backend), or will I need separate recipes? > > > > 3. Can a single recipe be source-compiled on one compiler, but > > binary on another? Or will I need to split the backend package, > > further, into a source recipe and a binary recipe? > > > > 4. (How) can I install a binary package from the binary factory > > itself? > > > > Regards > > Thomas
pgp11oUYTfiAF.pgp
Description: OpenPGP digital signature
