[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bison v2.2
From: |
Oleg Smolsky |
Subject: |
bison v2.2 |
Date: |
Thu, 13 Oct 2005 15:13:21 +1300 |
Hello all,
has anybody looked at the issue with generated files' location that I
reported in the beginning of September? I also posted a couple of
patches...
Here is the copy of the original report:
------------------------------------------------------------------
I think I have a couple of issues to report :) Given the following
command:
bison -d -S lalr1.cc -o generated/SomeParser.cpp SomeParser.y
I get two files created in my generated/ directory (which is fine):
SomeParser.cpp
SomeParser.hpp
1) The following files are created in the directory where bison is
run (instead of the given output dir):
location.hh
position.hh
stack.hh
2) newly created SomeParser.cpp contains a #include which has a full
path:
#include "generated/SomeParser.hpp"
(instead of just #include "SomeParser.hpp", which breaks the
compilation. After all, .cpp and .hpp files go together and are
located in the same dir.)
Best regards,
Oleg.
- bison v2.2,
Oleg Smolsky <=
- Re: bison v2.2, Akim Demaille, 2005/10/13
- Re[2]: bison v2.2, Oleg Smolsky, 2005/10/13
- Re[3]: bison v2.2, Oleg Smolsky, 2005/10/14
- Re: bison v2.2, Paul Eggert, 2005/10/14
- Re[2]: bison v2.2, Oleg Smolsky, 2005/10/14
- Re: bison v2.2, Paul Eggert, 2005/10/14
- Re[2]: bison v2.2, Oleg Smolsky, 2005/10/14
- Re: bison v2.2, Paul Eggert, 2005/10/15
- Re[2]: bison v2.2, Oleg Smolsky, 2005/10/16
- Re: Re[2]: bison v2.2, Akim Demaille, 2005/10/17