[partly solved] Errors in cross compilation with Windows EA 7
-
wrote on 13 May 2011, 16:31 last edited by
I at least found the reason, why the build breaks for the (pre-)generated sources:
The WinCE Compiler has a strange behaviour regarding those "#line" statements which are included in the pre-generated sources and which refer to the source of the generated files:
it appears that when compiling the generated files, the filename as referred to by the #line directive, actually has to be present at that location, otherwise the build fails...
(it's sufficient to be a 0-size file with exactly that name at the referred position, but it must exist)that's not even a new feature/bug introduced into WinEA7, WinCE6.00 (at least the MS-Auto variant) behaves exactly the same...
--> title updated!
-
wrote on 14 May 2011, 09:16 last edited by
It does not look that there has been any feedback from Qt's experts. At least nobody from Qt besides Alexandra has added something to this thread.
That is a pitty.
I think you should file a bug report. -
wrote on 14 May 2011, 09:26 last edited by
I have not prepared a bug report to Qt yet, but have a look to "Contribute ":http://developer.qt.nokia.com/contribute
Apparently, you have entered new ground, but Qt's experts should be interested to understand your issues. Sooner or later thay will face those problems as well.I am interested in the follow up, so please make sure that some sort of summary is posted, when you get additional help.
-
wrote on 16 May 2011, 09:41 last edited by
actually this problem regarding the broken "#line" directive seems more of a MicroSoft issue for MS Auto/Windows embedded automotive - those both do not use the PlatformBuilder for compilation but a pure commandline environment; at least in a normal (i.e. not cross-compile) VisualStudio Project, this works...
I already submitted a bug-report towards MicrosSoft, maybe they'll fix this in an upcomming release.Actually the contribution of QT developers here is a bit disappointing :-(
-- I have more unsolved issues which I would need assistance for... -
wrote on 16 May 2011, 11:06 last edited by
Did you try it with a bug report to Qt?
I could imagine that Qt brains may follow some discussions, but avoid to get too much involved in the forum. -
wrote on 17 May 2011, 12:43 last edited by
well - I don't see this as a Qt bug, it's more a Microsoft compiler bug...
actually the compiler-switches that I defined for my selfmade mkspec configuration were causing the trouble:
I used the same switches that I use at work for compiling, but there is a problem with the CE compiler's "/FA" switch - when this switch is defined, the "#line" directive behaves the strange way I described!
(/FA is used to let the compiler produce/keep the assembly listing; this is useful for debugging purpose but not really neccessary in Qt compilation)
21/26