Without looking at the code in question, my experience has been that
standards in C++ templates have been (tightening, changing, evolving)
and the newer versions of C++ are more picky.
Probably a line or two change in a template somewhere in the CellML
code would calm the compiler.
Best
David Nickerson wrote:
Hi all,
I know Andrew and I have discussed this in the past but just thought I'd
raise the issue here and see if anyone has any ideas.
I have just begun trying to build the C++ API implementation using the
latest svn trunk code. I'm using a freshly installed Fedora
Thanks Andrew. So just to make sure I'm getting it right, in the trunk
code CCGS is now a service sitting on top of CaVAS, MaLaES, etc., right?
Andre.
Andrew Miller wrote:
David Nickerson wrote:
Hi all,
I have just done an update on my working copy of the CellML API C++
implementation
Andrew Miller wrote:
David Nickerson wrote:
Thanks Andrew. So just to make sure I'm getting it right, in the trunk
code CCGS is now a service sitting on top of CaVAS, MaLaES, etc., right?
Thats right, so you need to enable those services in configure in order
to enable CCGS.
ok,
David Nickerson wrote:
Andrew Miller wrote:
David Nickerson wrote:
Thanks Andrew. So just to make sure I'm getting it right, in the trunk
code CCGS is now a service sitting on top of CaVAS, MaLaES, etc.,
right?
Thats right, so you need to enable those services in configure in order
Alan Garny wrote:
David Nickerson wrote:
Andrew Miller wrote:
David Nickerson wrote:
Thanks Andrew. So just to make sure I'm getting it right, in the trunk
code CCGS is now a service sitting on top of CaVAS, MaLaES, etc.,
right?
Thats right, so you need to
