Jean-Sebastien Delfino wrote:
Jean-Sebastien Delfino wrote:
As my laptop crashed earlier this week I'm trying to rebuild all the
Tuscany projects from source, on Linux.
The Tuscany CPP M3 release was using autoconf-based build scripts,
which worked well on Linux at least. The SDO tree still contains the
autoconf files and builds OK for me, but it looks like the autoconf
files have been removed from the SCA tree, when folks working on it
last year were trying to implement an ant-based build.
Unfortunately the ant-based build doesn't seem to work. I'm getting
many errors like this:
[cc] ../../../../deploy/lib/libtuscany_sca.so: undefined
reference to `pthread_key_create'
[cc] ../../../../deploy/lib/libtuscany_sca.so: undefined
reference to `pthread_getspecific'
[cc] ../../../../deploy/lib/libtuscany_sca.so: undefined
reference to `pthread_create'
[cc] ../../../../deploy/lib/libtuscany_sca.so: undefined
reference to `pthread_key_delete'
[cc] ../../../../deploy/lib/libtuscany_sca.so: undefined
reference to `pthread_setspecific'
[cc] ../../../../deploy/lib/libtuscany_sca.so: undefined
reference to `pthread_join'
[cc] collect2: ld returned 1 exit status
and then when I try to build the samples I get this:
BUILD FAILED
/home/delfinoj/SCA/Source/tuscany-cpp/sca/samples/build.xml:60: The
following error occurred while executing this line:
/home/delfinoj/SCA/Source/tuscany-cpp/sca/samples/build.xml:83: The
following error occurred while executing this line:
/home/delfinoj/SCA/Source/tuscany-cpp/sca/samples/CppBigBank/build.xml:50:
The following error occurred while executing this line:
/home/delfinoj/SCA/Source/tuscany-cpp/sca/samples/CppBigBank/build.xml:58:
The following error occurred while executing this line:
/home/delfinoj/SCA/Source/tuscany-cpp/sca/samples/CppBigBank/build.xml:125:
The following error occurred while executing this line:
/home/delfinoj/SCA/Source/tuscany-cpp/sca/antscripts/compile-targets.xml:135:
gcc failed with return code 1
If I comment the samples the build goes further but doesn't produce
the expected structure under sca/deploy.
So I'm going to try to restore the SCA autoconf build files to get the
build going again. I'll leave the ant build scripts if anybody wants
to go and fix them.
If that works, while I'm at it I may volunteer and try to upgrade the
composite loader code to the latest SCA schemas. It may take a little
bit of time, as I'm really busy at work and only looking at this on my
weekend free time.
Hope this helps.
I'm starting to look into supporting the latest SCDL schemas in the CPP
runtime. For now I've just copied the schemas from the Java assembly-xsd
module, and after trying a few changes to the ModelLoader, I'm starting
to think that it could be simplified a bit by using the libxml2 pull API
to read the composite files.
I've made a bit of progress today and committed utility functions that
can read composite files into simple linked lists of symbols and
strings, using the libxml2 XmlReader pull parsing API.
I've also committed an xml-test program that can be used to validate
composites against the latest SCDL schemas.
I'd like to add a few test assemblies and component implementations but
I'd rather not develop them in C++ so I'm probably going to try to
resurrect the python extension (which currently fails for me with a
Sigsegv). I'm also thinking about adding a mini extension with a mock-up
script language that I can use to write test case components. I'll give
an update later after I dig more into the python extension.
--
Jean-Sebastien
