> I am interested to a certain degree. However, it would help
> me a lot to
> have a quick look if the attachments were not declared as octet-stream
> but as, say, application/x-bzip or similar.
>
> Andre'
>
Apologies for the delay. I guess my mailer defaults to octet-stream for
types it doesn'
On Tue, Feb 01, 2005 at 01:16:58PM -0500, Rob Bearman wrote:
> I was able to complete a fresh vcproj build for the first time after the
> latest commits. Thank you for the fixes. I've attached the build log in
> case anyone's interested in the 30 warnings.
I am interested to a certain degree. Howe
Angus Leeming wrote:
>>> Thank *you*.
>>> Angus
>> I'll return the thanks again if someone can give me a pointer on how to
>> set up the LyX installation tree based on a vcproj build.
How is your python? The files that Asger and you both needed are generated
by a shell script lib/configure which
Rob Bearman wrote:
>> Thank *you*.
>>
>> --
>> Angus
>>
>>
>
> I'll return the thanks again if someone can give me a pointer on how to
> set up the LyX installation tree based on a vcproj build. The
> win32\readme.txt file hints that this information was given previously
> somewhere in the Jan
> Thank *you*.
>
> --
> Angus
>
>
I'll return the thanks again if someone can give me a pointer on how to
set up the LyX installation tree based on a vcproj build. The
win32\readme.txt file hints that this information was given previously
somewhere in the January list, but I can't find it beyo
Rob Bearman wrote:
> I was able to complete a fresh vcproj build for the first time after the
> latest commits. Thank you for the fixes. I've attached the build log in
> case anyone's interested in the 30 warnings.
>
> Thanks
> Rob
Thank *you*.
--
Angus
I was able to complete a fresh vcproj build for the first time after the
latest commits. Thank you for the fixes. I've attached the build log in
case anyone's interested in the 30 warnings.
Thanks
Rob
buildlog.htm.bz2
Description: buildlog.htm.bz2
Asger Ottar Alstrup wrote:
> Angus Leeming wrote:
>> Rob Bearman wrote:
>>>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
>>>trailin
Angus Leeming wrote:
Rob Bearman wrote:
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.
Sh
Rob Bearman wrote:
> 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?
It is checked in but has just (a couple of days ago
"Rob Bearman" <[EMAIL PROTECTED]> writes:
| 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
> 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 m
Rob Bearman wrote:
> I've applied Asger's MSVC patch
> (http://thread.gmane.org/gmane.editors.lyx.devel/41102) but I'm having
> problems with the Windows build under Visual Studio.NET 2003. I get a
> bunch of failures trying to find certain *_moc.c files that didn't seem
> to have been generated:
T
> and is there any heads up short of my updating my CVS tree and
watching for it?
Never mind this particular question. I found the lyx-cvs list which was
documented in the web pages if only I had bothered to read it.
Thanks
Rob
I've applied Asger's MSVC patch
(http://thread.gmane.org/gmane.editors.lyx.devel/41102) but I'm having
problems with the Windows build under Visual Studio.NET 2003. I get a
bunch of failures trying to find certain *_moc.c files that didn't seem
to have been generated:
/echo on
-- Build started
15 matches
Mail list logo
