Actually, now that I look at it more closely, I think I screwed up. When I run cmdparse.ypp through yacc/bison I get a different output that what is in the svn repository. I will update the repository and you can try the new copy.
David On 05/26/2010 10:00 PM, Mark Miesfeld wrote: > On Wed, May 26, 2010 at 4:59 PM, David Ashley > <[email protected]> wrote: > > >> Actually, the yacc portion is all automatic for the Linux build. See >> (about) line 936 in the Makefile.am. The libtool automatically uses the >> version of yacc discovered via the configure.ac file (about line 62). >> > Okay, I thought it would work something like that, but couldn't find > where it actually did it. > > >> My intent was to build the cpp file in Linux and store both the ypp and >> generated cpp file in SVN. That way a Windows builder would not be >> dependent on yacc to build hostemu. >> > Yeah, I think that is a good way to do it. Most people won't have > yacc on Windows, and I'm not sure how good the ported version is > anyway. > > That just leaves this, during the non-debug build on Windows: > > >> c:\work\wc\main\extensions\hostemu\cmdparse.y(304) : fatal error >> C1083: Cannot open source file: >> 'c:\work\wc\main\extensions\hostemu\cmdparse.y': No such file or >> directory >> > The fatal error kills the build. It is looking for cmdparse.y, not > cmdparse.ypp. > > If I rename cmyparse.ypp to cmdparse.y, then the build works. But, I > don't know what effect that would have on the Unix build. > > On the other, in the output cmdparse.cpp, it has lines like this: > > #line 2 "./extensions/hostemu/cmdparse.y" > > It seems there should be some switch for yacc, (or something,) so it > could generate: > > #line 2 "./extensions/hostemu/cmdparse.ypp" > > in the output file. > > Either thing fixes the build on Windows; renaming cmdparse.ypp to > cmdparse.y, or changing all the line directives in the cmdparse.cpp > file. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
