Abdelrazak Younes wrote:
>> no-undefined symbols work well with C++. However I don't
>> see what you'd link to make this usable.
>>
>> We have  (1)  core + frontend  (without Qt)
>>         (2)  frontend + frontend/qt (without core)
>>
>> But linking-wise both depend on the 'without' stuff
> 
> With some effort (1) should not depend on Qt and that's the way to go IMHO:
> 
> - static lib libLyX.[a/lib]:
>   contains core (src/inset/support/etc) + frontend + controller
> 

It's not hard do create a shared support library, it's the most simple
part, I already had it in my dll branch.

> - executable LyX[.exe]:
>   * contains main.C
>   * statically link to libLyX.
>   * not linked at all to qt.
>   * will dllopen a dll that conforms to the virtual interface defined
>     in frontend
> 
> - dynamic lib libLyXqt4.[so/dll]:
>   * constaind qt4/*
>   * statically linked to libLyX
> 
> Of course this would mean that the resulting binary files would be a bit
> larger because libLyXqt4 and LyX.exe would contain non shared symbols
> but with further cleanup of the frontend and controller interface, this
> should be diminishing with time.
> 
> Abdel.
> 
> 


-- 
Peter Kümmel

Reply via email to