This was a workaround for Solaris specific issues in the install program
there. The problem is that this can end up generating empty files, that
will not be detected by the packaging system as it will find the file is
present on destination and thus does not need to be installed.
Change-Id: Ib6107957cbf03c4e7da6cf2998d9103224f674d3
- Make errors fatal, so that they do not get ignored anymore.
- Use sane make variables that a shell will accept as valid, otherwise
the exports do not work at all.
- Do not use system paths when we should use in-tree ones.
(real ticket number: TT#6850)
Change-Id: I07af8f38cc37c2fa36b6b10559283a7c477d2d36
o DESTDIR is only used as installation target directory. Allows staging compile.
o xxx-target used in sub-makefiles
o CXX/CC taken from env variables
- some minor compililation fixes
git-svn-id: http://svn.berlios.de/svnroot/repos/sems/trunk@882 8eb893ce-cfd4-0310-b710-fb5ebe64c474
The version included is 4.1.1. If you generate some files using a new version
of sip4, update or remove sip.h in the apps/py_sems/sip directory.
git-svn-id: http://svn.berlios.de/svnroot/repos/sems/trunk@231 8eb893ce-cfd4-0310-b710-fb5ebe64c474
- py_sems is aimed at integrating as much functionnalities
from the core as possible into python driven applications
(not necessarily IVRs), in a more easy way. The classes can
then just be used as in C++.
- this plug-in uses the sip4 package included in debian.
Please refer to http://www.riverbankcomputing.co.uk/sip/
for more informations on the binding generator.
Please note that you do not need it, if you just want to compile
SEMS. You will need it first if you want to generate more classes.
git-svn-id: http://svn.berlios.de/svnroot/repos/sems/trunk@220 8eb893ce-cfd4-0310-b710-fb5ebe64c474
Guillem Jover
Stefan Sayer
Raphael Coeffic