Hello Chen,
there is one problem with your proposal:
Our SDK is using stringutil.h/stringutil.cpp for
standalone application, so you can't just remove
them, because they are missing then for these
projects.
I see that it is a little bit confusing to have
two files with nearly the same name
On Mon, 2010-03-08 at 08:27 -0800, Beat Forster wrote:
> Our SDK is using stringutil.h/stringutil.cpp for
> standalone application, so you can't just remove
> them, because they are missing then for these
> projects.
But if these files were kept and stringutils.h/cpp were moved into the
SDK, th
On Mon, 2010-03-08 at 08:27 -0800, Beat Forster wrote:
Our SDK is using stringutil.h/stringutil.cpp for
standalone application, so you can't just remove
them, because they are missing then for these
projects.
But if these files were kept and stringutils.h/cpp were moved into the
SDK, the ch
Hello,
>> As before, because moving files into the SDK implies a relicensing, this
>> change would have to be made in the synthesis.ch git repo by Synthesis.
>> Can we make that fairly soon so that we can remove the hack which
>> exposes these functions in the libsynthesis.so?
> Lukas has to check
Lukas Zeller wrote:
>So Congwu and Patrick, please go ahead and move those files until your builds
>work ok, and put these in a branch in your repo. I'll then merge these into
>synthesis.ch master to make the license change official. Ok?
Thanks Lukas.
I have done the code move and build changes i
Hello Chen,
just one additional remark to stringutil/stringutils:
"stringutil" has been created as engine
independent version of stringutils for the use in
SDK_textdb and other modules. So it might be
worth to try inclusion of stringutil instead of
stringutils (the same way as done e.g. in d
