more kdb build fixes

[Jaroslaw Staniek]

Hi Treeve,
Big thanks. I've applied the 1st patch and also to kproperty and
kreport repos (like kdb, testing these two is recommended).

I am unsure about the exact expression of the 2nd issue and its best solution.
"enable out of tree build if built in-tree, the contents
 of src/parser/generated/ are recreated, which corrupts the source tree. These
 files should not be part of the repository"

Please let me mention that our original desire for the KDb buildsystem
is to ensure that the tools such as flex and bison are not necessary.
We want to offer the code for easy compilation on Windows, mac and
mobile platforms, without forcing users to employ higher level
managers such as Homebrew. In this light the idea of not distributing
generated code has lower priority. A few projects do the same, e.g. I
believe the ANGLE project (see its inclusion Qt5's
qtwebkit/Source/ThirdParty/ANGLE/src/compiler/preprocessor/ExpressionParser.cpp/.y).

Other than that did you mention in-source builds? Do we want that?

Should there be a fix addressing our needs, please let me know.
I can imagine that we can generate files to the build dir and also
still distribute own 'fall back' files. Some cmake code can add the
generated files to the build if flex/bison is available OR else the
distributed ones are used. How does this sound?


On 6 June 2015 at 10:10, Treeve Jelbert <treeve at scarlet.be> wrote:
> see attached files
>
> Regrds, Treeve



-- 
regards, Jaroslaw Staniek

KDE:
: A world-wide network of software engineers, artists, writers, translators
: and facilitators committed to Free Software development - http://kde.org
Calligra Suite:
: A graphic art and office suite - http://calligra.org
Kexi:
: A visual database apps builder - http://calligra.org/kexi
Qt Certified Specialist:
: http://www.linkedin.com/in/jstaniek