> Try to build a release build, and see if that helps. If not, you can 
> manually inspect the files in the moc_files folders to see if their 
> custom build step is correct.

No difference with the release build. Looking at the "mocinput" folder
of 
the vcproj file, it's clear there's a bunch of missing files. This is
where 
the custom build directives are, in case anyone's confused. This looks 
easily corrected assuming there's no magic I'm unaware of.

The other build errors on this fresh release build:

lyx fatal error C1083: Cannot open source file:
'\lyx\lyx-devel\src\support\atoi.C': No such file or directory
-- is this file supposed to be checked in and is not?

C:\lyx\lyx-devel\src\insets\insetgraphicsParams.C(278): fatal error
C1021: invalid preprocessor command 'warning'
-- should be "#pragma warning ..." ?

C:\lyx\lyx-devel\src\frontends\qt2\moc\QGraphics_moc.C(54): error C2947:
expecting '>' to terminate template-argument-list, found '>>'
-- several of these in this file. The compiler wants a space before the 
trailing '>'. But, yikes, this is generated code.

I'm attaching the build log for anyone's convenience.

Question: I'm curious about the history behind the vcproj build - was
there 
no objection that this would have to be maintained separately from the
other 
makefile(s) whenever a file is added/removed from the build. Or am I
missing 
something?

Thanks
Rob 

Attachment: buildlog.htm.bz2
Description: buildlog.htm.bz2

Reply via email to