Mar
15
awarded Notable Question
Dec
1
asked how to run predicates and assertions in alloy
Sep
29
awarded Popular Question
Jun
11
comment pugixml vs tinyxml
I started off with Expat but expat does not have XML writing capabilities so I needed to move on to some other library that provides both parsing and XML creation capabilities.
Jun
6
asked merging diffs in two branches
Mar
1
comment string.h and <string>
Thanks to all who took time to reply.
Mar
1
awarded Scholar
Mar
1
accepted string.h and <string>
Mar
1
comment string.h and <string>
I eventually figured out that the makefile had the option -no-stdinc++ enabled and so the compiler wasn't looking into standard folders for headers. When I re-enabled, I have now fixed the above errors (though now a new set of errors in the standard headers which in theory should just work out of the box - but that's another story). Thanks for the suggestions.
Feb
29
comment string.h and <string>
I did change the compiler to g++, but I still get the same error: it is not able to locate string. Interestingly enough in the dependency file for the source file, it DOES show path to folder in cygwin where string resides (/usr/local/lib/gcc/powerpc-eabi/4.1.2/../../../../include/c++/4.1.2/string). Currently I am working on adding verbose flags to see more of what is going under the hood ...
Feb
29
comment string.h and <string>
Thanks. I am considering changing the legacy build scripts to use g++. One thing I did notice that nowhere in the sources (and most of it are cpp files) powerpc-eabi-g++ was used to build - all were built using powerpc-eabi-gcc. Neither, do I see any explicit references to stdc++ or -x c++ in the makefiles. May be it stdc++ was pulled in implicitly though boost (I do see some boost headers in the source code files). Is there I could determine how then some of the other libaries using string, vector etc were able to link into libstdc++ even if it was not explicitly called out in the makefile?
Feb
29
revised string.h and <string>
edited tags
Feb
28
awarded Editor
Feb
28
revised string.h and <string>
added 526 characters in body
Feb
28
comment string.h and <string>
@Mat: It is compiling with gcc i.e. powerpc-eabi-gcc, but it is the same compiler that successfully built the other library using the same source code file.
Feb
28
asked string.h and <string>
Feb
20
awarded Supporter
Feb
20
comment class vs helper routines - C++
Thank you very much to all of you who contributed. It has definitely clarified a lot of concepts for me.
Feb
16
asked class vs helper routines - C++
Jan
16
comment pugixml vs tinyxml
Thanks to both of you for your replies. @P3trus - Do you have any comments on 'memory usage' of pugixml and tinyxml - for both reading and writing? The files I am going to parse/write fairly small files and I am wondering which one would be more efficient.
1 2