Re: [SOSlib-discuss] [sbml-interoperability] libSBML 3.1.1 and SOSLib CVS version

[Rainer M. <ra...@tb...>]

Hi Chris,

Chris wrote:
> Sorry for the indirect post, I realize this is more of an SOSLib issue, but I thought I'd ask here in case anyone knows. We're posting to the SOSLib site separately...
> 
> We have a model consistent with SBML level 2, version 3, rev 2, and libSBML 3.1.1 installed. We use SOSLib for translation of our SBML model to C code; however, the last release of SOSLib depends on an older SBML library and language that is inconsistent with our model. The CVS version of SOSLib should work with libSBML 3.
> 


FYI, SOSlib  internally also generates C-code (with option -c 
SUNDIALS-specific
functions are generated and compiled using GCC, instead of using libSBML 
AST evaluation),
and the current CVS version can actually translate libSBML ASTs directly 
to machine code
(windows and linux, 32bit and 64bit architectures).

> Questions:
> - Are there other tools people use for SBML-to-C translation?
> - Has anyone managed to build the CVS version of SOSLib successfully? The autoconf/automake input and configure.txt seem to be broken.

Sorry, the configure.txt was outdated. I have updated it for now, but in 
general when using the CVS version, you should generate your own 
configure by using ./autogen.sh.


> - Will there be a future release of SOSLib? CVS commitments seems to be sporadic, so perhaps soon?

Yes, but unfortunately we are all snowed under work on other projects. 
We hope to release this summer though.

Rainer

> 
> Anyway, thanks for any advice,
> 
> Chris
> --
> Christopher H. Chang, Ph.D.
> Scientist II
> National Renewable Energy Laboratory
> 1617 Cole Blvd., MS 1608
> Golden, CO  80401
> ____________________________________________________________
> To manage your sbml-interoperability list subscription, visit 
> https://utils.its.caltech.edu/mailman/listinfo/sbml-interoperability
> 
> For a web interface to the sbml-interoperability mailing list, visit
> http://sbml.org/Forums/
> 
> For questions or feedback about the sbml-interoperability list,
> contact sbm...@ca...