|
From: | Philip Nienhuis |
Subject: | Re: Building on MinGW using MXE-built dependencies [WAS: Re: mxe-installer try 2] |
Date: | Thu, 13 Jun 2013 19:29:18 +0200 |
User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.11) Gecko/20100701 SeaMonkey/2.0.6 |
John D wrote:
I think one can add a "-platform win32-g++" option to configure.exe thatshould (uhm, might) point to the proper mkspecs subdir. I already have the platform option set, if I don't set it, it displays the message about it needing to be set. On make qt #16?, I think I have Qt compiling now - it looks like where qt
You can add #17-23 from my side :-)
looks for the mkspec folder follows the -prefix option rather than using the mkspec folder it uses in configure and (I assume?) will be copied during the install. The last make qt got to the point of linking QtCore4 and then failed as it couldn't link in libpng, and looked like configure isn't setting it to look in the correct place for it, so I've got it compiling again I hope this time with settings to pull the libpath correctly.
Once you got Octave built completely using native MingW/MXE and have documented it, we might continue hunting down and weeding out unneeded dependencies. libodbc++/postgres/freetds and perhaps sqlite have already been mentioned. During MXE cross-builds on Linux I saw several other package names flashing by that made me wonder what purpose they would serve.
BTW last night in the qt.mk file I think I spotted a reference to unixodbc - but it may be implicitly unselected during configure stage so it may do no harm.
P.
[Prev in Thread] | Current Thread | [Next in Thread] |