Hey, 1. don't use msys shell. 2. make sure stuff like sh.exe is not on your path 3. use configure.bat (not the configure shell script) 4. use backslashes for -I and -L when passing arguments to configure
configure (...) -I C:\ICU\include -L C:\ICU\lib 5. for everything else, use forward-slashes without the drive letter configure -prefix /qt/560 -examplesdir /qt/examples/560 (...) 6. use mingw32-make 7. make sure the Makefile generator qmake is used matches mingw32-make. Item #2 may cause qmake to generate wrong Makefiles for your system. Hope that helps. Rafael On Mon, Mar 28, 2016 at 12:34:38PM -0400, Partha Bagchi wrote: > On Mon, Mar 28, 2016 at 11:41 AM, Thiago Macieira <thiago.macie...@intel.com > > wrote: > > > On segunda-feira, 28 de março de 2016 09:28:14 PDT Partha Bagchi wrote: > > > I am building using a Windows command-line since ./configure chokes on > > > directory separators. For example, I cannot get glib support if I use the > > > Msys shell. > > > > Use forward slashes. > > > I do. for instance, here is the output from my glib-2.0 libs: > $ pkg-config --libs glib-2.0 > -LZ:/opts/opt64-kde/lib -lglib-2.0 -lintl > > However, during configuration, I get errors like > C:optsopt64-kdeincludeglibconfig.h unknown command. > > > > > > -- > > Thiago Macieira - thiago.macieira (AT) intel.com > > Software Architect - Intel Open Source Technology Center > > > > _______________________________________________ > > Development mailing list > > Development@qt-project.org > > http://lists.qt-project.org/mailman/listinfo/development > > > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development -- Rafael Roquetto | rafael.roque...@kdab.com | Software Engineer Klarälvdalens Datakonsult AB, a KDAB Group company Tel. Sweden (HQ) +46-563-540090, USA +1-866-777-KDAB(5322) KDAB - Qt Experts
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development