On 03/14/2010 09:01 PM, Joost Verburg wrote:
> On 3/14/2010 3:58 AM, Abdelrazak Younes wrote:
>> Forget about Enchant on Windows it brings in gtk dependency and we don't
>> want to maintain that. I've specifically introduced libhunspell so that
>> we can reuse OpenOffice and/or Firefox dictionaries. I have created an
>> hunspell MSVC solution to generate a dll a while ago, I will send that
>> to you privately. Or we can port that to CMake, more on that later.
>
> Great, thanks. So I can link to hunspell with CMake?

Sure.

>
> Last time I checked (long time ago) cmake didn't work with my gettext
> DLL. This should be fixed now, right?

Right, I always used your gettext dll without problem.

> So then it's indeed time to switch
> to CMake for the Windows releases.
>
>> Or LyX could directly use those installed dictionaries if they are
>> already installed. We should have this dictionaries detection in the
>> NSIS script for initial installation and/or in the configure script
>> (better). This way, we can just tell the user to install the firfox
>> addon and run reconfigure again and voilà, no need to maintain this
>> anymore :-)
>
> I was thinking about creating a wizard that installs an OpenOffice
> dictionary extension in the LyX dictionary folder. The extensions seem
> to be simple zip files.
>
> Not everyone uses Firefox or OpenOffice, so I think we should not rely
> on the dictionaries installed by other applications.

But what if they are already installed at LyX installation time? Quite frankly, when I am on Windows, I hate having to install 3 different dictionaries for OpenOffice, Firefox and Thunderbird... Couldn't we optionally ask the user if she wants to reuse any such installed dictionaries?

>
>> That sounds very good. Additional point: except for Uwe, we all use
>> CMake, not Scons; it's very easy to tell CMake to put compiled files in
>> some common directories. Also CMake has NSIS integration when used with
>> Cpack, which can also be used to generate zip files. So please it would
>> be a good time to standardize Windows developper (and MAC too!) on CMake.
>
> I agree. There's no need to maintain both SCons and CMake and I think
> CMake will be the best option.

Excellent then.

Abdel.

Reply via email to