You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The step of Getting started on the linux.
What steps will reproduce the problem?
1. vim setup.sh
2. . ./setup.sh
3. ./m.sh
4. make
What is the expected output? What do you see instead?
error message :
g++ -fPIC -O -O3 -DUSING_PCH -D_REENTRANT
-I"/home/jarvis/boost_1_55_0/include/boost-1_55"
-I"/home/jarvis/boost_1_55_0/." -I"/include" -I"../src" -DXML_USE_PTHREADS -c
-DQUICKFAST_BUILD_DLL -o "Codecs/XMLTemplateParser.o"
Codecs/XMLTemplateParser.cpp
Codecs/XMLTemplateParser.cpp:36:51: fatal error:
xercesc/framework/MemBufInputSource.hpp: No such file or directory
What version of the product are you using (svn Rev # or download package
version #)? On what operating system? What source of data
boost_1_55_0 , MPC4.0.0 , xerces-c-3.1.1 , Ubuntu 12.04
Please provide any additional information below. Attach templates and
test data if possible and relevant.
Original issue reported on code.google.com by [email protected] on 24 Apr 2014 at 7:42
The text was updated successfully, but these errors were encountered:
i found a typo probably introduced by the mpc makefile creator which causes
this problem.
in the "setup.sh" file we are told to set the paths for "XERCES_ROOT" to:
export XERCES_ROOT=~/quickfast/xerces-c-3.1.1 (or whatever your path is)
but if you look at the output makefile file created in the /src directory
"makefile.quickfast" you will see the mpc introduces some kind of typo and
instead of the CPPFLAGS line having "XERCES_ROOT" they put a "C" instead of "_"
to create the string -I"$(XERCESCROOT)/include
so in my setup.sh i changed XERCES_ROOT to XERCESCROOT
in my case i also had to change the -I"$(XERCESCROOT)/include to
-I"$(XERCESCROOT)/src by manually editing the makefile.quickfast file. for some
reason they hardcode the "/include" somewhere.
Original issue reported on code.google.com by
[email protected]
on 24 Apr 2014 at 7:42The text was updated successfully, but these errors were encountered: