On Sun, Feb 21, 2010 at 03:07:57PM +0100, Enrico Forestieri wrote: > On Sun, Feb 21, 2010 at 02:27:49PM +0100, Uwe Stöhr wrote: > > > Am 21.02.2010 05:59, schrieb LyX Ticket Tracker: > > > > >#5238: LyX 1.6 fails with non-ascii chars in path (on Windows) > > > > > > Fixed in trunk at r33524. > > > > This breaks the compilation. I now get this error: > > > > Creating library release\lyx.lib and object release\lyx.exp > > support.lib(os.obj) : error LNK2019: unresolved external symbol > > "__declspec(dllimport) public: static class QString __cdecl > > QString::fromWCharArray(wchar_t const *,int)" > > (__imp_?fromwcharar...@qstring@@sa?...@pb_wh@Z) referenced in > > function "class QString const __cdecl > > lyx::support::os::get_long_path(class QString const &)" > > (?get_long_p...@os@supp...@lyx@@YA?BVQString@@ABV4@@Z) > > release\lyx.exe : fatal error LNK1120: 1 unresolved externals > > scons: *** [release\lyx.exe] Error 1120 > > > > CAn you please have a look? > > It compiles fine with MinGW. However, I get a different error when the > NewAPIs.h include is available. Does the attached patch solve the problem > for you?
I have applied the patch in any case, as Win95 is not supported and the presence of NewAPIs.h was giving a compilation error with MinGW. -- Enrico
