Closed GoogleCodeExporter closed 8 years ago
Do you have the YAML file that produced the error?
Original comment by jbe...@gmail.com
on 4 Nov 2013 at 1:50
I have only game binaries. I have not get game source working, game making
needed to yaml-cpp devel version 0.3.0 or older. That strange??
i have yaml-cpp 0.5.1 and devel. But also 0.3.3 version (not devel files).
Original comment by lah...@gmail.com
on 4 Nov 2013 at 12:21
I'm sorry, this really isn't enough information to go on. In any case, it
doesn't sound like a yaml-cpp problem, but an openxcom problem. Why don't you
ask them?
Original comment by jbe...@gmail.com
on 4 Nov 2013 at 2:08
Original comment by jbe...@gmail.com
on 4 Nov 2013 at 2:09
Sorry about the previous bug report. I tried to accidentally compile the wrong.
My error is here emitterdef.h file.
backtrace is:
make
g++ -Wall -Wextra -O2 -rdynamic -D_GNU_SOURCE=1 -D_REENTRANT
-I/usr/include/SDL -c -o ../obj/pch.o pch.cpp
In file included from /usr/include/yaml-cpp/emitter.h:11:0,
from /usr/include/yaml-cpp/yaml.h:9,
from pch.h:61,
from pch.cpp:1:
/usr/include/yaml-cpp/emitterdef.h:10:43: error: expected identifier before
numeric constant
/usr/include/yaml-cpp/emitterdef.h:10:43: error: expected ”}” before
numeric constant
/usr/include/yaml-cpp/emitterdef.h:10:43: error: expected unqualified-id before
numeric constant
/usr/include/yaml-cpp/emitterdef.h:11:1: error: expected declaration before
”}” token
make: *** [../obj/pch.o] error 1
maybe this help with you.
Original comment by lah...@gmail.com
on 5 Nov 2013 at 6:36
The relevant code is:
struct EmitterNodeType { enum value { None, Property, Scalar, FlowSeq,
BlockSeq, FlowMap, BlockMap }; };
Does something else in your project define something as None?
Original comment by jbe...@gmail.com
on 5 Nov 2013 at 7:36
This is not my project.
im reporting this also openxcom bugtracker. When I do not know where this
would be reported.
sorry for this.
Original comment by lah...@gmail.com
on 5 Nov 2013 at 9:07
Please focus on the openxcom bugtracker, and if they determine it to be a
yaml-cpp bug, then reopen a bug here.
Original comment by jbe...@gmail.com
on 5 Nov 2013 at 11:46
Original issue reported on code.google.com by
lah...@gmail.com
on 4 Nov 2013 at 12:06